You are not logged in.
Pages: 1
Just a heads up. Don't upgrade to the new glibc/gcc combo.
Unless you want some of this.
checking for C compiler default output file name... configure: error: C compiler cannot create executables
Or some of this.
/usr/bin/ld:/usr/lib/gcc/i686-pc-linux-gnu/4.0.0/../../../libc.so: file format not recognized; treating as linker script
/usr/bin/ld:/usr/lib/gcc/i686-pc-linux-gnu/4.0.0/../../../libc.so:5: parse error
collect2: ld returned 1 exit status
make[2]: *** [graveman] Error 1
make[2]: Leaving directory `/opt/abs/local/graveman/src/graveman-0.3.10/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/opt/abs/local/graveman/src/graveman-0.3.10'
make: *** [all] Error 2
==> ERROR: Build Failed. Aborting...
Offline
Alright, I've come to the conclusion that it's the redhat / fedora patch that was introduced in -3.
I'm recompiling it right now to find out.
Offline
Odd, I removed the patch. Same thing..
I'm just going to rename -1 to -3 and leave it like that..
-1 gives no issues.. hmm..
Offline
Yes, and just to add to that, something else of relevance:
Offline
You need a new binutils with this new glibc.
Offline
I like this part:
/usr/bin/ld:/usr/lib/gcc/i686-pc-linux-gnu/4.0.0/../../../libc.so: file format not recognized; treating as linker script
libc not recognized... hah
Offline
/usr/lib/libc.so is actually a linker script, open it up with a text editor and you'll see. You'll also see the reason for the message and the "missing libc.so.5" or something like that: the new /usr/lib/libc.so uses scripting to enforce AS_NEEDED on everything that compiles against glibc. This is not supported by any version of binutils, except the ones in Fedora and the one in our testing repository, at the same place you got that glibc snapshot.
BTW: In the next few days we'll have another glibc, the -3 build breaks ancient binaries like the teamspeak client.
Offline
Pages: 1