X-Authentication-Warning:	delorie.com: mail set sender to djgpp-bounces using -f
From:	=?UTF-8?Q?Hans-Bernhard_Br=c3=b6ker?= <HBBroeker AT t-online DOT de>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: ANNOUNCE: DJGPP port of GNU binutils 2.29 uploaded.
Date:	Wed, 2 Aug 2017 20:44:12 +0200
Lines:	39
Message-ID:	<eueks1FadflU1@mid.dfncis.de>
References:	<201707301540 DOT v6UFecLb017840 AT delorie DOT com>
	<CAA2C=vBWY7HYeu+tdO=WYN=wEmWfhLXWgH-9PtSvZkMs54rs1Q AT mail DOT gmail DOT com>
	<5980C3AA DOT 2080305 AT gmx DOT de> <euccrcFp8kqU1 AT mid DOT dfncis DOT de>
	<598108FD DOT 5060908 AT gmx DOT de>
Mime-Version:	1.0
X-Trace:	news.dfncis.de 6U45OKg2bsrMyKcfxlk4uA1+8d+aKGAY0EDlFn+srEvDqc/cr9mxa+m2AT
Cancel-Lock:	sha1:DBAMC2+YAXQzWJLPkjMstm9D0mc=
User-Agent:	Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101
	Thunderbird/52.2.1
In-Reply-To:	<598108FD.5060908@gmx.de>
Bytes:	2669
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
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

Am 02.08.2017 um 01:04 schrieb Juan Manuel Guerrero 
(juan DOT guerrero AT gmx DOT de) [via djgpp AT delorie DOT com]:
> Am 02.08.2017 00:15, schrieb Hans-Bernhard Bröker:
>> Am 01.08.2017 um 20:08 schrieb Juan Manuel Guerrero [via 
>> djgpp AT delorie DOT com]:
>>> I do not know who has decide decades ago to declare _doprnt in
>>> stdio.h but now this declaration collides with the one from libiberty.
>>
>> How come it suddenly collides now?
>>
>> _doprint has been in libiberty for 16 years, and in both GCC and DJGPP 
>> sources longer than that. What change suddenly turned this friendly 
>> coexistence into a collision?

> We are talking about _doprnt and no other function.  

Just to clarify: so was I.  The "_doprint" above was a typo.  The 
function that's been in -liberty for all that time is indeed called _doprnt.

> But the point is something completely different.  They have 
> copied-and-pasted
> the _doprnt version of libiberty into bfd.c and adjusted it for their 
> particular
> purposes inside the bfd library.

Aha, so the conflict is not between libiberty and DJGPP libc, but rather 
between libbfd and DJGPP libc.

That has the potential of changing the entire story, because these are, 
to at least some degree, _both_ part of "the implementation", i.e. both 
sides of the conflict have rather equally valid rights to use this kind 
of name.

And just for the record, IMHO your assessment:

 > IMO this is a DJGPP bug.

remains untenable.  If this is a bug at all, it was in libiberty, and is 
now in BFD.

- Raw text -