Mailing List ArchiveSupport open source code!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: tlug: ccp
- To: tlug@example.com, chris@example.com
- Subject: Re: tlug: ccp
- From: "Manuel M. T. Chakravarty" <chak@example.com>
- Date: Tue, 15 Dec 1998 21:02:12 +0900
- Content-Transfer-Encoding: 7bit
- Content-Type: Text/Plain; charset=us-ascii
- In-Reply-To: Your message of "Tue, 15 Dec 1998 19:59:30 +0900 (JST)"<Pine.LNX.4.05.9812151956421.3795-100000@example.com>
- References: <Pine.LNX.4.05.9812151956421.3795-100000@example.com>
- Reply-To: tlug@example.com
- Sender: owner-tlug@example.com
Chris Sekiya <chris@example.com> wrote, > On Tue, 15 Dec 1998, Scott Stone wrote: > > > builds a first stage with an assembler, then uses the first stage to > > compile the second stage, etc. > > Check again, Scott. You can't even configure egcs for compilation without > a compiler, let alone build the sucker. > > Look: > > bash-2.02$ ../egcs-1.1b/configure --prefix=/usr i586-linux > Created "Makefile" in /usr/src/newobj using "mt-frag" > ../egcs-1.1b/configure: cc: command not found > *** The command 'cc -o conftest -g conftest.c' failed. > *** You must set the environment variable CC to a working compiler. > bash-2.02$ ../egcs-1.1b/gcc/configure --prefix=/usr i586-linux > creating cache ./config.cache > checking host system type... i586-pc-linux-gnu > checking target system type... i586-pc-linux-gnu > checking build system type... i586-pc-linux-gnu > checking for gcc... no > checking for cc... no > configure: error: no acceptable cc found in $PATH > > (not really 1.1b, it's patched up to 1.1.1) > > It don't go. No configure, then no Makefile. No Makefile, no compiler. > > Think about this. Unless egcs ships with .S files for every .c, > generation without a compiler can't possibly work. Which won't be very handy, as the .S tends to be a bit machine dependent ;-) Actually, sometimes high-level compilers can bootstrap themselves in a similar way, even if they are implemented in the language that they compile. They come as a set of .c files generated by the compiler from its own sources on another machine. So, you compile the .c files and get a first version of the compiler, which you then use to compile the compiler by itself from the high-level language. Nearly like Muenchhausen (if you know his story :-) I love compilers :-) Manuel ------------------------------------------------------------------ Next Nomikai: 15 January 1999, 19:30 Tengu TokyoEkiMae 03-3275-3691 Next Technical Meeting: 13 February, 12:30 Place: TBD ------------------------------------------------------------------ more info: http://tlug.linux.or.jp Sponsor: PHT
- References:
- Re: tlug: ccp
- From: Chris Sekiya <chris@example.com>
Home | Main Index | Thread Index
- Prev by Date: Re: tlug: Firewall
- Next by Date: Re: tlug: ccp
- Prev by thread: Re: tlug: ccp
- Next by thread: Re: tlug: ccp
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links