Subject: Broken gcc on alpha causing a few problems.
To: None <port-alpha@NetBSD.ORG>
From: Tim Rightnour <firstname.lastname@example.org>
Date: 07/23/1998 23:22:35
I'm posting this to both lists, because I feel its important that port alpha
knows about this.. even though this is a tech-pkg issue..
The following pkgs are able to consitently and reliably tickle a bug in the
alpha 1.3.2 and -current gcc:
Mesalib, xmame, mkisofs editors/joe
Of course.. they break any dependant packages along with them. Example below
is from the Mesa build:
rigel# gcc -c -I../include -O2 -fPIC -DSHM -I/usr/X11R6/include -DHZ=100
gcc: Internal compiler error: program cc1 got fatal signal 6
rigel# gcc -c -I../include -fPIC -DSHM -I/usr/X11R6/include -DHZ=100 readpix.c
There are, as I see it.. three or four ways we can deal with this issue. (it
is an issue, seeing as 1.3.2 is a release version)
1) Ignore it, wait until the compiler is fixed, and let the old 1.3.2 users
live with it.
2) Change all the pkgs that tickle the bug to compile without optimization.
3) Place a sepcific hack in the makefile to work around alpha <1.4 versions.
(I'm assuming here we fix the bug by 1.4)
4) Find the files that tickle the bug and hack the makefiles so only those
files get compiled w/o optimization.
I'm open to ideas here.. I want to make sure this gets handled correctly.
IMHO #1 is *not* an option here.. We sold them a CD, now we have to support it.
Tim Rightnour - email@example.com