Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!bunyip.cc.uq.oz.au!munnari.oz.au!spool.mu.edu!news.clark.edu!netnews.nwnet.net!selway.umt.edu!usenet.coe.montana.edu!bsd.coe.montana.edu!nate From: nate@bsd.coe.montana.edu (Nate Williams) Newsgroups: comp.os.386bsd.development Subject: Re: Wishlist: FreeBSD 2.0 Date: 17 Aug 1994 14:12:24 GMT Organization: Montana State University, Bozeman Montana Lines: 35 Message-ID: <32t5s8$hut@pdq.coe.montana.edu> References: <777048964.AA03114@f74.n700.z6.ftn.air.org> <32rh8j$cto@pdq.coe.montana.edu> <32rvah$lvq@spruce.cic.net> NNTP-Posting-Host: 153.90.192.29 In article <32rvah$lvq@spruce.cic.net>, Paul Southworth <pauls@locust.cic.net> wrote: >In article <32rh8j$cto@pdq.coe.montana.edu>, >Nate Williams <nate@bsd.coe.montana.edu> wrote: >>In article <777048964.AA03114@f74.n700.z6.ftn.air.org>, >>Clarence Chu <Clarence.Chu@f132.n700.z6.ftn.air.org> wrote: >>>5) cross compiler to ?????? processor can be made using the stock >>> compiler. >> >>Since FreeBSD runs on x86 machines, what gain would there be? > > >Just a wild guess: Porting to other architectures??? *Grin*. I guess I opened myself up for that one. My suggestion is to take a stock gcc and build it for cross-compilation, since for the *majority* of the users the amount of unused code (by them) for building a generic cross-compilation platform is not worth adding it to the generic system. It's pretty easy to build the cross tools, so by getting the stock distribution (from CD or whatever) a developer can build the tools w/out having to burden the normal user with the extra code. When multiple architecture/platforms come into existance for FreeBSD, we will add only the code necessary for that platform to the compiler tools. Nate -- nate@bsd.coe.montana.edu | FreeBSD core member and all around tech. nate@cs.montana.edu | weenie. work #: (406) 994-4836 | home #: (406) 586-0579 | Available for contract/otherwise work.