Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Edwards <grant.b.edwards@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] preparing rootfs with gcc in buildroot
Date: Thu, 21 Jun 2012 21:24:31 +0000 (UTC)	[thread overview]
Message-ID: <js03ef$2qm$1@dough.gmane.org> (raw)
In-Reply-To: 4FE38489.8060803@mind.be

On 2012-06-21, Arnout Vandecappelle <arnout@mind.be> wrote:
> On 06/21/12 18:55, Grant Edwards wrote:
>> If you want to build things that use libraries that were built as part
>> of buildroot, then you have to add a couple more command line options
>> to tell the compiler/linker where to find the include and library
>> files created by buildroot (e.g.<wherever>/output/target.
>
> And even that is not necessary if you use output/host/usr/bin/xxx-gcc
> as the cross-compiler - that one has the sysroot hard-coded.

Right -- if you have buildroot build your compiler.  If you're using
an external compiler (e.g. one built separately with crosstool-ng),
you need to tell it where buildroot's libraries and include files are.

> By the way, you should point to <wherever>/output/staging, not
><wherever>/output/target.  target doesn't normally contain header
> files or static libraries.

Yup, my mistake.

-- 
Grant

  reply	other threads:[~2012-06-21 21:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-21 12:16 [Buildroot] preparing rootfs with gcc in buildroot Kevin Wilson
2012-06-21 12:28 ` Thomas Petazzoni
2012-06-21 16:38   ` Kevin Wilson
2012-06-21 16:55     ` Grant Edwards
2012-06-21 20:31       ` Arnout Vandecappelle
2012-06-21 21:24         ` Grant Edwards [this message]
2012-06-21 21:55           ` Thomas Petazzoni

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='js03ef$2qm$1@dough.gmane.org' \
    --to=grant.b.edwards@gmail.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