X-Spam-Check-By: sourceware.org Message-ID: From: "Sisyphus" To: , "Paul Mallas" References: <76F97D29CEDF4D97BA3004F2C2B2EF08@desktop2> In-Reply-To: Subject: Re: Trying to build (perl) Inline::CPP-0.25. Date: Wed, 25 Jul 2007 01:48:05 +1000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Windows Mail 6.0.6000.16480 X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com ----- Original Message ----- From: "Paul Mallas" To: Sent: Wednesday, July 25, 2007 12:05 AM Subject: Re: Trying to build (perl) Inline::CPP-0.25. >I ran into a similar problem recently - the standard sort of c++ references >were not being found. It turns out that the linker I was calling was ld2, >a script that called another script perlld (in /usr/bin), where I found >this: > > # these are pretty mandatory > my $CC = 'gcc'; > my $EXPORT_ALL = 1; > > I edited this script and replaced gcc with g++. I don't know if this was a > good idea or not, but it seemed to fix the problem. > I personally think this was an *excellent* idea. It certainly works for me, too. I had run: ------------------------- Rob@desktop2 ~/comp/Inline-CPP-0.25 $ perl -V:ld ld='ld2'; ------------------------- and wondered about that. You're suggested amendment (apart from fixing the problem) is also in keeping with my "native" (MinGW) build of Windows perl 5.8 which reports: -------------------------- C:\>perl -V:ld ld='g++'; -------------------------- Dammit ... I should've known ... I've struck similar problems with MinGW builds of perl that want to set 'ld' to 'gcc' instead of 'g++'. So ... it *is* a Cygwin Perl bug after all ? (That's a question, not an assertion :-) Thanks Paul. Cheers, Rob -- 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/