Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH RFC] core/infra: fix build on toolchain without C++
Date: Mon, 08 Jan 2018 22:52:52 +0100	[thread overview]
Message-ID: <87mv1onhl7.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20180103173952.10834-1-yann.morin.1998@free.fr> (Yann E. MORIN's message of "Wed, 3 Jan 2018 18:39:52 +0100")

>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:

 > Autotools-based packages that do not need C++ but check for it, and use
 > libtool, will fail to configure on distros that lack /lib/cpp.

 > This is the case for example on Arch Linux, where expat fails to build
 > with:

 >     configure: error: in `/home/dkc/src/buildroot/build/build/expat-2.2.4':
 >     configure: error: C++ preprocessor "/lib/cpp" fails sanity check

 > This is because libtool uses AC_PROC_CXXCPP, which can not be avoided,
 > and does require a cpp that passes some "sanity" checks (does not choke
 > on valid input, but does choke on invalid input). So we can use neither
 > /bin/false nor /bin/true...

 > We instead need something that can digest some basic C++ preprocessor
 > input. We can't use the target preprocessor: that does not work, because
 > it obviously has no C++ cupport:

 >     arm-linux-cpp.br_real: error: conftest.cpp: C++ compiler not
 >     installed on this system

 > We can however consider that the host machine does have a C++ compiler,
 > so we use the host' cpp, which is gcc's compiler wrapper that ends up
 > calling the host's C++ preprocessor.

 > That would give us a valid C++ preprocessor when we don't have one, in
 > fact. But autotools will then correctly fail anyway, because there is
 > indeed no C++ compiler at all, as we can see in this excerpt of a
 > configure log from expat:

 >     checking whether we are using the GNU C++ compiler... no
 >     checking whether false accepts -g... no
 >     checking dependency style of false... none
 >     checking how to run the C++ preprocessor... cpp
 >     checking whether the false linker (/home/ymorin/dev/buildroot/O/host/bin/arm-linux-ld) supports shared libraries... yes
 >     libtool.m4: error: problem compiling CXX test program
 >     checking for false option to produce PIC...  -DPIC
 >     checking if false PIC flag  -DPIC works... no
 >     checking if false static flag  works... no
 >     checking if false supports -c -o file.o... no
 >     checking if false supports -c -o file.o... (cached) no
 >     checking whether the false linker (/home/ymorin/dev/buildroot/O/host/bin/arm-linux-ld) supports shared libraries... yes

 > So, using the host's C++ preprocessor (by way of gcc's wrapper) leads to
 > a working situation, where the end result is as expected.

 > 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: Vivien Didelot <vivien.didelot@savoirfairelinux.com>
 > Cc: Peter Korsgaard <peter@korsgaard.com>
 > Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>

Committed to 2017.11.x, thanks.

-- 
Bye, Peter Korsgaard

  parent reply	other threads:[~2018-01-08 21:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-03 17:39 [Buildroot] [PATCH RFC] core/infra: fix build on toolchain without C++ Yann E. MORIN
2018-01-07 14:58 ` Thomas Petazzoni
2018-01-08 21:52 ` Peter Korsgaard [this message]
2018-01-30 12:21 ` Peter Korsgaard

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=87mv1onhl7.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