From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 01/15] toolchain/helpers: add mandatory check for uclibc toolchain options
Date: Tue, 17 Mar 2015 11:13:10 -0300 [thread overview]
Message-ID: <55083676.6040000@zacarias.com.ar> (raw)
In-Reply-To: <20150314221850.GF4009@free.fr>
On 03/14/2015 07:18 PM, Yann E. MORIN wrote:
>> check_uclibc_feature = \
>> IS_IN_LIBC=`grep -q "\#define $(1) 1" $(3) && echo y` ; \
>> + if [ "$(2)" = "m" -a "$${IS_IN_LIBC}" != "y" ] ; then \
>
> With my proposal, that'd read:
>
> if [ -z "$(2)" -a "$${IS_IN_LIBC}" != "y" ] ; then \
>
> Otherwise, code looks good. :-)
>
> Regards,
> Yann E. MORIN.
Actually there's another scenario here, truth table!
If mandatory is true and the function is in libc the flow will go on,
hence doing the two other checks.
Problem is if parameter $2 is != 'y' and IS_IN_LIBC = 'y' then we've got
a problem (external toolchain with largefile and uclibc for example). So
resulting in:
-----
if [ -z "$(2)" ] ; then \
if [ "$${IS_IN_LIBC}" != "y" ] ; then \
echo "$(4) not available in C library, toolchain unsuitable for
Buildroot" ;
exit 1 ; \
fi ; \
else \
if [ "$($(2))" != "y" -a "$${IS_IN_LIBC}" = "y" ] ; then \
echo "$(4) available in C library, please enable $(2)" ; \
exit 1 ; \
fi ; \
if [ "$($(2))" = "y" -a "$${IS_IN_LIBC}" != "y" ] ; then \
echo "$(4) not available in C library, please disable $(2)" ; \
exit 1 ; \
fi ; \
fi
-----
Happens for not testing an uclibc lfs-enabled external toolchain :)
Regards.
next prev parent reply other threads:[~2015-03-17 14:13 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-13 18:21 [Buildroot] [PATCH 00/15] Drop non-largefile support Gustavo Zacarias
2015-03-13 18:22 ` [Buildroot] [PATCH 01/15] toolchain/helpers: add mandatory check for uclibc toolchain options Gustavo Zacarias
2015-03-14 22:18 ` Yann E. MORIN
2015-03-17 12:18 ` Gustavo Zacarias
2015-03-17 14:13 ` Gustavo Zacarias [this message]
2015-03-13 18:22 ` [Buildroot] [PATCH 02/15] toolchain/helpers: make LFS mandatory for uclibc Gustavo Zacarias
2015-03-14 22:22 ` Yann E. MORIN
2015-03-13 18:22 ` [Buildroot] [PATCH 03/15] toolchain-common: default to Y for LARGEFILE Gustavo Zacarias
2015-03-14 22:34 ` Yann E. MORIN
2015-03-13 18:22 ` [Buildroot] [PATCH 04/15] toolchain: remove LARGEFILE selects Gustavo Zacarias
2015-03-14 22:36 ` Yann E. MORIN
2015-03-17 15:11 ` Gustavo Zacarias
2015-03-13 18:22 ` [Buildroot] [PATCH 05/15] gcc/final: drop non-lfs builds Gustavo Zacarias
2015-03-13 18:22 ` [Buildroot] [PATCH 06/15] package infra: drop non-lfs support Gustavo Zacarias
2015-03-14 22:46 ` Yann E. MORIN
2015-03-13 18:22 ` [Buildroot] [PATCH 07/15] package/uclibc: drop non-largefile support Gustavo Zacarias
2015-03-14 22:47 ` Yann E. MORIN
2015-03-13 18:22 ` [Buildroot] [PATCH 08/15] configs: drop largefile option Gustavo Zacarias
2015-03-14 22:47 ` Yann E. MORIN
2015-03-13 18:22 ` [Buildroot] [PATCH 09/15] busybox: force lfs build Gustavo Zacarias
2015-03-14 22:49 ` Yann E. MORIN
2015-03-13 18:22 ` [Buildroot] [PATCH 10/15] system: drop largefile depends Gustavo Zacarias
2015-03-14 22:50 ` Yann E. MORIN
2015-03-13 18:22 ` [Buildroot] [PATCH 11/15] boot/gummiboot: " Gustavo Zacarias
2015-03-14 22:52 ` Yann E. MORIN
2015-03-13 18:22 ` [Buildroot] [PATCH 12/15] packages: remove (non-)lfs dependencies and tweaks Gustavo Zacarias
2015-03-13 18:22 ` [Buildroot] [PATCH 13/15] toolchain-common: drop BR2_LARGEFILE Gustavo Zacarias
2015-03-14 22:53 ` Yann E. MORIN
2015-03-13 18:22 ` [Buildroot] [PATCH 14/15] packages: remove non-lfs enabler patches Gustavo Zacarias
2015-03-13 18:22 ` [Buildroot] [PATCH 15/15] docs/manual: remove references to largefile Gustavo Zacarias
2015-03-14 22:56 ` Yann E. MORIN
2015-03-14 22:58 ` [Buildroot] [PATCH 00/15] Drop non-largefile support Yann E. MORIN
2015-03-17 12:23 ` Gustavo Zacarias
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=55083676.6040000@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--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