From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv2] core: alternate solution to disable C++
Date: Sat, 07 Apr 2018 17:41:25 +0200 [thread overview]
Message-ID: <871sfrf2hm.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20180327110022.19980-1-yann.morin.1998@free.fr> (Yann E. MORIN's message of "Tue, 27 Mar 2018 13:00:22 +0200")
>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:
> Some packages that use libtool really need some love to be able to
> disable C++ support.
> This is because libtool will want to call AC_PROG_CXXCPP as soon as CXX
> is set non-empty to something different from 'no'. Then, AC_PROG_CXXCPP
> will want a C++ preprocessor that works on valid input *and* fail on
> invalid input.
> So, providing 'false' as the C++ compiler will then require that we do
> have a working C++ preprocessor. Which is totally counter-productive
> since we do not have a C++ compiler to start with...
> bd39d11d2e (core/infra: fix build on toolchain without C++) was a
> previous attempt at fixing this, by using the host's C++ preprocessor.
> However, that is very incorrect (that's my code, I can say so!) because
> the set of defines will most probably be different for the host and the
> target, thus causign all sorts of trouble. For example, on ARM we'd have
> to include different headers for soft-float vs hard-float, which is
> decided based on a macro, which is not defined for x86, and thus may
> redirect to the wrong (and missing) header.
> Instead, we notice that libtool uses the magic value 'no' to decide that
> a C++ compiler is not available, in which case it skeips the call to
> AC_PROG_CXXCPP.
> Given that 'no' is not provided by any package in Debian and
> derivatives, as well as in Fedora, we can assume that no system will
> have an executable called 'no'. Hence, we use that as a magic value to
> disable C++ detection altogether.
> Fixes: #10846 (again)
> Reported-by: Damien Riegel <damien.riegel@savoirfairelinux.com>
> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> Cc: Damien Riegel <damien.riegel@savoirfairelinux.com>
> Cc: Peter Seiderer <ps.report@gmx.net>
> Cc: Vivien Didelot <vivien.didelot@savoirfairelinux.com>
> Cc: Peter Korsgaard <peter@korsgaard.com>
> Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
> ---
> Changes v1 -> v2:
> - add big fat comment...
Committed to 2018.02.x, thanks.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2018-04-07 15:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-27 11:00 [Buildroot] [PATCHv2] core: alternate solution to disable C++ Yann E. MORIN
2018-03-27 12:04 ` Baruch Siach
2018-03-27 12:43 ` Thomas Petazzoni
2018-03-27 17:49 ` Yann E. MORIN
2018-03-27 19:40 ` Peter Seiderer
2018-03-28 22:08 ` Arnout Vandecappelle
2018-03-29 16:25 ` Peter Seiderer
2018-03-30 12:25 ` Peter Korsgaard
2018-03-31 6:25 ` Peter Korsgaard
2018-04-07 15:41 ` Peter Korsgaard [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=871sfrf2hm.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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