Answering my own question Re: Compile of GCC-3.4 port fails on FreeBSD 4.11 --- Help?

2005-04-26 Thread Tom Russo
Answering my own question, just to get the answer into the archives. 

On Mon, Apr 25, 2005 at 10:20:38AM -0600, we recorded a bogon-computron 
collision of the [EMAIL PROTECTED] flavor, containing:
 
 I've been having trouble with ports on FreeBSD 4.11 lately, as more and more
 of them seem to want gcc 3.4 --- but I can't get gcc-3.4 to build.

Turns out that the mingw port (gcc 2.95 cross-compiler for building windows
binaries) is the culprit here.  It installs a /usr/local/include/ansidecl.h
file that is picked up by the configure of gcc-3.4, and that causes the 
problem.  To figure that out I had to look for ATTRIBUTE_NONNULL on my spare
linux box, found it in ansidecl.h, then hunted down why I had an ansidecl.h
without ATTRIBUTE_NONNULL in it with pkg_info -W.

Since I need the mingw port, I just temporarily moved ansidecl.h so gcc3.4
could build.

Never Mind.

 Here's what I get when I attempt to make gcc 3.4:
 
 [...]
 In file included from insn-conditions.c:30:
 ../../gcc-3.4-20050128/gcc/output.h:122: syntax error before 
 `ATTRIBUTE_NONNULL'
 In file included from insn-conditions.c:34:
 ../../gcc-3.4-20050128/gcc/toplev.h:57: syntax error before 
 `ATTRIBUTE_NONNULL'

[...]

 Has anyone else had a problem building gcc-3.4 on FreeBSD 4.11? I see nothing 
 in the -questions or -ports archives about it, and google gave me nothing.  

-- 
Tom RussoKM5VY SAR502  DM64ux http://www.swcp.com/~russo/
Tijeras, NM  QRPL#1592 K2#398  SOC#236 AHTB#1 
 The only thing you can do easily is be wrong, and that's hardly
  worth the effort. -- Norton Juster
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Compile of GCC-3.4 port fails on FreeBSD 4.11 --- Help?

2005-04-25 Thread Tom Russo

I've been having trouble with ports on FreeBSD 4.11 lately, as more and more
of them seem to want gcc 3.4 --- but I can't get gcc-3.4 to build.

Here's what I get when I attempt to make gcc 3.4:

[...]
cc -c   -g  -DIN_GCC   -W -Wall -Wwrite-strings -Wstrict-prototypes 
-Wmissing-prototypes -pedantic -Wno-long-long  -Wno-error  -DHAVE_CONFIG_H 
-DGENERATOR_FILE -I/usr/local/include   -I. -I. -I.././..//gcc-3.4-20050128/gcc 
-I.././..//gcc-3.4-20050128/gcc/. -I.././..//gcc-3.4-20050128/gcc/../include  
insn-conditions.c
In file included from insn-conditions.c:30:
../../gcc-3.4-20050128/gcc/output.h:122: syntax error before `ATTRIBUTE_NONNULL'
In file included from insn-conditions.c:34:
../../gcc-3.4-20050128/gcc/toplev.h:57: syntax error before `ATTRIBUTE_NONNULL'
../../gcc-3.4-20050128/gcc/toplev.h:61: syntax error before `ATTRIBUTE_NONNULL'
../../gcc-3.4-20050128/gcc/toplev.h:65: syntax error before `ATTRIBUTE_NONNULL'
../../gcc-3.4-20050128/gcc/toplev.h:74: syntax error before `ATTRIBUTE_NONNULL'
../../gcc-3.4-20050128/gcc/toplev.h:75: syntax error before `ATTRIBUTE_NONNULL'
gmake[2]: *** [insn-conditions.o] Error 1
gmake[2]: Leaving directory `/sandbox/ports/lang/gcc34/work/build/gcc'
gmake[1]: *** [stage1_build] Error 2
gmake[1]: Leaving directory `/sandbox/ports/lang/gcc34/work/build/gcc'
gmake: *** [bootstrap-lean] Error 2
*** Error code 2

Stop in /sandbox/ports/lang/gcc34.

My system is FreeBSD 4.11-STABLE, last updated on 24 Jan, and my ports tree
was last updated on 4 Feb.  Prior to 24 Jan I had been running a much older
FreeBSD 4.9.  I only updated it then because I was hoping the update would
fix this very same gcc-3.4 problem, and it didn't.  

Has anyone else had a problem building gcc-3.4 on FreeBSD 4.11?  I see nothing 
in the -questions or -ports archives about it, and google gave me nothing.  

-- 
Tom RussoKM5VY SAR502  DM64ux http://www.swcp.com/~russo/
Tijeras, NM  QRPL#1592 K2#398  SOC#236 AHTB#1 
 The only thing you can do easily is be wrong, and that's hardly
  worth the effort. -- Norton Juster
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]