Return to BSD News archive
Newsgroups: comp.os.386bsd.questions Path: sserve!newshost.anu.edu.au!munnari.oz.au!constellation!convex!convex!convex!cs.utexas.edu!uunet!pipex!uknet!cf-cm!paul From: paul@myrddin.isl.cf.ac.uk (Paul) Subject: Re: Compiling Kernel with GCC-2: How, exactly? Message-ID: <1993Jul25.192511.23179@cm.cf.ac.uk> Sender: news@cm.cf.ac.uk (Network News System) Organization: Intelligent Systems Lab, ELSYM, University of Wales, Cardiff References: <1993Jul22.011943.26148@husc14.harvard.edu> <1993Jul22.100311.24391@cm.cf.ac.uk> <HALEY.93Jul24163021@husc10.harvard.edu> Date: Sun, 25 Jul 1993 19:25:09 +0000 Lines: 50 In article <HALEY.93Jul24163021@husc10.harvard.edu> haley@husc10.harvard.edu (Elizabeth Haley) writes: > >O.K. So the answer is patience. :-) No much, you're only going to have to wait about a week. > >On the whole however, let me make this comment: > >I have already brought in and compiled gcc 2.4.5, and will be using it >for my programming projects. I in fact made gcc, g++, and objc, though >I deleted the last to save the disk space. > >I have no intention of bringing another copy down with an update, as I >do not have direct access to the net, and have to do it via the Nike >protocol. > I've not seen the exact packaging of the FreeBSD release yet but it's basically going to be an all or nothing update. There are fundamental changes in FreeBSD which means you're not going to be able to mix and match the new with the old and expect your system to work. For a start there's new db code that affects a lot more than you'd initially think. >I find it somewhat disturbing that the plan is take apart the gcc >distribution, though I can thoroughly understand the need to have a >smaller dist. I can also understand wanting to get rid of all the >files that pertain to other cpu's, though I would warn against a total >conversion to Berkeley style make, because I'm sure there are a few >intrepid adveturers out there who will make a cross-compiler, since >they have access to other machines... Everything that goes into the FreeBSD core source tree is b-maked. This goes for all gnu code that we've moved into the main source tree, such as gas, etc. Gnu build environments don't work well, if at all, in the berkeley world so there's not much choice but to convert essential tools to berkeley format. Support for other architectures is being integrated into the b-maked gcc2 release, though you'll see that in NetBSD sooner than FreeBSD and building a cross-compiler is but a small step from that. > >One question: What version of gcc 1 are you going to distribute? 1.39, it's exactly the same code as was distributed with 0.1 386BSD. -- Paul Richards, University of Wales, College Cardiff Internet: paul@isl.cf.ac.uk spedpr@thor.cf.ac.uk