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#43227 - [busybox] the binary should be statically linked
Attached to Project:
Community Packages
Opened by Xyne (Xyne) - Friday, 26 December 2014, 00:41 GMT
Last edited by Sergej Pupykin (sergej) - Thursday, 26 February 2015, 18:04 GMT
Opened by Xyne (Xyne) - Friday, 26 December 2014, 00:41 GMT
Last edited by Sergej Pupykin (sergej) - Thursday, 26 February 2015, 18:04 GMT
|
DetailsThe busybox executable is not statically linked:
$ ldd /usr/bin/busybox linux-vdso.so.1 (0x00007fff317fe000) libm.so.6 => /usr/lib/libm.so.6 (0x00007fcb51f69000) libc.so.6 => /usr/lib/libc.so.6 (0x00007fcb51bc6000) /lib64/ld-linux-x86-64.so.2 (0x00007fcb5226e000) This severely limits the utility of the executable for recovery on a live system. Compare to the binaries provided directly from upstream (http://busybox.net/downloads/binaries/latest/): $ ldd busybox-x86_64 not a dynamic executable Can the package be updated to provide a statically linked version? Sorry if this has already been answered. |
This task depends upon