FS#27579 - [lib32-glibc] please add symlink
Attached to Project:
Community Packages
Opened by Alexander F. Rødseth (xyproto) - Wednesday, 14 December 2011, 21:54 GMT
Last edited by Florian Pritz (bluewind) - Friday, 16 December 2011, 11:24 GMT
Opened by Alexander F. Rødseth (xyproto) - Wednesday, 14 December 2011, 21:54 GMT
Last edited by Florian Pritz (bluewind) - Friday, 16 December 2011, 11:24 GMT
|
Details
Hello,
Several Linux applications out there does not work without /lib/ld-lsb.so.3. Adding a symbolic link from /lib/ld-lsb.so.3 to /lib/ld-linux.so.2 solves the issue, and lets several applications (especially commercial ones, that are branded to be LSB-compatible) run without a hitch. The popularity of the ld-lsb package in AUR is a testament to how useful this is (498 votes right now). If this symbolic link was created by lib32-glibc, the "ld-lsb" AUR package [1] would no longer be needed to run (especially) commercial software. It's cheap and easy to implement and solves a lot of problems. All it would take, is: install -dm755 "$pkgdir/lib" ln -sf "/lib/ld-linux.so.2" "$pkgdir/lib/ld-lsb.so.3" Please consider this option. Thank you. [1] https://aur.archlinux.org/packages.php?ID=44043 |
This task depends upon
Closed by Florian Pritz (bluewind)
Friday, 16 December 2011, 11:24 GMT
Reason for closing: Won't implement
Friday, 16 December 2011, 11:24 GMT
Reason for closing: Won't implement
Also note that google-earth depends on ld-lsb, for example. The horrible, but popular, license management program "lmflex" (flexnet) also needs it.
You can also try asking glibc upstream, but judging from a blog post Ulrich wrote a while ago, which basically states that ldb is broken and useless, he won't include it either.
This alone would probably mean that the idea would be rejected. So, this would have to be introduced at a level closer to the user and further away from upstream.
Perhaps the ld-lsb package is the cleanest way after all. (Not that this should be needed in the first place, but, the reality of the situation makes it so).
On the other hand, this is only about a single file, /lib/ld-linux.so.2, which is only in the lib32-glibc package, and not in the regular glibc package.
I still think it would be a good idea to create the symlink in lib32-glibc, as it's Arch-specific enough and as it's only about that particular package.
If you still think it's a bad idea, just close this feature request, and I'll fully understand it.
Thanks.