Skip to contentSkip to conversation

mipsel-ctng-linux-uclibc.config: add BR2_TOOLCHAIN_EXTERNAL_CXX=y

PATCH New Vicente Olivert Riera 2 participants 3 messages Mar 5, 2015

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 mipsel-ctng-linux-uclibc.config: add BR2_TOOLCHAIN_EXTERNAL_CXX=y

This external toolchain has C++ support, so add
BR2_TOOLCHAIN_EXTERNAL_CXX=y to the config file.

---
 .../configs/mipsel-ctng-linux-uclibc.config        |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)
web/toolchains/configs/mipsel-ctng-linux-uclibc.config +1 -0
index c6ad9fb..d0ac37e 100644
@@ -8,3 +8,4 @@ BR2_TOOLCHAIN_EXTERNAL_HEADERS_3_9=y
 BR2_TOOLCHAIN_EXTERNAL_LARGEFILE=y
 BR2_TOOLCHAIN_EXTERNAL_WCHAR=y
 BR2_TOOLCHAIN_EXTERNAL_HAS_SSP=y
+BR2_TOOLCHAIN_EXTERNAL_CXX=y
Signature · 1 line
1.7.1
#1 lore raw

PATCH 1/1 mipsel-ctng-linux-uclibc.config: add BR2_TOOLCHAIN_EXTERNAL_CXX=y

Dear Vicente Olivert Riera,

Quoted 7 lines · Vicente Olivert Riera

This external toolchain has C++ support, so add
BR2_TOOLCHAIN_EXTERNAL_CXX=y to the config file.

---
 .../configs/mipsel-ctng-linux-uclibc.config        |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

Applied, thanks.

Next time, can you include some special thing within the [PATCH ...] text to indicate that this patch is for buildroot-test and not Buildroot? I.e, use:

	git format-patch --subject-prefix="PATCH buildroot-test"

Otherwise it's a bit annoying to differentiate buildroot-test patches from other patches in patchwork.

Thanks!

Thomas

Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
#2 lore raw

PATCH 1/1 mipsel-ctng-linux-uclibc.config: add BR2_TOOLCHAIN_EXTERNAL_CXX=y

Hello Thomas,

Quoted 6 lines · Thomas Petazzoni

Dear Vicente Olivert Riera,

Quoted 3 lines · Vicente Olivert Riera

This external toolchain has C++ support, so add
BR2_TOOLCHAIN_EXTERNAL_CXX=y to the config file.

Quoted 6 lines
Quoted 4 lines
---
 .../configs/mipsel-ctng-linux-uclibc.config        |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

Applied, thanks.

thanks to you.

Quoted 8 lines

Next time, can you include some special thing within the [PATCH ...] text to indicate that this patch is for buildroot-test and not Buildroot? I.e, use:

	git format-patch --subject-prefix="PATCH buildroot-test"

Otherwise it's a bit annoying to differentiate buildroot-test patches from other patches in patchwork.

of course, no problem. I have sent many patches to buildroot-test, why didn't you tell me this before? :-)

Best wishes,
--
Vincent

Quoted 4 lines

Thanks!

Thomas