From: softa at ttechgroup.com <softa@ttechgroup.com>
To: buildroot@busybox.net
Subject: [Buildroot] x86_64 , cannot find /lib/libc.so.0
Date: Fri, 29 Jun 2007 11:32:00 +0300 [thread overview]
Message-ID: <005501c7ba27$f69e7860$6614a8c0@softalap> (raw)
In-Reply-To: 20070629082320.GE8033@aon.at
Hi,
i have the same problem, if someone gives to me short instructions what/how
to do, i will try to make it.
Assen
----- Original Message -----
From: "Bernhard Fischer" <rep.dot.nop@gmail.com>
To: "Lee JJ" <jengjr@gmail.com>
Cc: <buildroot@uclibc.org>
Sent: Friday, June 29, 2007 11:23 AM
Subject: Re: [Buildroot] x86_64 , cannot find /lib/libc.so.0
> On Fri, Jun 29, 2007 at 03:20:35PM +0800, Lee JJ wrote:
>>/root/buildroot/build_x86_64/staging_dir/usr/x86_64-linux-uclibc/bin/ld:
>>skipping incompatible /root/buildroot/build_x86_64/s
>>taging_dir/lib/libc.so.0 when searching for /lib/libc.so.0
>>/root/buildroot/build_x86_64/staging_dir/usr/x86_64-linux-uclibc/bin/ld:
>>cannot
>>find /lib/libc.so.0 inside /root/buildroot/bu
>>ild_x86_64/staging_dir
>>collect2: ld returned 1 exit status
>>make[4]: *** [32/libgcc_s.so] Error 1
>>
>># ls build_x86_64/staging_dir/lib/libc.so.0 -lt
>>lrwxrwxrwx 1 root root 19 Jun 28 15:11
>>build_x86_64/staging_dir/lib/libc.so.0 -> libuClibc-0.9.29.so
>>
>>But the file do exist !??
> 'skipping incompatible' != 'ENOENT'
>
> Patches to fix multilib support are welcome.
> _______________________________________________
> buildroot mailing list
> buildroot at uclibc.org
> http://busybox.net/mailman/listinfo/buildroot
prev parent reply other threads:[~2007-06-29 8:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-29 7:20 [Buildroot] x86_64 , cannot find /lib/libc.so.0 Lee JJ
2007-06-29 8:23 ` Bernhard Fischer
2007-06-29 8:32 ` softa at ttechgroup.com [this message]
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='005501c7ba27$f69e7860$6614a8c0@softalap' \
--to=softa@ttechgroup.com \
--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