| Message ID | 1396216393-9841-1-git-send-email-jerzy.grzegorek@trzebnica.net |
|---|---|
| State | Not Applicable |
| Headers | show |
Dear Jerzy Grzegorek,
On Sun, 30 Mar 2014 23:53:13 +0200, Jerzy Grzegorek wrote:
> Signed-off-by: Jerzy Grzegorek <jerzy.grzegorek@trzebnica.net>
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
Thomas Petazzoni <thomas.petazzoni@free-electrons.com> schreef: >Dear Jerzy Grzegorek, > >On Sun, 30 Mar 2014 23:53:13 +0200, Jerzy Grzegorek wrote: >> Signed-off-by: Jerzy Grzegorek <jerzy.grzegorek@trzebnica.net> > >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.
diff --git a/docs/manual/configure.txt b/docs/manual/configure.txt index c1c9477..6ab0c37 100644 --- a/docs/manual/configure.txt +++ b/docs/manual/configure.txt @@ -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
Signed-off-by: Jerzy Grzegorek <jerzy.grzegorek@trzebnica.net> --- v2: - remove only one backslash docs/manual/configure.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)