Return to the
comp.compilers page.
Search the
comp.compilers archives again.
| Related articles |
|---|
| Writing a C++ compiler in C++ for-usenet-5c@alicewho.com (Adem) (2008-10-27) |
| Re: Writing a C++ compiler in C++ DrDiettrich1@aol.com (Hans-Peter Diettrich) (2008-10-28) |
| Re: Writing a C++ compiler in C++ echristo@gmail.com (Eric Christopher) (2008-10-28) |
| Re: Writing a C++ compiler in C++ cfc@shell01.TheWorld.com (Chris F Clark) (2008-10-28) |
| Re: Writing a C++ compiler in C++ marcov@stack.nl (Marco van de Voort) (2008-10-30) |
| Re: Writing a C++ compiler in C++ DrDiettrich1@aol.com (Hans-Peter Diettrich) (2008-10-31) |
| Re: Writing a C++ compiler in C++ marcov@stack.nl (Marco van de Voort) (2008-11-01) |
| From: | Marco van de Voort <marcov@stack.nl> |
| Newsgroups: | comp.compilers |
| Date: | Sat, 1 Nov 2008 13:02:09 +0000 (UTC) |
| Organization: | Stack Usenet News Service |
| References: | 08-10-049 08-10-050 08-10-058 08-11-001 |
| Keywords: | C++ |
| Posted-Date: | 01 Nov 2008 09:03:21 EDT |
On 2008-10-31, Hans-Peter Diettrich <DrDiettrich1@aol.com> wrote:
>>> itself in a restricted version, and that compiler to produce the final
>>> version. Unless you restrict your project to compile with one specific
>>> C++ compiler, you'll have to bootstrap your compiler in a similar way.
>>
>> (an alternate to dump such bootstrap strategy, and aim more for
>> crosscompiling)
>
> Even a cross compiler must be compiled, it doesn't come out of thin air ;-)
True, but you don't have to maintain multiple stages.
> With regards to FreePascal, I couldn't install or create it on an older
> Linux system, due to unresolvable dependencies in the distribution kit.
First: What exactly? The standalone compiler has no library dependancies:
$ ldd `which fpc`
not a dynamic executable
Second: Is that so strange? Would e.g. a modern gcc build on say an nineties
a.out Linux or BSD?
Return to the
comp.compilers page.
Search the
comp.compilers archives again.