From: "Dave Korn" <dave.korn@artimi.com>
To: <cygwin@cygwin.com>
References: <76F97D29CEDF4D97BA3004F2C2B2EF08@desktop2> <01e301c7cdf7$b4d93b20$2e08a8c0@CAM.ARTIMI.COM> <46A60338.86ADB36D@dessent.net>
Subject: RE: Trying to build (perl) Inline::CPP-0.25.
Date: Tue, 24 Jul 2007 14:58:39 +0100
Message-ID: <01e601c7cdfa$bd03cf10$2e08a8c0@CAM.ARTIMI.COM>
MIME-Version: 1.0
Content-Type: text/plain; 	charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-Reply-To: <46A60338.86ADB36D@dessent.net>
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

On 24 July 2007 14:49, Brian Dessent wrote:

> Dave Korn wrote:
> 
>>   That I can't say.  But assuming the build uses proper dependencies in the
>> makefile, you should be able to workaround it by cutting and pasting that
>> line into your shell, replacing 'gcc' by 'g++' as you go, and once you've
>> got past that manually the rest of the build should run to completion.
> 
> Normally that might work but in this case it misses the point, as the
> whole purpose of this perl module is to dynamically invoke the C++
> compiler at runtime to compile the inline C++ bits in the script.  And
> if it's invoking the compiler wrong it makes this essentially useless as
> all the stuff it feeds the compiler is dynamically generated.

  Oh, yes, I missed that this was happening during "make check" and thought it
was just part of the module build.  A 'workaround' for a testsuite failure is
indeed pretty damn useless!


    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/