Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 12 Apr 1996 16:52:14 +1000
From:      Bruce Evans <bde@zeta.org.au>
To:        craig@seabass.progroup.com, freebsd-hackers@FreeBSD.org
Subject:   Re: GNU binutils port
Message-ID:  <199604120652.QAA00548@godzilla.zeta.org.au>

next in thread | raw e-mail | index | archive | help
>> > Its getting ridiculous, considering how easy it is to import 
>> > the tree.  NetBSD has it running, why, may I ask, is the 2.2
>> > tree not tracking gcc-2.7?
>> 
>> Because last time people tried (2.7.2 IIRC), it failed to correctly compile 
>> the kernel, the X servers, and a few other things people threw at it.

>Is it the compiler or the code?

Probably the configuration (of gcc).  The default configuration is for
FreeBSD-1.1.  To bring it up to date you have to extract diffs from the
FreeBSD-current tree.  This isn't easy because the source organization
is different and the cvs history is a mess.

>I tried to compile the 2.1-R with 2.7.2 and it
>did not fail the compile, but the kernel was buggy.  A saved make log showed
>a substantial number of warnings.  A make log using the 2.6.3 compiler did not
>have any of those warnings.  I have used the 2.7.2 compiler on Solaris 2.4 since

They are only warnings and many would go away if less warnings were enabled.
There would be many more if more were enabled.  For the LINT kernel built on
Apr 6, the warning counts were:

	compiler	warnings (lines)
	--------	--------
	cc		74
	cc -Wall	2394
	gcc-2.7.2	4694

>it was available, and I have not had any problems I could attribute to the compiler.
>All of the ports I have compiled on 2.1-R have worked flawlessly (so far :*)!

>Would I be better off concentrating on Linux, and waiting for FreeBSD to
>catch up?

Many Linux installations use gcc-2.5.8 (because it was around when the
last official release of the Linux kernel (1.2.x) came out, and later
versions of gcc have problems with 1.2.x (gcc-2.7.2 can't compile linux-
1.2.x because of some asm differences...).

Bruce



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199604120652.QAA00548>