From: jacmet at uclibc.org <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/toolchain/external-toolchain
Date: Mon, 3 Nov 2008 02:37:28 -0800 (PST) [thread overview]
Message-ID: <20081103103728.0DA953C930@busybox.net> (raw)
Author: jacmet
Date: 2008-11-03 02:37:27 -0800 (Mon, 03 Nov 2008)
New Revision: 23910
Log:
External toolchain C++ cross-compiler fix
External toolchain C++ cross-compiler fix
package/Makefile.in resets CXX to "" in TARGET_CONFIGURE_OPTS if
BR2_GCC_CROSS_CXX is not set to 'y'. However, when using an external
toolchain, BR2_GCC_CROSS_CXX is not set even if the toolchain has a
C++ cross-compiler.
This patch adds a new BR2_GCC_CROSS_CXX option in the external
toolchain configuration menu, so that just like BR2_INET_RPC,
BR2_INET_IPV6 and the others, it can be set according to the external
toolchain configuration.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Modified:
trunk/buildroot/toolchain/external-toolchain/Config.in
Changeset:
Modified: trunk/buildroot/toolchain/external-toolchain/Config.in
===================================================================
--- trunk/buildroot/toolchain/external-toolchain/Config.in 2008-11-03 10:32:59 UTC (rev 23909)
+++ trunk/buildroot/toolchain/external-toolchain/Config.in 2008-11-03 10:37:27 UTC (rev 23910)
@@ -93,6 +93,12 @@
help
Set this option if the external toolchain supports soft float.
+config BR2_GCC_CROSS_CXX
+ bool "Toolchain has C++ cross-compiler ?"
+ help
+ Set this option if the external toolchain has a C++
+ cross-compiler.
+
config BR2_TARGET_OPTIMIZATION
string "Target Optimizations"
default "-Os -pipe"
next reply other threads:[~2008-11-03 10:37 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-03 10:37 jacmet at uclibc.org [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-01-12 12:54 [Buildroot] svn commit: trunk/buildroot/toolchain/external-toolchain laird at uclibc.org
2008-11-03 10:32 jacmet at uclibc.org
2008-10-17 10:19 jacmet at uclibc.org
2008-06-16 12:22 jacmet at uclibc.org
2008-06-16 13:54 ` Bernhard Fischer
2008-06-16 14:07 ` Peter Korsgaard
2008-06-16 15:35 ` Bernhard Fischer
2008-06-17 4:23 ` Hamish Moffatt
2008-06-17 7:16 ` Peter Korsgaard
2008-06-17 10:47 ` Hamish Moffatt
2008-06-17 13:45 ` Peter Korsgaard
2008-06-17 14:29 ` Bernhard Fischer
2008-06-17 14:55 ` Peter Korsgaard
2008-06-17 15:45 ` Bernhard Fischer
2008-06-18 1:18 ` Hamish Moffatt
2008-06-18 7:36 ` Peter Korsgaard
2008-06-18 1:05 ` Hamish Moffatt
2007-07-17 0:18 sjhill at uclibc.org
2007-04-28 17:10 sjhill at uclibc.org
2007-04-19 2:04 sjhill at uclibc.org
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=20081103103728.0DA953C930@busybox.net \
--to=jacmet@uclibc.org \
--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