Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Sat, 15 Feb 2003 16:05:05 -0500
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: [Problem] mempcpy is missing?  (FAQ alert)
Message-ID: <20030215210505.GA29578@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <00d001c2d530$02497430$78d96f83@pomello>
User-Agent: Mutt/1.5.1i

On Sat, Feb 15, 2003 at 08:22:49PM -0000, Max Bowsher wrote:
>bChristopher Faylor wrote:
>> On Sat, Feb 15, 2003 at 12:35:56PM -0700, Roger Sayle wrote:
>>> I apologise if this is the wrong list to report bugs.  I have
>>> searched the archive and haven't been able to find a reference to
>>> mempcpy.
>>
>> As you have discovered, mempcpy is not provided.  If a configure
>> script detects it, the configure script is broken.
>
>As he said, his configure script correctly decides #undef HAVE_MEMPCPY
>
>But then the source tries to define its own replacement mempcpy - but it
>can't, because that clashes with Cygwin's headers. So this really is
>Cygwin's fault.

Um.  This is not the first time something like this has come up.  And it
won't be the last.  There are a number of things in newlib that are not
exported by cygwin.  The definition of mempcpy has apparently been in
the header since July of 2002.

It is trivial to export the function or protect the header but that is
besides the point.  The whole point of systems like configure is to
provide pain-free ways to work around system quirks.  So the best fix is
to modify the libintl source so that this isn't a problem for older
versions of cygwin (which we obviously can't fix retroactively) or other
hypothetical systems out there which may have similar problems.

So, the cygwin bug report is noted and appreciated.  We'll fix this
eventually.  However, the "correct" fix is to modify the configury
mechanism which trips up on this in libintl.

I guess I can't get by without giving the long answers to reports
like this...  We should add this to the FAQ.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/