Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] enabling libc.a generation
Date: Tue, 01 May 2012 10:28:46 +0200	[thread overview]
Message-ID: <4F9F9EBE.2070303@mind.be> (raw)
In-Reply-To: <4F9F819C.80509@scalemp.com>

On 05/01/12 08:24, Eial Czerwacki wrote:
> I have a little issue, while trying to compile a small file within a
> buildroot generated env, I get this:
> /usr/lib/gcc/i686-unknown-linux-uclibc/4.2.4/../../../../i686-unknown-linux-uclibc/bin/ld:
> cannot find -lc
> collect2: ld returned 1 exit status

  It would help if you at least specified the command you used to start 
the link.  You can also add the -v option to gcc to see the exact 
parameters of the call to ld, including the search path.

  libc.a and libc.so should be present in output/staging/usr/lib.  But I 
see you're calling a gcc in /usr...  Is this a compiler running on the 
target?  In that case, you should have libc.so and libc.a in /usr/lib.

  Regards,
  Arnout
-- 
Arnout Vandecappelle                               arnout at mind be
Senior Embedded Software Architect                 +32-16-286540
Essensium/Mind                                     http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium                BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  reply	other threads:[~2012-05-01  8:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-01  6:24 [Buildroot] enabling libc.a generation Eial Czerwacki
2012-05-01  8:28 ` Arnout Vandecappelle [this message]
2012-05-01  8:45   ` Eial Czerwacki
2012-05-04 19:55     ` Arnout Vandecappelle

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=4F9F9EBE.2070303@mind.be \
    --to=arnout@mind.be \
    --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