LIGO Support Ticket 18191
Ticket Information
Number: admin 18191
User: dabrown@physics.syr.edu
Email: anderson__AT__ligo.caltech.edu,skoranda__AT__gravity.phys.uwm.edu,jolien__AT__gravity.phys.uwm.edu
Status: resolved
Assigned To: psilord
CC: Stuart Anderson <anderson__AT__ligo.caltech.edu>, Scott Koranda
<skoranda__AT__gravity.phys.uwm.edu>, Jolien Creighton
<jolien__AT__gravity.phys.uwm.edu>
From: Duncan Brown <dabrown__AT__physics.syr.edu>
Subject: LIGO: request to fix condor_compile error messages under gnu
autotools
Date: Thu, 3 Jul 2008 08:06:31 -0400
To: condor-admin response tracking system <condor-admin__AT__cs.wisc.edu>
X-Scanner: InterScan AntiVirus for Sendmail
X-Seen-BY: mailfromd 4.1 gypsum.cs.wisc.edu
Hi Peter,
When LIGO users try and condor compile our code using a gnu autoconf
generated configure script, the condor_compile prints out lots of
error messages. There is no actual error, as the linker returns with
status code 0, so the configure completes fine. Is there any way
these error messages can be suppressed, as they are confusion our
users? People think that there is a problem, when they can just type
make and continue fine.
Cheers,
Duncan.
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for gawk... (cached) gawk
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking how to run the C preprocessor... gcc -E
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking for condor_compile... condor_compile
checking for a BSD-compatible install... /usr/bin/install -c
checking whether ln -s works... yes
checking for ld used by GCC... /usr/lib64/ld ERROR: Internal ld was
not invoked! ERROR: Executable may not be linked properly for Condor!
ERROR: For users of Condor on Linux, we highly recommend ERROR: using
the default compiler that came with the ERROR: distribution. Usually
placing /usr/bin first in ERROR: your path will remedy this error.
ERROR: To learn more about this error, visit this web page: ERROR:
http://www.cs.wisc.edu/condor/manual/faq.html ERROR: and read the FAQ
entry about this problem for your ERROR: revision of Condor.
checking if the linker (/usr/lib64/ld ERROR: Internal ld was not
invoked! ERROR: Executable may not be linked properly for Condor!
ERROR: For users of Condor on Linux, we highly recommend ERROR: using
the default compiler that came with the ERROR: distribution. Usually
placing /usr/bin first in ERROR: your path will remedy this error.
ERROR: To learn more about this error, visit this web page: ERROR:
http://www.cs.wisc.edu/condor/manual/faq.html ERROR: and read the FAQ
entry about this problem for your ERROR: revision of Condor.) is GNU
ld... yes
checking for /usr/lib64/ld ERROR: Internal ld was not invoked! ERROR:
Executable may not be linked properly for Condor! ERROR: For users of
Condor on Linux, we highly recommend ERROR: using the default
compiler that came with the ERROR: distribution. Usually placing /usr/
bin first in ERROR: your path will remedy this error. ERROR: To learn
more about this error, visit this web page: ERROR: http://
www.cs.wisc.edu/condor/manual/faq.html ERROR: and read the FAQ entry
about this problem for your ERROR: revision of Condor. option to
reload object files... -r
checking for BSD-compatible nm... /usr/bin/nm -B
checking how to recognise dependant libraries... file_magic ELF [0-9]
[0-9]*-bit [LM]SB (shared object|dynamic lib )
checking command to parse /usr/bin/nm -B output... ok
checking for egrep... grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking for file... /usr/bin/file
checking for ranlib... ranlib
checking for strip... strip
checking for objdir... .libs
checking for condor_compile option to produce PIC... -fPIC
checking if condor_compile PIC flag -fPIC works... yes
checking if condor_compile static flag -static works... yes
checking if condor_compile supports -c -o file.o... yes
checking if condor_compile supports -c -o file.lo... no
checking if condor_compile supports -fno-rtti -fno-exceptions... no
checking whether the linker (/usr/lib64/ld ERROR: Internal ld was not
invoked! ERROR: Executable may not be linked properly for Condor!
ERROR: For users of Condor on Linux, we highly recommend ERROR: using
the default compiler that came with the ERROR: distribution. Usually
placing /usr/bin first in ERROR: your path will remedy this error.
ERROR: To learn more about this error, visit this web page: ERROR:
http://www.cs.wisc.edu/condor/manual/faq.html ERROR: and read the FAQ
entry about this problem for your ERROR: revision of Condor.)
supports shared libraries... yes
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... no
checking whether to build static libraries... yes
creating libtool
checking for pdflatex... pdflatex
checking for makeindex... makeindex
--
Duncan Brown Room 263-1, Department of Physics,
Assistant Professor of Physics Syracuse University, NY 13244, USA
Phone: (315) 443 5993 http://www.gravity.phy.syr.edu/~duncan
===========================================================================
Date of creation: Thu Jul 3 7:06:36 2008 (1215086799)
Subject: Actions
Assigned to psilord by psilord
===========================================================================
Date of actions: Thu Jul 3 11:10:46 2008 (1215101447)
Date: Thu, 3 Jul 2008 15:30:29 -0500
From: Peter Keller <psilord__AT__cs.wisc.edu>
To: psilord <condor-admin__AT__cs.wisc.edu>
Subject: Re: [condor-admin #18191] LIGO: request to fix condor_compile
error messages under gnu
Hello,
On Thu, Jul 03, 2008 at 11:10:46AM -0500, psilord wrote:
> From: Duncan Brown <dabrown__AT__physics.syr.edu>
>
> Hi Peter,
>
> When LIGO users try and condor compile our code using a gnu autoconf
> generated configure script, the condor_compile prints out lots of
> error messages. There is no actual error, as the linker returns with
> status code 0, so the configure completes fine. Is there any way
> these error messages can be suppressed, as they are confusion our
> users? People think that there is a problem, when they can just type
> make and continue fine.
Oh my, did you folks do a "full install" of stduniv on that machine? This
is where /usr/bin (or applicable)/ld is replaced by our ld script and
the original is moved to /usr/bin (or applicable)/ld.real?
What exactly is /usr/lib64/ld on that machine? Is it a real binary or
a Condor script?
I'm very surprised that this configure script would find or utilize our
condor_compile or ld scripts, unless the person specifically had
a condor path set up before their system paths to find it or you did
a full install.
Could I see the command they ran too to generate that?
Thank you.
-pete
===========================================================================
Date mail was appended: Thu Jul 3 15:30:31 2008 (1215117032)
Subject: Comments added
resolving this one for now -- duncan will do more homework since it now
looks like a problem w/ one of his configure macros.
Comments added by tannenba
===========================================================================
Date comments were added: Fri Jul 18 13:56:16 2008 (1216407377)
Subject: Actions
Ticket resolved by tannenba
===========================================================================
Date of actions: Fri Jul 18 13:56:53 2008 (1216407413)