Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#22070 - [udev] 164-3 doesn't contain the needed link /lib/libudev.so
Attached to Project:
Arch Linux
Opened by Maurel (guy-kde) - Sunday, 12 December 2010, 14:50 GMT
Last edited by Tobias Powalowski (tpowa) - Wednesday, 26 January 2011, 21:14 GMT
Opened by Maurel (guy-kde) - Sunday, 12 December 2010, 14:50 GMT
Last edited by Tobias Powalowski (tpowa) - Wednesday, 26 January 2011, 21:14 GMT
|
DetailsDescription:
the package udev 164-3 doesn't contain the needed link /lib/libudev.so |
This task depends upon
Closed by Tobias Powalowski (tpowa)
Wednesday, 26 January 2011, 21:14 GMT
Reason for closing: Won't implement
Wednesday, 26 January 2011, 21:14 GMT
Reason for closing: Won't implement
Workaround: I done the symbolic link myself
It was present at least at version 162
as libxyz.so
Most of the libraries have also 3 inodes, ie.
lrwxrwxrwx 1 root root 18 28. Mai 2010 libshadow.so -> libshadow.so.0.0.0
lrwxrwxrwx 1 root root 18 28. Mai 2010 libshadow.so.0 -> libshadow.so.0.0.0
-rwxr-xr-x 1 root root 62138 28. Mai 2010 libshadow.so.0.0.0
The libudev.so at version 164 has only 2 inodes.
The ld-command cannot work.
ld works quite fine btw:
$ cat > "test.c" << "EOF"
> int main() {
> return 0;
> }
> EOF
$ gcc -o test test.c -Wall -ludev
$ ldd test
linux-vdso.so.1 => (0x00007fffcfff9000)
libudev.so.0 => /lib/libudev.so.0 (0x00007feb366be000)
libc.so.6 => /lib/libc.so.6 (0x00007feb36361000)
/lib/ld-linux-x86-64.so.2 (0x00007feb368cb000)
$
I found a difference between the versions 163-1-x86_64 and 164-3-x86_64, as one can see below:
$ pacman -Q -l -p /var/cache/pacman/pkg/udev-163-1-x86_64.pkg.tar.xz | grep libudev.so
udev /lib/libudev.so
udev /lib/libudev.so.0
udev /lib/libudev.so.0.9.1
$ pacman -Q -l -p /var/cache/pacman/pkg/udev-164-3-x86_64.pkg.tar.xz | grep libudev.so
udev /lib/libudev.so.0
udev /lib/libudev.so.0.9.3
udev /usr/lib/libudev.so
The file libudev.so has changes the directory from /lib to /usr/lib, as written at the first comment
Is it an packaging error or a new feature, beginning at the version 164-3?
This was probably caused by us, changing configure from --prefix=/ to --prefix=/usr, if I read the udev Makefile right. This is intended behaviour by upstream udev developers.
I used cmake to prepare kdelibs.
The next day I made a pacman -Su
I got without take care of it, the version 164-3 of udev
Tried to "make" and got the ld-problem
If this was "really" intended, I hope that some people had a good use of that change.
I found it not very pretty.
If cmake generate such new files, all the .o and libraries will needed to be build at new.
It takes lot of time for a so little change! I don't see now the advantage of the change,
my view might be to small.
Thanks for helping.