Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] uClibc toolchain building issue
Date: Sun, 7 Jul 2013 18:43:30 -0300	[thread overview]
Message-ID: <20130707214327.GC5429@localhost> (raw)
In-Reply-To: <87ip0mgkeu.fsf@dell.be.48ers.dk>

On Sun, Jul 07, 2013 at 10:55:05PM +0200, Peter Korsgaard wrote:
> >>>>> "Ezequiel" == Ezequiel Garcia <ezequiel.garcia@free-electrons.com> writes:
> 
>  Ezequiel> Hello,
>  Ezequiel> I'm using today's origin/master HEAD to build my uClibc toolchain
>  Ezequiel> with the below config, and I found this error message:
> 
>  Ezequiel>   cp -f toolchain/uClibc/uClibc-0.9.33.config /home/zeta/buildroot/buildroot/output/build/uclibc-0.9.32.1/.config
>  Ezequiel>   cp: cannot stat ?toolchain/uClibc/uClibc-0.9.33.config?: No such file or directory
>  Ezequiel>   make: *** [/home/zeta/buildroot/buildroot/output/build/uclibc-0.9.32.1/.stamp_configured] Error 1
> 
>  Ezequiel> But a quick find tells me that the uClibc config is not in toolchain,
>  Ezequiel> but in package/uclibc, right?
> 
>  Ezequiel>   $ find . -name "uClibc*"
>  Ezequiel>   ./package/uclibc/uClibc-0.9.33.config
>  Ezequiel>   ./package/uclibc/uClibc-snapshot.config
>  Ezequiel>   ./package/uclibc/uClibc-0.9.32.config
> 
> Indeed, it recently got moved.
> 
>  Ezequiel> So, am I doing anything wrong or is this a bug?
> 
> I'm not sure I would call it a bug in buildroot. The problem is that the
> uClibc configuration file is given as a kconfig string variable, which
> defaults to the "standard" configuration file shipped with Buildroot.
> 
> The problem is that kconfig writes this value to the .config file, even
> though the user hasn't actively changed it, so if we move files around
> (and change the default for the string option), old .config files are
> not automatically updated and the build will fail.
> 
> Minimal config files (as output by make savedefconfig) don't have this
> problem as they only contain the lines that are changed from the
> default, which is why we recommend people use them (and use them
> ourselves for the defconfigs).
> 

Of course, this is no bug, it's just me forgetting to update the config
after the recent toolchain changes.

Thanks for the help,
-- 
Ezequiel Garc?a, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com

      reply	other threads:[~2013-07-07 21:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-07 20:29 [Buildroot] uClibc toolchain building issue Ezequiel Garcia
2013-07-07 20:55 ` Peter Korsgaard
2013-07-07 21:43   ` Ezequiel Garcia [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=20130707214327.GC5429@localhost \
    --to=ezequiel.garcia@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