public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
* building and using gcc-3.2
@ 2002-10-25 17:51 Mike Eldridge
  0 siblings, 0 replies; only message in thread
From: Mike Eldridge @ 2002-10-25 17:51 UTC (permalink / raw)
  To: gcc-help

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

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2002-10-26  0:51 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-10-25 17:51 building and using gcc-3.2 Mike Eldridge

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).