Summary: | USE=static support broken for >=sys-fs/udev-0.44 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Sascha Silbe <sascha-gentoo-bugzilla> |
Component: | [OLD] Core system | Assignee: | Greg Kroah-Hartman (RETIRED) <gregkh> |
Status: | VERIFIED FIXED | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Sascha Silbe
2004-12-14 13:58:13 UTC
Where does /usr/src/linux point to? What version of the kernel is that symlink? The symlink points to the (fully configured and built) sources of the currently running 2.6.7 kernel: sascha@cube:/usr/src$ ls -l /usr/src/linux lrwxrwxrwx 1 root root 18 Aug 9 20:55 /usr/src/linux -> linux-2.6.7-cube-3 sascha@cube:/usr/src$ uname -a Linux cube 2.6.7-cube-3 #1 Sun Aug 1 14:46:56 CEST 2004 i686 AMD Athlon(tm) XP 1700+ AuthenticAMD GNU/Linux It's vanilla 2.6.7 + minor patches: sascha@cube:/usr/src$ cat linux-2.6.7-cube-3/PATCHES ftp://ftp.silbe.org/linux/kernel/v2.4/linux-2.4.23-enable_caps.patch ftp://ftp.silbe.org/linux/kernel/v2.6/user-mode-linux/host-skas3-2.6.7-v1.patch sascha@cube:/usr/src$ Odd, this really looks like a kernel directory that has not been set up properly. Can you duplicate this with udev 049? And if so, can you try it with a 2.6.9 kernel? Happens with a freshly built 2.6.9, too (even used genkernel this time). udev-049 makes no difference. I still got sys-kernel/linux-headers-2.4.21-r1 instead of sys-kernel/linux26-headers since I've still a 2.4 kernel floating around for testing purposes. Will try with linux26-headers now. Installing linux26-headers did not help. What is the output of the following two lines typed in on the command line: echo /lib/modules/`uname -r`/build ls /lib/modules/`uname -r`/build sascha@cube:~$ echo /lib/modules/`uname -r`/build /lib/modules/2.6.7-cube-3/build sascha@cube:~$ ls /lib/modules/`uname -r`/build /lib/modules/2.6.7-cube-3/build sascha@cube:~$ ls -l /lib/modules/2.6.7-cube-3/build lrwxrwxrwx 1 root root 27 Aug 6 12:09 /lib/modules/2.6.7-cube-3/build -> /usr/src/linux-2.6.7-cube-4 That's weird. So I probably forgot to adjust EXTRAVERSION in the Makefile when compiling this kernel. If I link /usr/src/linux to a clean, but fully built (i.e. unpacked, patched, compiled and installed) 2.6.9 source tree, udev still does not build. I'll try booting that new kernel and compiling udev again, but it should work even when linking against a kernel that's not currently running. OK, after I booted the kernel that /usr/src/linux links to, I could successfully build udev-045. So it appears udev cannot link statically against a kernel that's not currently running. :( BTW: udevstart is linked dynamically: root@cube:/tmp/x# ldd sbin/* sbin/scsi_id: not a dynamic executable sbin/udev: not a dynamic executable sbin/udevd: not a dynamic executable sbin/udevsend: not a dynamic executable sbin/udevstart: linux-gate.so.1 => (0xffffe000) libc.so.6 => /lib/libc.so.6 (0xb7ebc000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0xb7fea000) sbin/udev_volume_id: not a dynamic executable sbin/wait_for_sysfs: not a dynamic executable Try 051 release of udev. udevstart is statically linked for me. Statically linking udevstart still does not work for me:
root@cube:/tmp/sascha_silbe/x# ACCEPT_KEYWORDS='~x86' USE=static emerge -v --buildpkgonly sys-fs/udev
[...]
>>> Completed installing udev-052 into /var/tmp/portage/portage/udev-052/image/
[...]
root@cube:/tmp/sascha_silbe/x# tar -xjf /usr/portage/packages/All/udev-052.tbz2
bzip2: (stdin): trailing garbage after EOF ignored
root@cube:/tmp/sascha_silbe/x# ldd sbin/*
sbin/scsi_id:
not a dynamic executable
sbin/udev:
not a dynamic executable
sbin/udevd:
not a dynamic executable
sbin/udevsend:
not a dynamic executable
sbin/udevstart:
linux-gate.so.1 => (0xffffe000)
libc.so.6 => /lib/libc.so.6 (0xb7ebb000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0xb7fea000)
sbin/udev_volume_id:
not a dynamic executable
root@cube:/tmp/sascha_silbe/x#
PS: Should I file a new bug report about this?
Yes, please file a new bug and assign it to me. thanks. |