> El 21 ene 2016, a las 07:23, Gianfranco Costamagna
> <[email protected]> escribió:
>
> Hi, since gcc-6 is approaching, somebody did a test build with boinc,
> boinc-app-seti with the newly shiny gcc-6 (not stable yet).
>
>
> Lets start with boinc:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811947
>
>> ./sched_msgs.h:46:21: error: unable to find string literal operator
>> 'operator""x' with 'const char [6]', 'long unsigned int' arguments
>> #define _(x) "_(\""x"\")"
>
> I did this:
> -#define _(x) "_(\""x"\")"
> +#define _(x) "_(\"\"x\"\")"
>
>
> and now the build has completed
> (note: I'm not sure this is the correct way to fix it :) )
That completely changes the intended result of the macro. Your change will
always return the literal string _(""x"") instead of concatenating the value of
x.
Maybe adding spaces is enough to avoid having it interpreted as the new C++11
custom string literal operator:
#define _(x) "_(\"" x "\")"
which is also more readable.
I wonder if this is a gcc-6 bug though.
--
Nicolás
Sent from my bed
_______________________________________________
boinc_dev mailing list
[email protected]
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.
