From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] problems building w/ external glibc toolchain
Date: Sat, 29 Jan 2011 09:50:38 +0100 [thread overview]
Message-ID: <20110129095038.11522bdb@surf> (raw)
In-Reply-To: <AANLkTi=LxaU-+wms053YX-BFrv3nQQod0mimafS7D=4K@mail.gmail.com>
Hello Bryce,
On Fri, 28 Jan 2011 16:23:30 -0800
Bryce Schober <bryce.schober@gmail.com> wrote:
> I've built an external glibc toolchain using crosstool-ng with old
> (2.6.29.6) linux kernel headers. I've already tested that the toolchain
> basically works, but buildroot fails just after building cross-depmod26.
> I've build with the --debug=v option, and it seems like it's trying to go
> fetch kernel headers, but doesn't know the kernel version. Looking into the
> configs and makefiles, it seems that the config variables for the kernel
> header versions are unsettable when using an external toolchain, yet
> buildroot is going out and trying to download them without knowing the
> version, eventually resulting in:
>
> Must remake target `/home/bschober/buildroot-2010.02/dl/linux-..tar.bz2'.
>
> Which is clearly never going to work. You'll noticed that this happened
> using buildroot-2010.02, but I've reproduced the same behavior on 2010.11
> and need to use the old version because I need Xorg 7.4.
Sounds strange. Could you post : your Buildroot .config, the complete
build log, and the list of commands you're using to trigger the
problem ?
Thanks,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2011-01-29 8:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-29 0:23 [Buildroot] problems building w/ external glibc toolchain Bryce Schober
2011-01-29 8:50 ` Thomas Petazzoni [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=20110129095038.11522bdb@surf \
--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.