-march=pca56 blows up nethack34-nox11 (fwd)
Dave
friend at vortex4.net
Sun Apr 13 09:10:27 PDT 2003
On Sat, Apr 12, 2003 at 03:42:30PM -0700, Kris Kennaway wrote:
> On Sat, Apr 12, 2003 at 02:15:05AM -0700, Dave wrote:
> >
> > This was intended for the maintainer listed in
> > /usr/ports/games/nethack34-nox11/Makefile, but
> > mail to that address is bouncing, so I'm
> > resending to the address listed in
> > /usr/ports/games/nethack34/Makefile.
>
> Upgrade to a newer 5.0 (which has a newer gcc). If it still fails,
> report it to the gcc people.
>
> Kris
Hmmm...
before
FreeBSD frane.vortex4.net 5.0-RELEASE-p6 FreeBSD 5.0-RELEASE-p6 #2: Tue Mar 25 0
4:13:12 PST 2003 root at frane.vortex4.net:/usr/src/sys/alpha/compile/FRANE al
pha
$ gcc -v
Using built-in specs.
Configured with: FreeBSD/alpha system compiler
Thread model: posix
gcc version 3.2.1 [FreeBSD] 20021119 (release)
after
FreeBSD frane.vortex4.net 5.0-RELEASE-p7 FreeBSD 5.0-RELEASE-p7 #0: Sun Apr 13 0
8:07:08 PDT 2003 root at frane.vortex4.net:/usr/obj/usr/src/sys/FRANE alpha
Using built-in specs.
Configured with: FreeBSD/alpha system compiler
Thread model: posix
gcc version 3.2.1 [FreeBSD] 20021119 (release)
Verified the problem still repeats. Is there a FreeBSD gcc contact in
particular who I can report this to? /usr/src/contrib/gcc/MAINTAINERS
says to use http://gcc.gnu.org/bugs.html to report gcc bugs, and I don't
know enough to be able to identify the code snippet in particular that's
causing the problems. I tried adding -Wall to CFLAGS in make.conf, but I
didn't get any warnings that might be pertinent.
--
Dave Cotton
friend at vortex4.net
More information about the freebsd-ports
mailing list