From owner-freebsd-ports Sat Jul 18 11:24:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA13576 for freebsd-ports-outgoing; Sat, 18 Jul 1998 11:24:16 -0700 (PDT) (envelope-from owner-freebsd-ports@FreeBSD.ORG) Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [128.120.56.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA13517 for ; Sat, 18 Jul 1998 11:23:43 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: from dragon.nuxi.com (d96-072.orchard2.ucdavis.edu [169.237.96.72]) by relay.nuxi.com (8.8.7/8.6.12) with ESMTP id LAA08879; Sat, 18 Jul 1998 11:23:31 -0700 (PDT) Received: (from obrien@localhost) by dragon.nuxi.com (8.8.8/8.7.3) id SAA12987; Sat, 18 Jul 1998 18:23:30 GMT Message-ID: <19980718112330.B12875@nuxi.com> Date: Sat, 18 Jul 1998 11:23:30 -0700 From: "David O'Brien" To: trouble@webfyre.com Cc: ports@FreeBSD.ORG Subject: Re: FreeBSD & EGCS Reply-To: obrien@NUXI.com Mail-Followup-To: trouble@webfyre.com, ports@freebsd.org References: <35AF292C.EE97F87D@iwebb.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <35AF292C.EE97F87D@iwebb.com>; from Support on Fri, Jul 17, 1998 at 05:36:28AM -0500 X-Operating-System: FreeBSD 2.2.6-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Jul 17, 1998 at 05:36:28AM -0500, Support wrote: > Ive noticed that you include egcs in the ports tree, so after reading > about it, i did the make , and noticed tremendous amounts of warnings, > during the build process, so then i started asking around, ive heard > rumours that it wount even build a 2.2.6 kernel, if this alone is true > and correct why is it even in the ports collect, when its actually > really broken... Id love to use egcs because it does have much better Building a runable kernel is always a stress-test for a compiler due to the structure of the end executable and its total lack of ability to tolerate certain bad code generation. The problems with EGCS building a kernel are the same as for gcc28. I have a feeling that some of the problems are due to FreeBSD's a.out exec format. The compiler and tools community only want to support the ELF exec format -- which is one of the reasons the upcomming 3.0 release will be ELF based (or at least supported). The C compiler from both of these ports still compiles most things fine and give better warning messages. The C++ compilers with these ports is an order of magnitude better than G++ 2.7.2 which is very incompliant with the ISO C++ spec. Nor can 2.7.2 compile many of the examples from Stroustrup's "The C++ Programming Language, 3rd Ed.". This is especially true for the STL and templets examples. My current class project is not compilable with G++ 2.7.2, but is with G++ 2.8.1 and the latest EGCS port. > optimizations from what ive read duuring research, yet id vbe afraid > that a make world with egcs installed would possibly mean a complete > re-install of FreeBSD, any thoughts ideas or suggestions would be > appreciated.... You will NOT get fully through a ``make world'' with either EGCS or gcc28. Unless you are interested in heavy toolchain development, I would stick with the stock compiler for ``make world''. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message