From: Li Liang <li.liang@neomeridian.com>
To: buildroot@busybox.net
Subject: [Buildroot] Error:"Staging_dir/lib/libc.so.0: could not read symbols:file in wrong format" while "make" buildroot with xscale, gcc-4.2.3
Date: Wed, 23 Apr 2008 01:04:15 +1000 [thread overview]
Message-ID: <1208876655.480dfe6f0bef5@www.server101.com> (raw)
I have struggled with this problem for few days. Actually I found a similar
subject in
http://busybox.net/lists/buildroot/2007-October/005854.html
However, I checked the mentioned patch in that thread, it actually applied to
the gcc-4.2.3. Unfortunately, the issue wasn't be solved. Moreover, I couldn't
find further useful info regarding to this problem. I really appreciate if
anyone could tell me the solution. If any further log or info could help to
diagnose this issue,please don't hesitate to ask me. Thank you very much in
advance.
~LL
next reply other threads:[~2008-04-22 15:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-22 15:04 Li Liang [this message]
2008-04-22 15:45 ` [Buildroot] Error:"Staging_dir/lib/libc.so.0: could not read symbols:file in wrong format" while "make" buildroot with xscale, gcc-4.2.3 Rex Ashbaugh
2008-04-23 3:38 ` Li Liang
2008-04-23 11:43 ` Hamish Moffatt
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=1208876655.480dfe6f0bef5@www.server101.com \
--to=li.liang@neomeridian.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