From: Jerry Richards <jerryr@tonecommander.com>
To: buildroot@busybox.net
Subject: [Buildroot] Compilation Error Using Buildroot
Date: Wed, 26 Sep 2007 13:03:52 -0700 [thread overview]
Message-ID: <001801c80078$5d2cc5f0$2c48a8c0@greyhawk.tonecommander.com> (raw)
Hello All
I am using buildroot for a MIPS processor and encountered a compilation
error in an application module I added to the build environment (see build
output excerpt attachment). It states "./.libs/libsu.a: could not read
symbols: Archive has no index; run ranlib to add one", yet a couple of lines
earlier shows "ranlib .libs/libsu.a" already executed.
Could someone take a quick look at this? I don't see how GCC gets this
error. Perhaps there is some configuration option missing?
Best Regards,
Jerry
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: CompilerError.txt
Url: http://busybox.net/lists/buildroot/attachments/20070926/61a6c4cc/attachment.txt
next reply other threads:[~2007-09-26 20:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-26 20:03 Jerry Richards [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-09-26 20:41 [Buildroot] Compilation Error Using Buildroot Jerry Richards
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='001801c80078$5d2cc5f0$2c48a8c0@greyhawk.tonecommander.com' \
--to=jerryr@tonecommander.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