Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Libraries built with buildroot can only be used by buildroot itself.
Date: Tue, 30 Jul 2013 11:19:15 +0200	[thread overview]
Message-ID: <20130730111915.2d2f00d9@skate> (raw)
In-Reply-To: <20130730085749.GA12392@zuhnb712.ap.bm.net>

Dear Woody Wu,

On Tue, 30 Jul 2013 16:57:49 +0800, Woody Wu wrote:

> > So the behavior you are seeing is expected. You should always use the
> > toolchain through output/host/usr/bin/.
> 
> Okay, Thomas.  But I found fully copy of output/host/usr/bin (just in
> another directory) also does not work.  Is this also expected behavior?

Copying output/host/usr/bin alone doesn't make any sense because
you're moving the compiler and other tools but not the sysroot. Copying
the entire output/host directory elsewhere would make more sense, but
unfortunately, Buildroot doesn't support a relocatable sysroot for now.
So you should *not* move this directory.

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2013-07-30  9:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-30  4:40 [Buildroot] Libraries built with buildroot can only be used by buildroot itself Woody Wu
2013-07-30  4:54 ` Alexander Lukichev
2013-07-30  9:00   ` Woody Wu
2013-07-30  6:22 ` Thomas De Schampheleire
2013-07-30  8:57   ` Woody Wu
2013-07-30  9:19     ` Thomas Petazzoni [this message]
2013-07-31  8:57       ` Woody Wu

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=20130730111915.2d2f00d9@skate \
    --to=thomas.petazzoni@free-electrons.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