Return to BSD News archive
Path: sserve!manuel.anu.edu.au!munnari.oz.au!hp9000.csc.cuhk.hk!uakari.primate.wisc.edu!zaphod.mps.ohio-state.edu!uwm.edu!ogicse!clark!serval!hlu From: hlu@eecs.wsu.edu (H.J. Lu) Newsgroups: comp.unix.bsd Subject: Re: Sun/386BSD Cross Compiler? Message-ID: <1992Oct7.175256.13113@serval.net.wsu.edu> Date: 7 Oct 92 17:52:56 GMT Article-I.D.: serval.1992Oct7.175256.13113 References: <1992Oct5.204631.8172@tinman.mke.ab.com> <7636@skye.ed.ac.uk> Sender: news@serval.net.wsu.edu (USENET News System) Organization: School of EECS, Washington State University Lines: 31 In article <7636@skye.ed.ac.uk>, richard@aiai.ed.ac.uk (Richard Tobin) writes: |> In article <1992Oct5.204631.8172@tinman.mke.ab.com> tdphette@mke.ab.com (Thad Phetteplace x4461) writes: |> >I've been thinking it would be really handy if I could use one of my |> >SPARCstations to compile 386BSD code (in particular X386). |> |> Cross-compiling isn't too difficult a problem - gcc2 can be configured |> as one. I believe I sent out some patches to BSD's ld to use it as a |> cross-linker (it doesn't handle byte-order differences correctly) |> about 6 months ago, but I no can no longer find them. |> |> However, cross-building X looks rather tricky, due to the complicated |> configuration process. For example, it builds and then runs imake |> so you have to arrange for that to be compiled for the host machine, |> rather than the target. |> I cross-compiled X11R5 for Linux. It is kind of tricky. X11R5 was not designed with cross-compiling in mind. You have to be very careful about a few details. Finally, I managed to make X11R5 for Linux. |> If your problem is disk space, you might find it easier to put your |> 386BSD machine on the net and nfs-mount a filesystem from the Sun. |> |> -- Richard |> -- |> Richard Tobin, |> AI Applications Institute, R.Tobin@ed.ac.uk |> Edinburgh University. H.J.