On Fri, 03 Feb 2012 21:44:34 -0800 Bryan Kadzban <[email protected]> wrote:
> Andrew Benton wrote: > > But according to that bugzilla page, the bug was fixed weeks ago? The > > 'fix' is definitely in the glibc source so it would appear that it's > > not working. > > I assume that by this you mean you've verified that the right-hand side > of this diff is present in your git tree? > > http://sourceware.org/git/?p=glibc.git;a=commitdiff;h=8ecd6b2a1283a28bcf56cfe48099fafa412a3929 Indeed. > That *seems* like it should fix the issue. What does the installed > stdio.h look like? What happens if you do something like "/path/g++ -E > -D_GNU_SOURCE -Wp,-dU /usr/include/stdio.h"? (Assuming that's where the > stdio.h from this glibc build got installed, anyway.) /tools/include/stdio.h looks like this: http://www.linuxfromscratch.org/~andy/stdio.h > Do you get > __USE_ISOC11 #define'd (to what value?) or #undef'ed? What about > __cplusplus (again, what value)? > andy@eccles:/mnt/lfs/sources$ /tools/bin/x86_64-lfs-linux-gnu-gcc -E -D_GNU_SOURCE -Wp,-dU /tools/include/stdio.h | grep __USE_ISOC11 #define __USE_ISOC11 1 andy@eccles:/mnt/lfs/sources$ /tools/bin/x86_64-lfs-linux-gnu-gcc -E -D_GNU_SOURCE -Wp,-dU /tools/include/stdio.h | grep __cplusplus #undef __cplusplus I'm out of my depth here. Andy -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
