Re: Native OpenBSD 3.4 gcc 3.3.2 build (MORE)

[Nathanael Nerode <neroden at twcny dot rr dot com>]

Marc Espie:
> Sorry for the delay in pitching in.
> I hope to submit the elf configuration for OpenBSD i386 in a few days.
Great news!

Last time I looked, the OpenBSD generic configuration stanza in 
config.gcc was missing a number of features common to the NetBSD and 
FreeBSD stanzas... which made me suspicious.  ;-)

For ELF, I'd guess that you want to add t-slibgcc-elf-ver to the 
beginning of the tmake_file list.

I think you use a version of gas as the assembler, don't you?  And a 
version of gnu ld as the (static) linker?  In that case, you probably want
gas=yes
gnu_ld=yes
clauses as well.  (Yeah, it shouldn't be needed, but they do help 
configury to work right at the moment.)

Hope this helps.  Please do tell us what's needed for gcc to work 'out 
of the box' on OpenBSD.  :-)

> As far as the main compiler in OpenBSD goes, only the gcc 3.3.2 source
> is there. There's still a small stumbling block, which I hope to solve
> soon: the libstdc++-v3 has issues, and thus it doesn't work in-tree.
> It's probably just an includes issue. We don't expect to switch to 3.3.2
> for OpenBSD 3.5 globally. The architectures most broken with 2.95 (e.g.,
> sparc64) are very likely to switch first.
>
> As far as the 3.3.2 in ports goes, it's perfectly fine.  At least, as
> far as i386 is concerned. gcc 3.3.2, with a few patches, appears to work
> on i386, sparc, sparc64, ppc. It has definite issues on m68k,
I seem to remember that general m68k support is quite a bit better in 
the 3.4 development sources, though I could be wrong.

> vax
> (ICEs), alpha (linker can't solve jump for main, looks like this comes
> from main being in a lib too far away from start), and m88k is still
> basically broken, though Miod Vallat is working on it.