Message-ID: <34C673A8.CAAB4F16@gmx.net>
Date: Wed, 21 Jan 1998 23:16:08 +0100
From: Robert Hoehne <robert DOT hoehne AT gmx DOT net>
Organization: none provided
MIME-Version: 1.0
To: djgpp-workers AT delorie DOT com
Subject: Re: gcc 2.8.0
References: <34C3CFFE DOT F72F7C7 AT gmx DOT net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Precedence: bulk

At first thanks to all, who ansered me. All of the replies were really
constructive to me. Since I asked so much, and many answered, I will
try to summarize the answers to my questions by telling you, what I want
to do.

Robert Hoehne wrote :
> 
> - Is there some interest for it? :-)
I see it is. :-))

> - Should we test the port first before makeing a
>   public release? (I would prefer it)

When it is ready, I will upload it to DJ, and then I think,
he should upload it for a week or two to v2/.alphas and then
if no big problems occour, we can make the port official.

> - Where to upload it for testing? (I would prefer a
>   similar solution like the v2/.alphas directory)

see above.

> - Is it OK, to have the binaries configured (which
>   needs mostly changes to djgpp.env) to search the
>   executables in a more unix-like way in

I wii do it by modifying gcc.c to use the DJDIR variable,
which then enables gcc to search for the compilers, includes,
specs and so on in

%DJDIR%/lib/gcc-lib/i386-pc-msdosdjgpp/VERSION/

without changing djgpp.env.

> - Should the stabs debugging format be the default? (Which
>   I would prefer). The only problems I see here are

I will uses the standard COFF debug as default.

> - Should the binaries be built with the DJGPP alpha release
>   or with the original 2.01 version?

I will use Thomas's patched 2.01 libc.

> - Should the gcc280b.zip include also a specs file? This could

I will include in gcc280b.zip a sample specs file (called specs.smp
or so) together with a description about it, so the user can decide
to use/modify it for it's own needs.

> - Does it make sense to distribute gcc 2.8.0 (including
>   of course gpp280 objc280) without libg++ 2.8.0?
>   (making the libg++ 2.8.0 port is much harder, as an
>   example see my other mail in this list)

Here I will make at first a libstdc++ package which I could compile
already, but not fixed yet the lfn problems (there is often the
c++ used in the names).

OK, it may still need some time, but I think, it will be ready
soon. I'll send all (or most) of my patches to bug-gcc in the
hope, that they will be accepted for the next version(s).

If you have still some questions/problems/patches please send
me at least a CC.

Robert
-- 
******************************************************
* email:   Robert Hoehne <robert DOT hoehne AT gmx DOT net>     *
* Post:    Am Berg 3, D-09573 Dittmannsdorf, Germany *
* WWW:     http://www.tu-chemnitz.de/~sho/rho        *
******************************************************