From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 847] New: Compiling target-gcc v4.4 fails with "libc.so.0: cannot open shared object file: No such file or directory"
Date: Fri, 8 Jan 2010 17:17:46 +0000 (UTC) [thread overview]
Message-ID: <bug-847-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=847
Host: Linux xxxxxxxx 2.6.32-gentoo-r1 #5 SMP PREEMPT Tue Jan 5
11:39:06 CET 2010 i686 Intel(R) Pentium(R) 4 CPU 3.00GHz
GenuineIntel GNU/Linux
Target: 686 + uClib
Summary: Compiling target-gcc v4.4 fails with "libc.so.0: cannot
open shared object file: No such file or directory"
Product: buildroot
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: blocker
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: belef at risx.net
CC: buildroot at uclibc.org
Estimated Hours: 0.0
Created an attachment (id=883)
--> (https://bugs.busybox.net/attachment.cgi?id=883)
output of target gcc(4.4) before stop
Something seems to go wrong in the depth of relative paths?
I could not find out, where the various Variations of relative paths is
generated.
BTW: uClibc-snapshot.tar.bz2 has no directory "uClibc-snapshot" in it, so I had
to repack/retar with link to uClibc ...
No way to find out, where this path "uClibc-snapshot/.unpacked" is really
generated.
wbr belef
att
--
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-01-08 17:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-08 17:17 bugzilla at busybox.net [this message]
2010-04-09 14:54 ` [Buildroot] [Bug 847] Compiling target-gcc v4.4 fails with "libc.so.0: cannot open shared object file: No such file or directory" bugzilla at busybox.net
2010-07-19 6:58 ` bugzilla at busybox.net
2010-07-27 21:29 ` 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-847-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