From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 2971] New: rootfs lacks /lib64 directory for 64 bits arch
Date: Wed, 15 Dec 2010 15:58:53 +0000 (UTC) [thread overview]
Message-ID: <bug-2971-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=2971
Summary: rootfs lacks /lib64 directory for 64 bits arch
Product: buildroot
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: major
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: bardon.pro at gmail.com
CC: buildroot at uclibc.org
Estimated Hours: 0.0
bug version: Buildroot-2010.11 (does not exists in version field).
When x86_64/generic (Crosstool-NG toolchain, glibc) architecture is chosen
compiled executables expect to have pure 64 bit libs in lib64 :
/src/buildroot-2010.11$ ldd output/target/bin/bash
linux-vdso.so.1 => (0x00007fff50fff000)
libncurses.so.5 => /lib/libncurses.so.5 (0x00007fe7f6c2b000)
libdl.so.2 => /lib/libdl.so.2 (0x00007fe7f6a27000)
libc.so.6 => /lib/libc.so.6 (0x00007fe7f66d4000)
/lib64/ld-linux-x86-64.so.2 (0x00007fe7f6e6a000)
ld-linux-x86-64.so.2 is located in /lib.
Need to have a link from lib64 to lib in fs/skeleton :
cd fs/skeleton
ln -s /lib lib64
4 drwxr-xr-x 16 andromede andromede 4096 d?c 15 16:51 .
4 drwxr-xr-x 14 andromede andromede 4096 nov 30 16:52 ..
4 drwxr-xr-x 2 andromede andromede 4096 nov 30 16:52 bin
4 drwxr-xr-x 3 andromede andromede 4096 nov 30 16:52 dev
4 drwxr-xr-x 5 andromede andromede 4096 nov 30 16:52 etc
4 drwxr-xr-x 2 andromede andromede 4096 nov 30 16:52 home
4 drwxr-xr-x 2 andromede andromede 4096 nov 30 16:52 lib
0 lrwxrwxrwx 1 andromede andromede 4 d?c 15 16:51 lib64 -> /lib
4 drwxr-xr-x 2 andromede andromede 4096 nov 30 16:52 mnt
4 drwxr-xr-x 2 andromede andromede 4096 nov 30 16:52 opt
4 drwxr-xr-x 2 andromede andromede 4096 nov 30 16:52 proc
4 drwxr-xr-x 2 andromede andromede 4096 nov 30 16:52 root
4 drwxr-xr-x 2 andromede andromede 4096 nov 30 16:52 sbin
4 drwxr-xr-x 2 andromede andromede 4096 nov 30 16:52 sys
4 drwxr-xr-x 2 andromede andromede 4096 nov 30 16:52 tmp
4 drwxr-xr-x 6 andromede andromede 4096 nov 30 16:52 usr
4 drwxr-xr-x 3 andromede andromede 4096 nov 30 16:52 var
refs:
GCC 4.3.5
Glibc 2.11.1
(generated by Crosstool-NG 1.9)
target is Intel x86_64.
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2010-12-15 15:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-15 15:58 bugzilla at busybox.net [this message]
2011-01-14 15:46 ` [Buildroot] [Bug 2971] rootfs lacks /lib64 directory for 64 bits arch bugzilla at busybox.net
2011-02-03 13:24 ` bugzilla at busybox.net
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-2971-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox