From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] rebuilding a project on older commits
Date: Sun, 27 Jan 2013 11:33:09 +0100 [thread overview]
Message-ID: <20130127113309.4623b949@skate> (raw)
In-Reply-To: <5104EF52.3010608@googlemail.com>
Dear Carsten Schoenert,
On Sun, 27 Jan 2013 10:11:46 +0100, Carsten Schoenert wrote:
> Yes, this is the solution. Right now I build the toolchain with ct-ng
> inside buildroot.
> Is it possible to move this existing toolchain outside buildroot or
> should I rebuild from scratch?
You should build it once with Crosstool-NG outside of Buildroot,
install it somewhere, and tell Buildroot to use it as an external
toolchain.
> 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?
That sounds really odd. Maybe we have a bug in the ct-ng backend, and
it doesn't copy the libraries? I would have to do a test build, but I'm
on the battery in the train for now, so I can't do heavy builds for now.
If someone could do a quick test build of a minimal system that uses
the ct-ng backend, and verify that $(O)/target/lib contains the right
libraries, that would be nice.
Best regards,
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:[~2013-01-27 10:33 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 [this message]
2013-01-27 11:24 ` Stephan Hoffmann
2013-01-27 11:36 ` Peter Korsgaard
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=20130127113309.4623b949@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