Bill Baxter wrote:
> That would be truly a huge boon to the D community if it were possible to run 'make' on the reference D compiler and get a working executable.

You can already do that with GDC... but no one does.

Robert Fraser wrote:
> Bill Baxter wrote:
>> That would be truly a  huge boon to the D community if it were possible
>> to run 'make' on the *reference D compiler* and get a working executable.
> 
> You can already do that with GDC... but no one does.

Note the words "reference D compiler". :-)

And compiling GDC is far more involved than just running 'make'.  The the process Walter uses to build DMD cannot possibly be as byzantine.

--bb

"BCS" <ao@pathlink.com> wrote in message news:55391cb32bf578ca711ae8b7876a@news.digitalmars.com...
> Reply to Walter,
>
>> BCS wrote:
>>
>>> a.k.a. "sooner or later" ???
>>>
>> Eventually I hope to do it.
>>
>
> <G size=huge>

That would never validate!

<g size = "huge" />

Bill Baxter wrote:
> And compiling GDC is far more involved than just running 'make'.  The the process Walter uses to build DMD cannot possibly be as byzantine.

I eschew complex build processes. If it cannot be built with:

	make

I rewrite it.

Walter Bright wrote:
> BCS wrote:
>> a.k.a. "sooner or later" ???
> 
> Eventually I hope to do it.
What licensing is an issue, I would probobly say, release the code that is yours and put in comments for what is removed. I bet you someone is willing to fill in the blanks.

Robert Fraser wrote:

>> That would be truly a huge boon to the D community if it were possible to run 'make' on the reference D compiler and get a working executable.
> 
> You can already do that with GDC... but no one does.

Fortunately you don't have to build GDC yourself, in order to use it.

--anders

Walter Bright wrote:

>> And compiling GDC is far more involved than just running 'make'.  The the process Walter uses to build DMD cannot possibly be as byzantine.
> 
> I eschew complex build processes. If it cannot be built with:
> 
>     make
>
> I rewrite it. 

The only question being: "which dialect of make" ? :-P

GCC uses autoconf/automake in order to be portable, which really just
means there is an extra "configure" step before the "make" invocation.

GDC's need to patch GCC is complex, but also automated.

--anders

1. PREPARE: ./gcc/d/setup-gcc.sh && mkdir build
2. CONFIGURE: cd build && ../configure --enable-languages=d
3. BUILD: make bootstrap