This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
building and using gcc-3.2
- From: Mike Eldridge <diz at cafes dot net>
- To: gcc-help at gcc dot gnu dot org
- Date: Fri, 25 Oct 2002 19:51:30 -0500
- Subject: building and using gcc-3.2
hi all,
i've built and installed gcc-3.2. however, it won't link to shared
objects compiled with gcc-2.96-98 (this is straight c, no c++ involved).
the dynamic linker bombs with this message:
/lib/ld-linux.so.2(*IND*+0x0): multiple definition of `__xstat64'
/lib/ld-linux.so.2(.text+0xd600): first defined here
/lib/ld-linux.so.2(*IND*+0x0): multiple definition of `__fxstat64'
/lib/ld-linux.so.2(.text+0xd640): first defined here
collect2: ld returned 1 exit status
i successively built binutils and glibc-2.2.5, thinking that was my
problem. now i can dynamically link to glibc-2.2.5's libc and
ld-linux.so utilizing -Wl,--dynamic-linker and -Wl,--rpath, though the
resulting binary segfaults. :/
my question: what do i *need* in order to be able to use gcc 3.2 on my
current system?
- do i *need* a new binutils?
- do i *need* shared objects exclusively compiled with gcc 3.2?
- do i *need* a new glibc exclusively compiled with gcc 3.2/binutils
2.13?
any pointers (no pun intended), urls, comments, flames, and/or
suggestions are more than welcome; in fact, they are appreciated.
thanks for your time,
-mike
------------------------------------------------------------------------
/~\ the ascii "a jury consists of twelve persons
\ / ribbon campaign chosen to decide who has the better
X against html lawyer"
/ \ email! -- robert frost