Skip to contentSkip to conversation

klibc: type of symbol changed warning

DISCUSSION Martin Hicks 1 participant 3 messages Nov 25, 2003

lore
Share & tools
lore
#0 lore raw

Hello,

I've been trying to get klibc working on ia64. I'm running into a problem while compiling it. I get a warning during the final link:

gcc --static --nostdlib -nostartfiles -o udev klibc/klibc/crt0.o udev.o udev-add.o udev-remove.o udevdb.o logging.o namedev.o libsysfs/sysfs_bus.o libsysfs/sysfs_class.o libsysfs/sysfs_device.o libsysfs/sysfs_dir.o libsysfs/sysfs_driver.o libsysfs/sysfs_utils.o libsysfs/dlist.o tdb/tdb.o tdb/spinlock.o klibc/klibc/libc.a /usr/lib/gcc-lib/ia64-linux/3.3.2/libgcc.a

/usr/bin/ld: Warning: type of symbol `errno' changed from 1 to 6 in /usr/lib/gcc-lib/ia64-linux/3.3.2/../../../libc.a(errno.o)

Whatever causing this is also messing up other stuff. The __ctypes array, which is used by many of the ctype.h functions is not in the right place in the final udev executable.

The fix that I've found is to do the final link with ld instead of gcc.

Anyone know what's causing this problem?
thanks
mh

Signature · 2 lines
Martin Hicks                Wild Open Source Inc.
[email protected]     613-266-2296
#1 lore raw
Quoted 4 lines · Martin Hicks

Hello,

I've been trying to get klibc working on ia64. I'm running into a problem while compiling it. I get a warning during the final link:

Sorry,

This is what happens while compiling udev against klibc. The klibc seems to work fairly well for most other things contained in the klibc tarball (ash, minimal gzip/gunzip, etc)

mh

Signature · 2 lines
Martin Hicks                Wild Open Source Inc.
[email protected]     613-266-2296
#2 lore raw
In reply to Martin Hicks
Quoted 7 lines · Martin Hicks
Quoted 4 lines · Martin Hicks

Hello,

I've been trying to get klibc working on ia64. I'm running into a problem while compiling it. I get a warning during the final link:

Quoted 5 lines

Sorry,

This is what happens while compiling udev against klibc. The klibc seems to work fairly well for most other things contained in the klibc tarball (ash, minimal gzip/gunzip, etc)

Adding -nodefaultlibs to LDFLAGS seems to have solved this problem. Thanks to willy for giving me the hint that allowed me to figure this out.

mh

Signature · 2 lines
Martin Hicks                Wild Open Source Inc.
[email protected]     613-266-2296