From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] BR2_UCLIBC_PROGRAM_INVOCATION symbol missing in external toolchain
Date: Fri, 31 Jul 2009 11:12:49 +0200 [thread overview]
Message-ID: <20090731111249.03cfdf87@surf> (raw)
In-Reply-To: <159a01660907310134l76b73595q634d30255cf8cf70@mail.gmail.com>
Le Fri, 31 Jul 2009 10:34:41 +0200,
Daniele Salvatore Albano <d.albano@gmail.com> a ?crit :
> some time ago i started to use buildroot to build a system for
> pc-appliances, but, for performance reason, i preferred to put glibc
> instead of uclibc. So, in these days, after some work, i finally
> managed to build a full toolchain using crosstool-NG. After a fresh
> checkout from buildroot git (i've seen some patches committed for
> external toolchains) i've seen, after that i disabled busybox, that i
> can't select some stuff because of WCHAR and/or PROGRAM_INVOCATION
> missing. Looking toolchain compile options i seen that
> PROGRAM_INVOCATION is missing! I've seen that the symbol called
> BR2_UCLIBC_PROGRAM_INVOCATION is only into toolchain/uClibc/Config.in
> and not in toolchain/external-toolchain/Config.in (and or
> Config.in.2).
>
> Is that config symbol only for uClibc? It should appears in external
> toolchains too or, however, packages that depends on this flag should
> check if external toolchain is used?
Correct, it should appear in external toolchains configurations, and be
checked like the other configuration options against the real
uClibc/glibc configuration.
I never saw it because I always use Busybox. I will try to make a patch
to fix it.
Thanks a lot for the report,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers and embedded Linux development,
consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2009-07-31 9:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-31 8:34 [Buildroot] BR2_UCLIBC_PROGRAM_INVOCATION symbol missing in external toolchain Daniele Salvatore Albano
2009-07-31 9:12 ` 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=20090731111249.03cfdf87@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox