Newsgroups: comp.os.minix
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msunews!agate!howland.reston.ans.net!newsfeed.internetmci.com!btnet!demon!peer-news.britain.eu.net!info!iialan
From: iialan@iifeak.swan.ac.uk (Alan Cox)
Subject: Re: Cross Compiler Linux->Minix
X-Nntp-Posting-Host: iifeak.swan.ac.uk
Message-ID: <DIvG53.BrC@info.swan.ac.uk>
Sender: news@info.swan.ac.uk
Organization: Institute For Industrial Information Technology
References: <497pql$ced@news3.cts.com> <DIrJGx.Hn5@westminster.ac.uk> <49fnm5$bsl@news.tamu.edu>
Date: Thu, 30 Nov 1995 19:43:49 GMT
Lines: 28

In article <49fnm5$bsl@news.tamu.edu> richard@atheist.tamu.edu (Richard Henderson) writes:
>>think that as soon as gcc can produce 16 bit code. A 16 bit gcc
>>will be produced using gcc to compile gcc.
>
>I would kind of doubt it.  Even if gcc were modified to generate 
>16-bit code for minix, it would still be limited to 64K+64K.
>Not even close to enough room for gcc.

gcc is out for that. You could work from bcc, or possibly lcc though lcc
will break the 64K+64K boundary.

You could always crosscompile if you taught gcc/gas about ix86 16bit code
(there is already gcc 68HC11... cross compile stuff).

>If someone went farther, and added multiple segments to minix,
>and then made gcc understand segments, it would be possible to
>run gcc on a hefty AT.

At this point I would suggest you buy a real computer 8)

Alan


-- 
  ..-----------,,----------------------------,,----------------------------,,
 // Alan Cox  //  iialan@www.linux.org.uk   //  GW4PTS@GB7SWN.#45.GBR.EU  //
Redistribution of this message via the Microsoft Network is prohibited
<A href="file:/dev/mouse">Click here to disable mouse.</A>
