Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Adam Nielsen <a.nielsen@shikadi.net>
To: buildroot@busybox.net
Subject: [Buildroot] buildroot still compiles C++ code when C++ compiler is unavailable
Date: Thu, 25 Apr 2013 14:46:05 +1000	[thread overview]
Message-ID: <klacea$3sl$1@ger.gmane.org> (raw)

Hi all,

After a successful build and changing some settings, I'm struggling to get a 
second successful build.  I had to select a newer version of GCC to avoid some 
segfaults, but now when compiling I get these errors:

checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking how to run the C++ preprocessor... /lib/cpp
configure: error: in 
`buildroot/build/gettext-0.18.2.1/gettext-runtime/libasprintf':
configure: error: C++ preprocessor "/lib/cpp" fails sanity check
See `config.log' for more details
configure: error: ./configure failed for libasprintf
configure: error: ./configure failed for gettext-runtime

According to Google it's because I don't have a C++ compiler installed, which 
is correct, I had originally compiled it, but then I deselected it in the 
buildroot config as the library was too big to fit in my device's flash memory.

I was assuming buildroot would now omit those packages that require C++, but 
it looks like I am wrong.  Is there an easy way to find out which packages 
depend on C++ and tell buildroot not to build them, now I have deselected C++ 
support?

Thanks,
Adam.

             reply	other threads:[~2013-04-25  4:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-25  4:46 Adam Nielsen [this message]
2013-04-25 13:31 ` [Buildroot] buildroot still compiles C++ code when C++ compiler is unavailable Thomas Petazzoni
2013-04-25 23:13   ` Adam Nielsen

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='klacea$3sl$1@ger.gmane.org' \
    --to=a.nielsen@shikadi.net \
    --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