From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] rebuilding a project on older commits
Date: Sun, 27 Jan 2013 12:36:58 +0100 [thread overview]
Message-ID: <877gmydfhh.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20130127113309.4623b949@skate> (Thomas Petazzoni's message of "Sun, 27 Jan 2013 11:33:09 +0100")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
Hi,
>> Is it possible to move this existing toolchain outside buildroot or
>> should I rebuild from scratch?
Thomas> You should build it once with Crosstool-NG outside of Buildroot,
Thomas> install it somewhere, and tell Buildroot to use it as an external
Thomas> toolchain.
Building it inside Buildroot should also work (E.G. just set
BR2_HOST_DIR to some/place/elsewhere and use that directory as your
external toolchain dir).
>> For the first two points I can answer with yes, but your tip with the
>> /lib folder is the right one. This folder is empty, and this also in
>> the output/target directory so it must be empty in the rootfs.tar too.
>>
>> So the libraries in the /lib folder are missing there must be
>> something wrong with the config of the ct-ng? Any suggestions where I
>> have to look to?
Thomas> That sounds really odd. Maybe we have a bug in the ct-ng
Thomas> backend, and it doesn't copy the libraries? I would have to do
Thomas> a test build, but I'm on the battery in the train for now, so I
Thomas> can't do heavy builds for now.
It sounds like this:
commit de1eb105a45f88d8c6bf0e00f9b878a36114a5c1
Author: Floris Bos <bos@je-eigen-domein.nl>
Date: Sat Jan 5 19:11:45 2013 +0000
Fix installation of crosstool-ng libraries to target
When using the crosstool-ng toolchain option, the libc libraries were not
installed to target. Buildroot calls the show-tuple function to determine
the directory to copy from, and it seems that outputs the result to stderr
instead of stdout
Signed-off-by: Floris Bos <bos@je-eigen-domein.nl>
Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
I don't quite recall when the problem was introduced, but if it's
present in 2012.11, this would certainly be a candidate for 2012.11.2.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2013-01-27 11:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-26 17:57 [Buildroot] rebuilding a project on older commits Carsten Schoenert
2013-01-27 8:30 ` Thomas Petazzoni
2013-01-27 9:11 ` Carsten Schoenert
2013-01-27 10:33 ` Thomas Petazzoni
2013-01-27 11:24 ` Stephan Hoffmann
2013-01-27 11:36 ` Peter Korsgaard [this message]
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=877gmydfhh.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--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