Re: Officially sanctioned way of installing multiple glibcs?
The 'compiler' still runs (if I use -c or -S) but if it tries to link
anything, I get:
(%:~)- ecc
/usr/lib/crt1.o(.text+0x41): In function `_start':
: undefined reference to `main'
/usr/lib/libc_nonshared.a(elf-init.oS)(.text+0x31): In function
`__libc_csu_init ':
: undefined reference to `__init_array_start'
/usr/lib/libc_nonshared.a(elf-init.oS)(.text+0x32): In function
`__libc_csu_init ':
: undefined reference to `__init_array_end'
/usr/lib/libc_nonshared.a(elf-init.oS)(.text+0x40): In function
`__libc_csu_init ':
: undefined reference to `__init_array_start'
/usr/lib/libc_nonshared.a(elf-init.oS)(.text+0x41): In function
`__libc_csu_init ':
: undefined reference to `__init_array_end'
/usr/lib/libc_nonshared.a(elf-init.oS)(.text+0xd1): In function
`__libc_csu_fini ':
: undefined reference to `__fini_array_start'
/usr/lib/libc_nonshared.a(elf-init.oS)(.text+0xd2): In function
`__libc_csu_fini ':
: undefined reference to `__fini_array_end'
/usr/lib/libc_nonshared.a(elf-init.oS)(.text+0xf0): In function
`__libc_csu_fini ':
: undefined reference to `__fini_array_start'
/usr/lib/libc_nonshared.a(elf-init.oS)(.text+0xf1): In function
`__libc_csu_fini ':
: undefined reference to `__fini_array_end'
I asked Intel and they said this was due to their not supporting glibc
2.3 yet, but I really would appreciate getting this to work again.
An important note is that the compiler _used_ to work just fine (even
with 2.3!) but one of the more recent updates to glibc broke it for me,
sometime between August 5th and August 11th, if I remember correctly.
Duraid
Matthew Wilcox wrote:
On Thu, Aug 21, 2003 at 08:30:08AM +1000, Duraid Madina wrote:
Hi all,
Is there a "Debian way" of installing multiple glibc(-dev) packages
simultaneously, so that I can enjoy my 'unstable' system (2.3) but
continue to use the Intel C/C++ compilers (which require 2.2.x)?
No there isn't. The 2.3 glibc packages should support any program
compiled against 2.2 though, what's broken?
(Other than the ABI problem reported at
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=204654 that is. Or the
possibly related ones at 202756 / 205328)
Reply to: