Followup on https://github.com/open-mpi/ompi/pull/1028.


> On Oct 14, 2015, at 2:37 AM, Gilles Gouaillardet 
> <[email protected]> wrote:
> 
> Folks,
> 
> i was able to reproduce the issue by adding CPPFLAGS=-I/tmp to my
> configure command line.
> here is what happens :
> opal/mca/pmix/pmix1xx/configure.m4 set the CPPFLAGS environment
> variable with -I/tmp and include paths for hwloc and libevent
> then opal/mca/pmix/pmix1xx/pmix/configure is invoked with
> CPPFLAGS=-I/tmp on the command line
> the CPPFLAGS environment variable is simply ignored, and only -I/tmp
> is used, which causes the compilation failure reported by Siegmar.
> 
> at this stage, i do not know the best way to solve this issue :
> one option is not to pass CPPFLAGS=-I/tmp to the sub configure
> an other option is not to set the CPPFLAGS environment variable but
> invoke the sub configure with "CPPFLAGS=$CPPFLAGS"
> note this issue might not be limited to CPPFLAGS handling
> 
> could you please advise on how to move forward ?
> 
> Cheers,
> 
> Gilles
> 
> On Wed, Oct 7, 2015 at 4:42 PM, Siegmar Gross
> <[email protected]> wrote:
>> Hi,
>> 
>> I tried to build openmpi-v2.x-dev-415-g5c9b192 and
>> openmpi-dev-2696-gd579a07 on my machines (Solaris 10 Sparc, Solaris 10
>> x86_64, and openSUSE Linux 12.1 x86_64) with gcc-5.1.0 and Sun C 5.13.
>> I got the following error on all platforms with gcc and with Sun C only
>> on my Linux machine. I've already reported the problem September 8th
>> for the master trunk (at that time I didn't have the problem for the
>> v2.x trunk. I use the following configure command.
>> 
>> ../openmpi-dev-2696-gd579a07/configure \
>>  --prefix=/usr/local/openmpi-master_64_gcc \
>>  --libdir=/usr/local/openmpi-master_64_gcc/lib64 \
>>  --with-jdk-bindir=/usr/local/jdk1.8.0/bin \
>>  --with-jdk-headers=/usr/local/jdk1.8.0/include \
>>  JAVA_HOME=/usr/local/jdk1.8.0 \
>>  LDFLAGS="-m64" CC="gcc" CXX="g++" FC="gfortran" \
>>  CFLAGS="-m64" CXXFLAGS="-m64" FCFLAGS="-m64" \
>>  CPP="cpp" CXXCPP="cpp" \
>>  CPPFLAGS="" CXXCPPFLAGS="" \
>>  --enable-mpi-cxx \
>>  --enable-cxx-exceptions \
>>  --enable-mpi-java \
>>  --enable-heterogeneous \
>>  --enable-mpi-thread-multiple \
>>  --with-hwloc=internal \
>>  --without-verbs \
>>  --with-wrapper-cflags="-std=c11 -m64" \
>>  --with-wrapper-cxxflags="-m64" \
>>  --with-wrapper-fcflags="-m64" \
>>  --enable-debug \
>>  |& tee log.configure.$SYSTEM_ENV.$MACHINE_ENV.64_gcc
>> 
>> 
>> openmpi-v2.x-dev-415-g5c9b192:
>> ==============================
>> 
>> linpc1 openmpi-v2.x-dev-415-g5c9b192-Linux.x86_64.64_gcc 135 tail -15
>> log.make.Linux.x86_64.64_gcc
>>  CC       src/class/pmix_pointer_array.lo
>>  CC       src/class/pmix_hash_table.lo
>>  CC       src/include/pmix_globals.lo
>> In file included from
>> ../../../../../../openmpi-v2.x-dev-415-g5c9b192/opal/mca/pmix/pmix1xx/pmix/src/include/pmix_globals.c:19:0:
>> /export2/src/openmpi-2.0.0/openmpi-v2.x-dev-415-g5c9b192/opal/mca/pmix/pmix1xx/pmix/include/private/types.h:43:27:
>> fatal error: opal/mca/event/libevent2022/libevent2022.h: No such file or
>> directory
>> compilation terminated.
>> make[4]: *** [src/include/pmix_globals.lo] Error 1
>> make[4]: Leaving directory
>> `/export2/src/openmpi-2.0.0/openmpi-v2.x-dev-415-g5c9b192-Linux.x86_64.64_gcc/opal/mca/pmix/pmix1xx/pmix'
>> make[3]: *** [all-recursive] Error 1
>> make[3]: Leaving directory
>> `/export2/src/openmpi-2.0.0/openmpi-v2.x-dev-415-g5c9b192-Linux.x86_64.64_gcc/opal/mca/pmix/pmix1xx/pmix'
>> make[2]: *** [all-recursive] Error 1
>> make[2]: Leaving directory
>> `/export2/src/openmpi-2.0.0/openmpi-v2.x-dev-415-g5c9b192-Linux.x86_64.64_gcc/opal/mca/pmix/pmix1xx'
>> make[1]: *** [all-recursive] Error 1
>> make[1]: Leaving directory
>> `/export2/src/openmpi-2.0.0/openmpi-v2.x-dev-415-g5c9b192-Linux.x86_64.64_gcc/opal'
>> make: *** [all-recursive] Error 1
>> linpc1 openmpi-v2.x-dev-415-g5c9b192-Linux.x86_64.64_gcc 135
>> 
>> 
>> openmpi-dev-2696-gd579a07:
>> ==========================
>> 
>> linpc1 openmpi-dev-2696-gd579a07-Linux.x86_64.64_gcc 158 tail -15
>> log.make.Linux.x86_64.64_gcc
>>  CC       src/class/pmix_pointer_array.lo
>>  CC       src/class/pmix_hash_table.lo
>>  CC       src/include/pmix_globals.lo
>> In file included from
>> ../../../../../../openmpi-dev-2696-gd579a07/opal/mca/pmix/pmix1xx/pmix/src/include/pmix_globals.c:19:0:
>> /export2/src/openmpi-master/openmpi-dev-2696-gd579a07/opal/mca/pmix/pmix1xx/pmix/include/private/types.h:43:27:
>> fatal error: opal/mca/event/libevent2022/libevent2022.h: No such file or
>> directory
>> compilation terminated.
>> make[4]: *** [src/include/pmix_globals.lo] Error 1
>> make[4]: Leaving directory
>> `/export2/src/openmpi-master/openmpi-dev-2696-gd579a07-Linux.x86_64.64_gcc/opal/mca/pmix/pmix1xx/pmix'
>> make[3]: *** [all-recursive] Error 1
>> make[3]: Leaving directory
>> `/export2/src/openmpi-master/openmpi-dev-2696-gd579a07-Linux.x86_64.64_gcc/opal/mca/pmix/pmix1xx/pmix'
>> make[2]: *** [all-recursive] Error 1
>> make[2]: Leaving directory
>> `/export2/src/openmpi-master/openmpi-dev-2696-gd579a07-Linux.x86_64.64_gcc/opal/mca/pmix/pmix1xx'
>> make[1]: *** [all-recursive] Error 1
>> make[1]: Leaving directory
>> `/export2/src/openmpi-master/openmpi-dev-2696-gd579a07-Linux.x86_64.64_gcc/opal'
>> make: *** [all-recursive] Error 1
>> linpc1 openmpi-dev-2696-gd579a07-Linux.x86_64.64_gcc 159
>> 
>> 
>> I would be grateful if somebody can fix the problem. Thank you very much
>> for any help in advance.
>> 
>> 
>> Kind regards
>> 
>> Siegmar
>> 
>> 
>> 
>> _______________________________________________
>> users mailing list
>> [email protected]
>> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users
>> Link to this post:
>> http://www.open-mpi.org/community/lists/users/2015/10/27826.php
> _______________________________________________
> devel mailing list
> [email protected]
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> Link to this post: 
> http://www.open-mpi.org/community/lists/devel/2015/10/18159.php


-- 
Jeff Squyres
[email protected]
For corporate legal information go to: 
http://www.cisco.com/web/about/doing_business/legal/cri/

Reply via email to