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=20161025;
	h=subject:to:references:from:message-id:date:user-agent:mime-version
	:in-reply-to:content-language:content-transfer-encoding;
	bh=DpVQBQEZLtzOb4iPXIm+rEtHSwpZQogIIP8wSupNQ/w=;
	b=XWGyTUjVGlA40dUw8a/rocRqq5u0p1G4bqiKCuwfFxtlKz4Lb2hHVNIaDeU6No0IoR
	eN1QkPGApUx+tHP8Qf3KIFJfhJvWwp2xBGWWpRUi+XNL+j8aSJx5vzUdDDbM2g/raGfk
	9Ud6fPcWeRUKVCCo3TXt/ZfuN1L8F1Tuz/zLDQ2dLRoaLAplA72qRuzMfkd7EjXOJYTD
	HDJZ45S+6b3WimVDOJBRkeg/mQPhZOQAnCZihmxhiBfoiTUga3H93hK0aUOxAN611v5H
	V0ym4zOC3SL2CawWTlw27ZotM25OJ5PYmZSwhclHNEz42Vkk/r75ircTUj6Cawq+KhzM
	CbmA==
X-Google-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:subject:to:references:from:message-id:date
	:user-agent:mime-version:in-reply-to:content-language
	:content-transfer-encoding;
	bh=DpVQBQEZLtzOb4iPXIm+rEtHSwpZQogIIP8wSupNQ/w=;
	b=akpaSvn5Vix8F3fC4oQiZVr+1L1nhyQIKHF9ODKWC+tHJDEV8ckg9o38ajYYKqraM1
	8+yagqrQtSpWqE9fKom3/Yp49CkfclDH//b3AZK9XNKdAhBprUe9gX/rTqHW2FMXiczY
	5TnfCW8BKx+WuniDAqQqM6m/+X3XJD8KOqvYi/++1dGq4eNgbahHsA6ei1GeX3oDUcLk
	otI2uUaE+itbR/A8cSagEYi/SJ2LOuUpoFfesjgZE/JtDSg3DFc4d5n6OUXafSECzqev
	wH/Sdp5kovc8c3/KGPCRJTDQXHWVSIu47XuVRC8hbzw7AVHjjwyk98bp7gQpMAzYblLX
	wGgA==
X-Gm-Message-State:	ANhLgQ0X6sEOg7to5mcrdBhESYR+ediy+gaU9c76suYCKTedGwBerv9Z
	gOVOGPiReP4HkOD5YsRD3JI+o6D8BpM=
X-Google-Smtp-Source:	ADFU+vuTXqRkDgIqNkWfxmXfB5CYKqHSO3A72BB4nCDeLfXRjg0xsCWfN0RPo7R7P84MH7TNt/F8KQ==
X-Received:	by 2002:adf:e3cc:: with SMTP id k12mr15456431wrm.266.1584129306030;
	Fri, 13 Mar 2020 12:55:06 -0700 (PDT)
Subject:	Re: ANNOUNCE: DJGPP port of GNU binutils 2.34 uploaded.
To:	djgpp AT delorie DOT com
References:	<202003101900 DOT 02AJ0s2L026948 AT delorie DOT com>
	<88b53f3e-5c10-256f-5a0c-aa942a48c6e9 AT gmail DOT com> <5E694788 DOT 5090308 AT gmx DOT de>
	<41a90860-92e9-632e-4b56-4da87681e8f3 AT iki DOT fi>
From:	"J.W. Jagersma (jwjagersma AT gmail DOT com) [via djgpp AT delorie DOT com]" <djgpp AT delorie DOT com>
Message-ID:	<ba4830dc-af2d-d824-0265-2ecfd2182bab@gmail.com>
Date:	Fri, 13 Mar 2020 20:55:04 +0100
User-Agent:	Mozilla/5.0 (Windows NT 6.1; WOW64; rv:68.0) Gecko/20100101
	Thunderbird/68.5.0
MIME-Version:	1.0
In-Reply-To:	<41a90860-92e9-632e-4b56-4da87681e8f3@iki.fi>
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

On 2020-03-13 05:30, Andris Pavenis (andris DOT pavenis AT iki DOT fi) [via djgpp AT delorie DOT com] wrote:
> On 3/11/20 10:18 PM, Juan Manuel Guerrero (juan DOT guerrero AT gmx DOT de) [via djgpp AT delorie DOT com] wrote:
>> Am 11.03.2020 15:56, schrieb J.W. Jagersma (jwjagersma AT gmail DOT com) [via djgpp AT delorie DOT com]:
>>
>> [snip]
>>>>    DJGPP specific changes.
>>>>    =======================
>>>>    - There are no DJGPP specific changes compared with the previous port.
>>>>      The DJGPP specific changes enumerated below are the same than the ones
>>>>      already available in the previous port.
>>>
>>> Are there any plans to have these changes (even partially) upstreamed
>>> to GNU?  Because currently the upstream version is unusable even for
>>> cross-compiling, primarily due to a missing '_environ' symbol in the
>>> ldscripts.
>>
>> No, I have no intention to upstream the patch to GNU.  Primary due to my
>> limited english skills I do not want to become involved in endless discussions
>> about a port that may be considered today as archaic by the maintainers.
>> I do not even know if there is still an official COFF and/or djgpp maintainer
>> of binutils.
> 
> Getting in parts that are necessary for building a cross-compiler should be not too difficult I guess . Than means changes to libbfd and linker scripts. I suppose that DJ would give some support in discussions. An example of such assistance:
> 
> - https://gcc.gnu.org/legacy-ml/gcc-patches/2016-07/msg02005.html (see all thread)
> 
> I did not succeed to get in all changes in than but would not have perhaps got in anything at all without DJ assistance then
> 
> Changes needed to build with 8+3 filename limitations is another thing. I would not even try that. I does not really matter as it is easy to build native binutils for DJGPP using cross-compiler.

Yes, the DOS-specific patches are probably impossible to include.  But
it should at least be possible to get the ldscripts and maybe the
extended relocation patches in.  Binutils appears to support djgpp, but
in its current state it is provably broken.

One potential issue with the ldscripts is that they apply to "go32" in
general.  I'm not sure if there are any targets that use go32, but
don't use djgpp (or at least djgpp's libc).  FreePascal maybe?  If so
then those targets may conflict with the djgpp-specific changes.

I don't yet know when I'll get around to this.  First I've been trying
to get a patch included in gcc, that seemingly takes forever.  After
that I have a patch to binutils (bfd) that I want to submit.  Then I'll
see if it's possible to get the djgpp patches upstreamed.


While on the topic of upstreaming, I should mention that I have a
mirror of djgpp CVS on GitHub, where I also made some changes:

https://github.com/jwt27/djgpp-cvs/compare/jwt27

Some of these patches could probably be merged back into CVS.  These
include changes necessary to build a cross-toolchain, one patch fixes
stack alignment, and there are two patches by Stas Sergeev that I
believe have already been submitted to this list, but not yet included
in CVS.
If desired, I can submit each patch separately to this mailing list.

- Raw text -