On Wed, Jan 30, 2002 at 06:40:19PM +0900, Jun-ichiro itojun Hagino wrote:
> 	make build has been failing for me in gcc/lib/libobjc.  does anyone
> 	have similar problem?  the offending line (machine/ansi.h) looks okay
> 	to me.  i've checked out the tree couple of hours ago, and made sure
> 	i have the fresh toolchain.

I see the exact same problem doing a full build on a pristine
source tree.

/Niels Chr.


> >typedef union {
> >        char __mbstate8[128];
> >        __int64_t __mbstateL;   /* for alignment */
> >} __mbstate_t;
> >#define _BSD_MBSTATE_T_         __mbstate_t     /* mbstate_t */
> 
> itojun
> 
> 
> dependall ===> libobjc
> /usr/tool/bin/i386--netbsdelf-gcc -O2   -Werror  -I. -I/usr/home/itojun/NetBSD/src/gnu/lib/libobjc/../../usr.bin/gcc/arch/i386 -DIN_GCC -I/usr/home/itojun/NetBSD/src/gnu/lib/libobjc/../../dist/toolchain/libobjc -I/usr/home/itojun/NetBSD/src/gnu/lib/libobjc/../../dist/toolchain/libobjc/objc -I/usr/home/itojun/NetBSD/src/gnu/lib/libobjc/../../dist/toolchain/libobjc/../gcc -I/usr/home/itojun/NetBSD/src/gnu/lib/libobjc/../../dist/toolchain/libobjc/../gcc/config -I/usr/home/itojun/NetBSD/src/gnu/lib/libobjc/../../dist/toolchain/libobjc/../include -nostdinc -isystem /usr/include  -c /home/itojun/NetBSD/src/gnu/lib/libobjc/../../dist/toolchain/libobjc/NXConstStr.m
> In file included from /usr/include/stddef.h:41,
>                  from /usr/home/itojun/NetBSD/src/gnu/lib/libobjc/../../dist/toolchain/libobjc/objc/objc.h:34,
>                  from /usr/home/itojun/NetBSD/src/gnu/lib/libobjc/../../dist/toolchain/libobjc/objc/Object.h:30,
>                  from /home/itojun/NetBSD/src/gnu/lib/libobjc/../../dist/toolchain/libobjc/objc/NXConstStr.h:31,
>                  from /home/itojun/NetBSD/src/gnu/lib/libobjc/../../dist/toolchain/libobjc/NXConstStr.m:28:
> /usr/include/machine/ansi.h:94: parse error before `union'
> i386--netbsdelf-gcc: Internal compiler error: program cc1obj got fatal signal 11
> *** Error code 1
> 
> Stop.
> 

-- 
 Niels Christian Bank-Pedersen, NCB1-RIPE.

 "Hey, are any of you guys out there actually *using* RFC 2549?"