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
Message-ID: <000501c2d540$235e96e0$78d96f83@pomello>
From: "Max Bowsher" <maxb AT ukf DOT net>
To: <cygwin AT cygwin DOT com>
References: <20030215210505 DOT GA29578 AT redhat DOT com> <010601c2d537$decb05c0$78d96f83 AT pomello> <20030215215840 DOT GA3446 AT redhat DOT com>
Subject: Re: [Problem] mempcpy is missing?  (FAQ alert)
Date: Sat, 15 Feb 2003 22:18:16 -0000
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106

Christopher Faylor wrote:
> On Sat, Feb 15, 2003 at 09:19:05PM -0000, Max Bowsher wrote:
>> Yes, in an ideal world, configure would deal with this - but unless
>> you have a better idea, the only way I can think of dealing with it
>> is to copy the problem header to the compilation directory, parse
>> out the problem declaration somehow, and modify the compiler
>> invocations with an additional -I option.  Messy and fragile.
>
> Wow, are you related to Rube Goldberg?
>
> #define mempcpy foo_mempcpy
> #include <string.h>
> #undef mempcpy

Ok, I feel stupid :-)

>> So, when fixing the problem is orders of magnitude easier than
>> making a workaround, it's easy to see which will happen! :-)
>
> This is *not* a workaround.  This is making configury work for what
> it was designed to do.

One could say that configury is a workaround :-)
You are, of course, correct that this is one more class of weirdness that
configury could be enhanced to deal with.
I was just commenting that I didn't think it was particulary likely to
happen.

> In this case, the whole point of configuration scripts is to work
> around OS build environment differences.  "In an ideal world" is
> exactly what configure is not supposed to assume.

I agree. What I meant was: In an ideal world someone would make the relevant
improvements to configury.

> Of course we're going to fix cygwin.  I just checked in a fix.

Great!

> I assume this will probably be the end of it since no one will go to
> the effort of trying to fix libintl's configury

Yes, that's what I was trying to say. Seems I didn't convey my point very
well.

Max.


--
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/