X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
X-Recipient: djgpp AT delorie DOT com
X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        bh=Z+B0AOtVNhUdvO6QIV4pIcAvTpJO7Ljv+uE+7Eygen4=;
        b=lN7Ba+9Cb+zkuMrjkf7tl9iadr0L/i8tk9lThXEaoDQ6AN+QqBP+GmNbLlxKiwAUzq
         SOdx6feh+dvC2afhLFyjIJmy/D1g4k6Obms3PWjrIYLV0nceUGDnZBlDnOk4bssGJz9T
         K27pTh64bM1u1Krz/8IrwH27WWBiqq33qv+mEh6sB8/4iu8KI9YyQheQVUId+/QVtjWR
         sTPFLaMc86wfVSzeA2d6imJMdC8RyzwKGxLZncbYj9p7LB3dfowzvtNq9gr70z+u5/M4
         YH9rnC9qj21sfsfFtc8i1FC3mXh2f79JUVvXGnKtjh9haDV3lKkqQ2LA2azZl7OSC42L
         /NEQ==
MIME-Version: 1.0
X-Received: by 10.107.46.94 with SMTP id i91mr582933ioo.68.1432840297807; Thu,
 28 May 2015 12:11:37 -0700 (PDT)
In-Reply-To: <CAA2C=vCr1BfJV6vVCnbht0i3w+okeCu+5ALOXZATikripy61Wg@mail.gmail.com>
References: <201505042003 DOT t44K3odg011007 AT delorie DOT com>
	<CAA2C=vCr1BfJV6vVCnbht0i3w+okeCu+5ALOXZATikripy61Wg AT mail DOT gmail DOT com>
Date: Thu, 28 May 2015 22:11:37 +0300
Message-ID: <CAA2C=vD5zCtZENrf+DhcP9hFuqUwZ08MqqmR5qd9ZaOD-b9uCQ@mail.gmail.com>
Subject: Re: ANNOUNCE: DJGPP 2.05 beta 1
From: "Ozkan Sezer (sezeroz AT gmail DOT com)" <djgpp AT delorie DOT com>
To: djgpp AT delorie DOT com
Content-Type: text/plain; charset=UTF-8
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

On 5/28/15, Ozkan Sezer <sezeroz AT gmail DOT com> wrote:
> On 5/4/15, Andris Pavenis (andris DOT pavenis AT iki DOT fi)
> <djgpp-announce AT delorie DOT com> wrote:
>> This is announcement of DJGPP 2.05 beta 1
>>
>> It has numerous changes since previous DJGPP 2.04 beta 1 release in 2003.
>> (http://www.delorie.com/djgpp/mail-archives/browse.cgi?p=djgpp-announce/2003/12/06/22:18:05)
>> Unfortunately DJGPP v2.04 was never released and old beta version slowly
>> became almost unusable together with other newer DJGPP packages.
>>
>> More information about changes in DJGPP 2.05 beta 1 is available at
>>
>>      http://www.delorie.com/djgpp/doc/kb/
>>
>> both in sections about changes in 2.04 and 2.05. The same information is
>> also
>> available in file info/kb.inf in djdev205.zip
>>
>> It needs a lot of testing. Please test it if you have time and/or are
>> interested in any of the above features. Any level of testing would be
>> appreciated.
>
> Some dxe3gen and dxe3res issues: They are not flexible with relation to
> development environment:
>
> 1. As it seems, they were designed to be run under dos-djgpp not with a
>  cross-toolchain, i.e. dxe3gen expects 'gcc', 'as', 'ar' and 'ld' to be
>  djgpp-targeting tools. Well, ld _can_ be changed to be a cross-ld, but
>  only at compile time. User must have the ability to specify his choice
>  of tools.
> - We may make dxe3gen to check environment variables such as DXE_CC,
>  DXE_AS, DXE_AR and DXE_LD whose values will be the names of the tools
>  of choice. (Maybe even a common DXE_CROSS_PREFIX to cover all those
>  at once??)
> - Command line switches instead? (Environment vars seem better to me.)
>
> 2. Strict requirement for DXE_LD_LIBRARY_PATH environment is rude for
>  cross-compilers. It should be optional ifndef DJGPP

I was miserably wrong about the DXE_LD_LIBRARY_PATH. Noticed that I
was testing with some stale environment vars set

>
> 3. dxe3gen sends -T dxe.ld to ld, but the user can't specify a choice
>  of linker script. (One consequence is when compiling djgpp itself with
>  old toolchains, the toolchain-provided dxe.ld is used instead of the
>  one in the source tree.)  Maybe add a '-T' switch to dxe3gen itself??

.. was wrong about the wrong script part too like above.  (Sorry.)


>
> 3. Both dxe3gen and dxe3res expect little endian host.  On the other
>  hand, their father tool dxegen swaps bytes as required. Needs fixing.
>
> Thoughts?
>