manual/configure.txt: fix typo
PATCH v2 1/1 manual/configure.txt: fix typo
---
v2:
- remove only one backslash
docs/manual/configure.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
docs/manual/configure.txt +1 -1
@@ -165,7 +165,7 @@ Then, you have three solutions to use an external toolchain: prefix+ and +External toolchain C library+ options. Then, you have to tell Buildroot what your external toolchain supports. If your external toolchain uses the 'glibc' library, you only have to tell - whether your toolchain supports C\+\+ or not and whether it has + whether your toolchain supports C\++ or not and whether it has built-in RPC support. If your external toolchain uses the 'uClibc' library, then you have to tell Buildroot if it supports largefile, IPv6, RPC, wide-char, locale, program invocation, threads and
Signature · 1 line
1.7.9.5
PATCH v2 1/1 manual/configure.txt: fix typo
Dear Jerzy Grzegorek,
Quoted 1 line · Jerzy Grzegorek
Signed-off-by Jerzy Grzegorek <[email protected]>
This patch does not apply. Additionally, I believe in fact using C\++ is not needed: there are many occurrences of just "C++" that work perfectly fine.
Can you cook a patch, that applies on the latest master, which makes sure we just use C++ everywhere?
Thanks,
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com
PATCH v2 1/1 manual/configure.txt: fix typo
Thomas Petazzoni <[email protected]> schreef:
Quoted 11 lines
Dear Jerzy Grzegorek,
Quoted 1 line · Jerzy Grzegorek
Signed-off-by Jerzy Grzegorek <[email protected]>This patch does not apply. Additionally, I believe in fact using C\++ is not needed: there are many occurrences of just "C++" that work perfectly fine.
Can you cook a patch, that applies on the latest master, which makes sure we just use C++ everywhere?
Make sure to test this properly. I added these escapes for a real reason.