X-Spam-Check-By: sourceware.org Message-ID: <46A65A46.80209@x-ray.at> Date: Tue, 24 Jul 2007 22:00:06 +0200 From: Reini Urban User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de-AT; rv:1.8.1.5) Gecko/20070716 SeaMonkey/1.1.3 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Trying to build (perl) Inline::CPP-0.25. References: <76F97D29CEDF4D97BA3004F2C2B2EF08 AT desktop2> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Sisyphus schrieb: > ------------------------- > Rob AT 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++'; Interesting. We should definitely ask p5p if we shouldn't switch back to normal behaviour without the ld2 wrapper, but first I must study history on this issue, why we introduced that at all. Switching to g++ probably has other issues. Most XS modules are pretty fine with gcc, but I wouldn't be sure if all of them are C++ safe. MS cl is probably not that strict as gnu. Even xsubpp creates lousy c++ code. For the start having a wrapper should help use in fixing this inside ld2 or perlld. We should detect if the intermediate .o was compiled as c++ or plain gcc. nm -C $obj|grep "operator new(" for example. Is there a better way? -- Reini Urban -- 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/