[Bug 11136] New: extraneous ld scripts in official busybox-1.29.0.tar.bz2 tarball?
bugzilla at busybox.net
bugzilla at busybox.net
Mon Jul 2 13:47:37 UTC 2018
https://bugs.busybox.net/show_bug.cgi?id=11136
Bug ID: 11136
Summary: extraneous ld scripts in official
busybox-1.29.0.tar.bz2 tarball?
Product: Busybox
Version: 1.29.x
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at busybox.net
Reporter: balducci at units.it
CC: busybox-cvs at busybox.net
Target Milestone: ---
Created attachment 7661
--> https://bugs.busybox.net/attachment.cgi?id=7661&action=edit
configuration file
hello
my build of 1.29.0 (from official tarball
https://busybox.net/downloads/busybox-1.29.0.tar.bz2) stops with:
----8<----
attempt to open
/opt/stow.d/versions/gcc-8.1.0/usr/lib64/gcc/x86_64-pc-linux-gnu/8.1.0/../../../libresolv.a
failed/usr/bin/ld: skipping incompatible /usr/lib/../lib64/libm.a when
searching for -lm
/usr/bin/ld: cannot find -lm
/usr/bin/ld: skipping incompatible /usr/lib/../lib64/libresolv.a when
searching for -lresolv
/usr/bin/ld: cannot find -lresolv
collect2: error: ld returned 1 exit status
make[1]: *** [Makefile:718: busybox_unstripped] Error 1
make[1]: Leaving directory
'/home/balducci/tmp/install-us-d/busybox-1.28.4.d/busybox-1.29.0'
---->8----
AFAICS, the reason is the presence of 3 ld scripts which (it looks to
me) shouldn't be there:
busybox_ldscript
busybox_ldscript_bss
busybox_ldscript_nobss
The failure is because the ld scripts are (apparently) for a 32 bit
machine:
----8<----
#:2> head busybox_ldscript
/* Script for -z combreloc: combine and sort reloc sections */
OUTPUT_FORMAT("elf32-i386", "elf32-i386",
"elf32-i386")
OUTPUT_ARCH(i386)
ENTRY(_start)
SECTIONS
{
/* Read-only sections, merged into text segment: */
PROVIDE (__executable_start = 0x08048000); . = 0x08048000 +
SIZEOF_HEADERS;
.interp : { *(.interp) }
---->8----
where my box is 64 bit
As a matter of fact, removing the scripts makes the build complete
successfully.
ciao
-gabriele
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the busybox-cvs
mailing list