[cgma-dev] buildbot failure in Fathom on cgm-cubit

Robert Smith smithrm at mcs.anl.gov
Thu Jan 21 10:05:00 CST 2010


This failure looks like a configure specification issue.
LD_LIBRARY_PATH should point to the Cubit bin directory.  There should  
be no "/lib/" at the end.  The location should end at "/bin".

Also I thought the "--with-cubit" flag on configure should just point  
to the Cubit directory and not to the bin directory.

So my proposed changes are:
     LD_LIBRARY_PATH=/home/sharp/3rdparty/Cubit/Cubit64/cubit-10.2- 
amd64/bin:$LD_LIBRARY_PATH
     --with-cubit=/home/sharp/3rdparty/Cubit/Cubit64/cubit-10.2-amd64

--Bob

On Jan 21, 2010, at 12:17 AM, cgma-dev at lists.mcs.anl.gov wrote:

> The Fathomatic has detected a failed build of cgm-cubit on Fathom.
> Full details are available at:
> http://gnep.mcs.anl.gov:8010/builders/cgm-cubit/builds/0
>
> Buildbot URL: http://gnep.mcs.anl.gov:8010/
>
> Buildslave for this Build: gnep
>
> Build Reason: The Nightly scheduler named 'nightly' triggered this  
> build
> Build Source Stamp: None
> Blamelist:
>
> BUILD FAILED: failed configure
>
> LOG EXCERPT:
> checking if cc supports -fno-rtti -fno-exceptions... no
> checking for cc option to produce PIC... -fPIC
> checking if cc PIC flag -fPIC works... yes
> checking if cc static flag -static works... yes
> checking if cc supports -c -o file.o... yes
> checking whether the cc linker (/usr/bin/ld -m elf_x86_64) supports  
> shared libraries... yes
> checking dynamic linker characteristics... GNU/Linux ld.so
> checking how to hardcode library paths into programs... immediate
> checking whether stripping libraries is possible... yes
> checking if libtool supports shared libraries... yes
> checking whether to build shared libraries... no
> checking whether to build static libraries... yes
> configure: creating libtool
> appending configuration tag "CXX" to libtool
> checking for ld used by c++... /usr/bin/ld -m elf_x86_64
> checking if the linker (/usr/bin/ld -m elf_x86_64) is GNU ld... yes
> checking whether the c++ linker (/usr/bin/ld -m elf_x86_64) supports  
> shared libraries... yes
> checking for c++ option to produce PIC... -fPIC
> checking if c++ PIC flag -fPIC works... yes
> checking if c++ static flag -static works... yes
> checking if c++ supports -c -o file.o... yes
> checking whether the c++ linker (/usr/bin/ld -m elf_x86_64) supports  
> shared libraries... yes
> checking dynamic linker characteristics... GNU/Linux ld.so
> (cached) (cached) checking how to hardcode library paths into  
> programs... immediate
> appending configuration tag "F77" to libtool
> checking if libtool supports shared libraries... yes
> checking whether to build shared libraries... no
> checking whether to build static libraries... yes
> checking for gfortran option to produce PIC... -fPIC
> checking if gfortran PIC flag -fPIC works... yes
> checking if gfortran static flag -static works... yes
> checking if gfortran supports -c -o file.o... yes
> checking whether the gfortran linker (/usr/bin/ld -m elf_x86_64)  
> supports shared libraries... yes
> checking dynamic linker characteristics... GNU/Linux ld.so
> (cached) (cached) checking how to hardcode library paths into  
> programs... immediate
> checking for a sed that does not truncate output... /bin/sed
> checking whether byte ordering is bigendian... no
> checking for known C compilers... GNU
> checking for known compiler/OS combinations... GNU:x86_64
> checking for known c++ compilers... GNU
> checking for known compiler/OS combinations... GNU:x86_64
> checking how to get verbose linking output from gfortran... -v
> checking for Fortran libraries of gfortran...  -L/usr/lib/gcc/x86_64- 
> linux-gnu/4.2.4 -L/usr/lib/gcc/x86_64-linux-gnu/4.2.4/../../../../ 
> lib -L/lib/../lib -L/usr/lib/../lib -L/usr/lib/gcc/x86_64-linux-gnu/ 
> 4.2.4/../../.. -lgfortranbegin -lgfortran -lm
> checking for dummy main to link with Fortran libraries... none
> checking for Fortran name-mangling scheme... lower case, underscore,  
> no extra underscore
> checking for C++-standard library in std:: namespace... yes
> checking for C++-standard I/O in std:: namespace... yes
> checking if C++ template definitions should be included... yes
> checking for AcisQueryEngine::instance_ in /home/sharp/3rdparty/ 
> Cubit/Cubit64/cubit-10.2-amd64/bin/lib/*cubiti[0-9][0-9].*... no
> configure: error: "Cubit library not found in /home/sharp/3rdparty/ 
> Cubit/Cubit64/cubit-10.2-amd64/bin/lib"
>
> sincerely,
> -The Fathomatic



More information about the cgma-dev mailing list