Hi Gilles san, thank you for your quick comment. I fully understand the
meaning of the warning. Regarding the question you raise, I'm afraid that
I'm not sure which solution is better ...

Regards,
Tetsuya Mishima

2016/07/07 14:13:02、"devel"さんは「Re: [OMPI devel] v2.0.0rc4 is
released」で書きました
> This is a warning that can be safely ignored.
>
>
> That being said, this can be seen as a false positive (unless we fix
> flex or its generated output).
>
> Also, and generally speaking, these kind of warnings is for developers
> only (e.g. end users can do nothing about that).
>
>
> That raises the question : what could/should we do ?
>
> - master filters out these false positives, should we backport this to
> v2.x ?
>
> - should we simply not check for common symbols when building from a
> tarball ?
>
>
> Cheers,
>
>
> Gilles
>
> On 7/7/2016 2:03 PM, tmish...@jcity.maeda.co.jp wrote:
> > Hi Jeff, sorry for a very short report. I saw the warning below
> > at the end of installation of openmpi-2.0.0rc4. Is this okay?
> >
> > $ make install
> > ...
> > make  install-exec-hook
> > make[3]: Entering directory
> > `/home/mishima/mis/openmpi/openmpi-pgi16.5/openmpi-2.0.0rc4'
> > WARNING!  Common symbols found:
> >            show_help_lex.o: 0000000000000004 C opal_show_help_yyleng
> >            show_help_lex.o: 0000000000000008 C opal_show_help_yytext
> >             hostfile_lex.o: 0000000000000004 C orte_util_hostfile_leng
> >             hostfile_lex.o: 0000000000000008 C orte_util_hostfile_text
> >      rmaps_rank_file_lex.o: 0000000000000004 C
orte_rmaps_rank_file_leng
> >      rmaps_rank_file_lex.o: 0000000000000008 C
orte_rmaps_rank_file_text
> > make[3]: [install-exec-hook] Error 1 (ignored)
> > make[3]: Leaving directory
> > `/home/mishima/mis/openmpi/openmpi-pgi16.5/openmpi-2.0.0rc4'
> > make[2]: Nothing to be done for `install-data-am'.
> > make[2]: Leaving directory
> > `/home/mishima/mis/openmpi/openmpi-pgi16.5/openmpi-2.0.0rc4'
> > make[1]: Leaving directory
> > `/home/mishima/mis/openmpi/openmpi-pgi16.5/openmpi-2.0.0rc4'
> >
> > Regards,
> > Tetsuya Mishima
> >
> > 2016/07/07 2:40:25、"devel"さんは「[OMPI devel] v2.0.0rc4 is
released」で書
> > きました
> >> While crossing our fingers and doing mystical rain dances, we're
hoping
> > that 2.0.0rc4 is the last rc before v2.0.0 (final) is released.  Please
> > test!
> >> https://www.open-mpi.org/software/ompi/v2.x/
> >>
> >> Changes since rc3 (the list may look long, but most are quite small
> > corner cases):
> >> - Lots of threading fixes
> >> - More fixes for the new memory patcher system
> >> - Updates to NEWS and README
> >> - Fixed some hcoll bugs
> >> - Updates for external PMIx support
> >> - PMIx direct launching fixes
> >> - libudev fixes
> >> - compatibility fixes with ibv_exp_*
> >> - 32 bit compatibility fixes
> >> - fix some powerpc issues
> >> - various OMPIO / libnbc fixes from Lisandro Dalcin
> >> - fix some Solaris configury patching
> >> - fix PSM/PSM2 active state detection
> >> - disable PSM/PSM2 signal hijacking by default
> >> - datatype fixes
> >> - portals4 fixes
> >> - change ofi MTL to only use a limited set of OFI providers by default
> >> - fix OSHMEM init error check
> >>
> >> --
> >> Jeff Squyres
> >> jsquy...@cisco.com
> >> For corporate legal information go to:
> > http://www.cisco.com/web/about/doing_business/legal/cri/
> >> _______________________________________________
> >> devel mailing list
> >> de...@open-mpi.org
> >> Subscription: https://www.open-mpi.org/mailman/listinfo.cgi/devel
> >> Link to this post:
> > http://www.open-mpi.org/community/lists/devel/2016/07/19153.php
> > _______________________________________________
> > devel mailing list
> > de...@open-mpi.org
> > Subscription: https://www.open-mpi.org/mailman/listinfo.cgi/devel
> > Link to this post:
http://www.open-mpi.org/community/lists/devel/2016/07/19158.php
>
> _______________________________________________
> devel mailing list
> de...@open-mpi.org
> Subscription: https://www.open-mpi.org/mailman/listinfo.cgi/develLink to
this post: http://www.open-mpi.org/community/lists/devel/2016/07/19159.php

Reply via email to