[Expat-bugs] [ expat-Bugs-1580748 ] Not linking under Fedora Core 5

SourceForge.net noreply at sourceforge.net
Fri Oct 27 16:43:56 CEST 2006


Bugs item #1580748, was opened at 2006-10-19 13:17
Message generated for change (Comment added) made by wkosborn
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1580748&group_id=10127

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Build control
Group: Platform Specific
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Greg Stein (gstein)
Summary: Not linking under Fedora Core 5

Initial Comment:
I'm trying to compile Expat on Fedora Core 5 (first
1.95.8, then I obtained 2.0.0 from CVS to try that) and
it fails at the linking stage.
Below is the output from make and configure. Please help.

What we have:
gcc 4.1.0
libool 1.5.22

If you need any other information please let me know. 

Thanks!

Wendy

-----------output from make---------------
/bin/sh ./libtool --silent --mode=compile gcc -I./lib
-I. -g -O2 -Wall
-Wmissing-prototypes -Wstrict-prototypes -fexceptions 
-DHAVE_EXPAT_CONFIG_H -o lib/xmlparse.lo -c lib/xmlparse.c
/bin/sh ./libtool --silent --mode=compile gcc -I./lib
-I. -g -O2 -Wall
-Wmissing-prototypes -Wstrict-prototypes -fexceptions 
-DHAVE_EXPAT_CONFIG_H -o lib/xmltok.lo -c lib/xmltok.c
/bin/sh ./libtool --silent --mode=compile gcc -I./lib
-I. -g -O2 -Wall
-Wmissing-prototypes -Wstrict-prototypes -fexceptions 
-DHAVE_EXPAT_CONFIG_H -o lib/xmlrole.lo -c lib/xmlrole.c
/bin/sh ./libtool --silent --mode=link gcc -I./lib -I.
-g -O2 -Wall
-Wmissing-prototypes -Wstrict-prototypes -fexceptions 
-DHAVE_EXPAT_CONFIG_H -no-undefined -version-info 6:0:5
-rpath
/usr/local/lib  -o libexpat.la lib/xmlparse.lo
lib/xmltok.lo
lib/xmlrole.lo
./libtool: line 5906: eval: -@: invalid option
eval: usage: eval [arg ...]
make: *** [libexpat.la] Error 2


-------output from configure-----------
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
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 a sed that does not truncate output...
/bin/sed
checking for egrep... grep -E
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for /usr/bin/ld option to reload object
files... -r
checking for BSD-compatible nm... /usr/bin/nm -B
checking whether ln -s works... yes
checking how to recognise dependent libraries... pass_all
checking how to run the C preprocessor... gcc -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 g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking how to run the C++ preprocessor... g++ -E
checking for g77... g77
checking whether we are using the GNU Fortran 77
compiler... yes
checking whether g77 accepts -g... yes
checking the maximum length of command line
arguments... 32768
checking command to parse /usr/bin/nm -B output from
gcc object... ok
checking for objdir... .libs
checking for ar... ar
checking for ranlib... - at true
checking for strip... strip
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC
checking if gcc PIC flag -fPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking whether the gcc linker (/usr/bin/ld) supports
shared libraries...
yes
checking whether -lc should be explicitly linked in... no
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... yes
checking whether to build static libraries... yes
configure: creating libtool
appending configuration tag "CXX" to libtool
checking for ld used by g++... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking whether the g++ linker (/usr/bin/ld) supports
shared libraries...
yes
checking for g++ option to produce PIC... -fPIC
checking if g++ PIC flag -fPIC works... yes
checking if g++ static flag -static works... yes
checking if g++ supports -c -o file.o... yes
checking whether the g++ linker (/usr/bin/ld) supports
shared libraries...
yes
checking dynamic linker characteristics... GNU/Linux ld.so
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... yes
checking whether to build static libraries... yes
checking for g77 option to produce PIC... -fPIC
checking if g77 PIC flag -fPIC works... yes
checking if g77 static flag -static works... yes
checking if g77 supports -c -o file.o... yes
checking whether the g77 linker (/usr/bin/ld) supports
shared libraries...
yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs...
immediate
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler...
(cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to accept ANSI C... (cached)
none needed
checking for a BSD-compatible install...
/usr/bin/install -c
checking whether gcc accepts -fexceptions... yes
checking for ANSI C header files... (cached) yes
checking whether byte ordering is bigendian... no
checking for an ANSI C-conforming const... yes
checking for size_t... yes
checking for memmove... yes
checking for bcopy... yes
checking fcntl.h usability... yes
checking fcntl.h presence... yes
checking for fcntl.h... yes
checking for unistd.h... (cached) yes
checking for off_t... yes
checking for stdlib.h... (cached) yes
checking for unistd.h... (cached) yes
checking for getpagesize... yes
checking for working mmap... yes
checking for an ANSI C99-conforming __func__... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: creating expat_config.h






----------------------------------------------------------------------

Comment By: wko (wkosborn)
Date: 2006-10-27 08:43

Message:
Logged In: YES 
user_id=1625052

Hi again,

I figured out the problem.  

The reason for:

checking for ranlib... - at true

Is because I had an environment variable RANLIB that was set
to - at true (assuming that this variable is supposed to
contain the location of the executable program ranlib, this
obviously isn't it).  The configure script reads this value
in and uses it. 

Removing the environment variable seem to work - I did that
with: 

unset RANLIB

and now it's compiling. 

Thanks, and sorry about all of this!

Wendy
(wkosborn at sourceforge)

----------------------------------------------------------------------

Comment By: Karl Waclawek (kwaclaw)
Date: 2006-10-25 18:00

Message:
Logged In: YES 
user_id=290026

I tried again with FC4, no problem. Here is what I am using:

- autoconf version 2.59
- libtool version 1.5.16
- gcc (GCC) 4.0.0 20050519 (Red Hat 4.0.0-8)

and yes, my configure output is: checking for ranlib... ranlib
I don't know what ranlib refers to, however.
Looks like this should be the focus of attention.




----------------------------------------------------------------------

Comment By: wko (wkosborn)
Date: 2006-10-25 14:13

Message:
Logged In: YES 
user_id=1625052

Hi again,

I just noticed something that may be causing the problem -
although I admit I don't know what to do about it. 

In the configure output above I noticed this: 

checking for ranlib... - at true

isn't this supposed to be:
checking for ranlib... ranlib

? 

Thanks,

Wendy
(wkosborn at sourceforge)

----------------------------------------------------------------------

Comment By: wko (wkosborn)
Date: 2006-10-25 13:44

Message:
Logged In: YES 
user_id=1625052

Hi again,

I was able to access another machine with Fedora Core 4, so
I thought I would try to make expat 2.0.0 on there (CVS
distribution).  I ran buildconf.sh, then ./configure, then
make. I got the same error as above.

I was told that Expat did link with no problems under FC4. 
So maybe i'm doing something wrong?  Please let me know . 

Thanks,

Wendy

----------------------------------------------------------------------

Comment By: Karl Waclawek (kwaclaw)
Date: 2006-10-19 14:13

Message:
Logged In: YES 
user_id=290026

This one seems important to fix before the next release.
Greg or Fred, please assist!

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1580748&group_id=10127


More information about the Expat-bugs mailing list