X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f X-Recipient: djgpp AT delorie DOT com Date: Wed, 03 Jun 2015 17:44:40 +0300 From: "Eli Zaretskii (eliz AT gnu DOT org)" Subject: Re: ANNOUNCE: release 2 of the DJGPP port of GNU binutils 2.25 uploaded. In-reply-to: <201506022055.t52KtjYm009133@delorie.com> X-012-Sender: halo1 AT inter DOT net DOT il To: djgpp AT delorie DOT com Message-id: <834mmosvfr.fsf@gnu.org> References: <201506022055 DOT t52KtjYm009133 AT delorie DOT com> 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 > Date: Tue, 02 Jun 2015 22:43:32 +0200 > From: "Juan Manuel Guerrero (juan DOT guerrero AT gmx DOT de)" > > This is a port of GNU binutils 2.25 to MSDOS/DJGPP. > > The GNU binutils are utilities of use when dealing with binary files, either > object files or executables. These tools consist of the linker (ld), the > assembler (gas), and the profiler (gprof). There is also a collection of > other binary tools, including the disassembler (objdump). These tools make > use of a pair of libraries (bfd and opcodes) and a common set of header files. > > > > DJGPP specific changes. > ======================= > - This is an bug fix update. > This update provides all DJGPP specific features than presented in the > previous release. Please see: > http://www.delorie.com/archives/browse.cgi?p=djgpp-announce/2014/12/27/22:55:14 > > - The previous port has a bug that is not related to any DJGPP specific changes. > This bug is a genuine binutils bug and can be reproduced by compiling the original > code from binutils-2.25.tar.gz. > The bug can be triggered by compiling a simple hello-world program. Thanks! > Because I am an DJGPP user and I do not care about 64-bit cygwin I have simple > commented out the change and recompiled the sources to produce a working DJGPP > port of binutils-2.25. Of course this must fixed in some other way. It should > not be that to fix one system another system becomes broken. May be someone > with inside in cygwin and djgpp cann give me a hint how to fix this or may be he > sends the fix directly to the binutils mailing list. Please don't keep the fact of this breakage known only on this forum. Please do report it to the Binutils bug-reporting address, if only to make it known to the Binutils maintainers. At the very least making that change be conditioned by "#ifndef __DJGPP__" should fix this problem upstream for DJGPP without breaking Cygwin. FWIW, the following messages on the Cygwin mailing list provide some information about the reasons for that change: https://www.cygwin.com/ml/cygwin/2014-03/msg00437.html https://cygwin.com/ml/cygwin-apps/2013-06/msg00057.html