Date: 15 Mar 2004 12:01:16 -0700 From: llewelly@xmission.com To: David Gilbert <dgilbert@dclg.ca> Cc: freebsd-hackers@freebsd.org Subject: Re: GCC include files conundrum. Message-ID: <s3rk71mhr43.fsf@xmission.xmission.com> In-Reply-To: <s3rr7vuhtud.fsf@xmission.xmission.com> References: <16468.65270.123954.862565@canoe.dclg.ca> <20040315013817.GA68381@crodrigues.org> <16469.3340.625290.632134@canoe.dclg.ca> <20040315102516.GH15687@atrbg11.informatik.tu-muenchen.de> <16469.46609.293027.840180@canoe.dclg.ca> <s3rr7vuhtud.fsf@xmission.xmission.com>
next in thread | previous in thread | raw e-mail | index | archive | help
llewelly@xmission.com writes:
[snip]
> As far as 'being compatible' goes, there is a gcc 2.95.3 port
> (/usr/ports/lang/gcc295), and if it is still being maintained, I
> would suggest any port which doesn't build with gcc 3.3.x be
> modified to be use and require that port, after emiting a warning
> of some kind, saying that gcc 2.95 won't be around forever, and
> the port will have to be fixed soon. I just checked, and on my
> 5.2p2 box, gcc295 still builds. But surely someone already thought
> of this, and decided that making ports build with gcc 3.3.3 was
> better than making them use and require the gcc295 port, which,
> after all, will only become harder to maintain over time.
[snip]
Replying to myself, I just tried hacking audio/tclmidi to use and
require lang/gcc295, and it does not build with the gcc295 port.
/usr/local/bin/g++295 -c -O -pipe -mcpu=pentiumpro -DHAVE_UNISTD_H=1
+-DHAVE_SYS_TIME_H=1 -DHAVE_SYS_FILIO_H=1 -DTIME_WITH_SYS_TIME=1
+-DRETSIGTYPE=void -I/usr/local/include/tcl8.2 -fpic SMFTrack.cxx
SMFTrack.cxx: In function `class ostream & operator <<(ostream &, const SMFTrack &)':
SMFTrack.cxx:364: `::_Ios_Fmtflags' undeclared (first use here)
SMFTrack.cxx:364: parse error before `;'
SMFTrack.cxx:371: `prev_flags' undeclared (first use this function)
SMFTrack.cxx:371: (Each undeclared identifier is reported only once
SMFTrack.cxx:371: for each function it appears in.)
*** Error code 1
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?s3rk71mhr43.fsf>