This is the mail archive of the mailing list for the GCC project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: GCC 3.1 OpenBSD

In article <> you write:
>Is there any known issue compiling GCC 3.1 on OPENBSD 3.1 i386 ?
>I did a full install of OBSD 3.1 and then tried to compile gcc3.1 ..
>and it bombs at the following:
>gcc -c -DIN_GCC -DLOCALEDIR=\"/usr/local/share/locale\" 
>-DLIBDIR=\"/usr/local/lib\" -DHAVE_CONFIG_H -I.. -I. 
>-I/junk/gcc-3.1/gcc/intl -I/junk/gcc-3.1/gcc  -I/junk/gcc-3.1/gcc/config 
>-I/junk/gcc-3.1/gcc/../include  -g -W -Wall -Wwrite-strings 
>-Wstrict-prototypes -Wmissing-prototypes -Wtraditional -pedantic 
>-Wno-long-long  /junk/gcc-3.1/gcc/intl/ngettext.c -o ngettext.o
>yacc --name-prefix=__gettext --output plural.c /junk/gcc-3.1/gcc/intl/plural.y
>usage: yacc [-dlrtv] [-b file_prefix] [-o outputfile] [-p symbol_prefix] 
>*** Error code 1
>Stop in /junk/gcc-3.1/bsd/gcc/intl.
>*** Error code 1

I'll check how this fares. I generally compile gcc with intl support
disabled, for various reasons...

Also, I haven't verified, but due to some weird bugs in gcc's Makefile,
recent gcc require gnu-make to compile. Last time I checked, I wasn't able
to track the problem down beyond excessive makefile hackery/libtool
interactions in libstdc++.

If you are compiling the whole of gcc 3.1, be advised that java is currently
incomplete, and won't compile. There's also a necessary patch of mine on

In any case, your best bet is probably to wait until a proper port appears
in OpenBSD port's collection.

Right now, gcc cannot even compile the whole system, thanks to guys breaking
#pragma weak support...

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]