From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Using Buildroot generated toolchain on different machine without Buildroot environment
Date: Tue, 26 Jun 2012 17:58:10 +0200 [thread overview]
Message-ID: <20120626175810.5725388e@skate> (raw)
In-Reply-To: <jsclju$7qc$1@dough.gmane.org>
Le Tue, 26 Jun 2012 15:48:14 +0000 (UTC),
Grant Edwards <grant.b.edwards@gmail.com> a ?crit :
> Toolchains built with crosstool-ng can be moved anywhere, but all you
> end up with is the basic "libc" libraries. You'll have to copy the
> libraries built by buildroot manually if you want to use them on the
> other hosts.
Correct, but many things besides the toolchain contain hardcoded paths:
the pkg-config binary, the external toolchain wrapper, the .la files,
etc. See the report I mentioned for details.
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-06-26 15:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-26 15:05 [Buildroot] Using Buildroot generated toolchain on different machine without Buildroot environment Aleksandar Zivkovic
2012-06-26 15:19 ` Thomas Petazzoni
2012-06-26 15:48 ` Grant Edwards
2012-06-26 15:58 ` Thomas Petazzoni [this message]
2012-06-27 22:03 ` Aleksandar Zivkovic
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=20120626175810.5725388e@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.