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: Fri, 26 Apr 2013 09:13:35 +1000	[thread overview]
Message-ID: <klcdas$3s8$1@ger.gmane.org> (raw)
In-Reply-To: <20130425153128.71c7c44f@skate>

Hi Thomas,

Many thanks for your reply!

>> 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
>
> However, did you do a complete 'make clean; make' cycle after disabling
> C++ support? Buildroot doesn't track the configuration changes you're
> making, so when you make a change as big in consequences as disabling
> C++, you should do a complete rebuild.

Ahh ok, well that makes more sense, but yes, I did do a 'make clean' as part 
of trying to solve the problem.  I have just done it again to make absolutely 
sure, and I'm still getting the same error.

I've uploaded my .config here if it will help:

   http://www.shikadi.net/files/buildroot/2013-04-26.gettext_cpp_fails.config

Let me know if you can figure out what I have done wrong!

Thanks again,
Adam.

      reply	other threads:[~2013-04-25 23:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-25  4:46 [Buildroot] buildroot still compiles C++ code when C++ compiler is unavailable Adam Nielsen
2013-04-25 13:31 ` Thomas Petazzoni
2013-04-25 23:13   ` Adam Nielsen [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='klcdas$3s8$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