Subject: | [Fwd: [Fwd: Re: '()' escaped to '\(\)' is breaking my build]] |
Date: | Thu, 17 Dec 2009 13:56:08 -0800 |
To: | via RT <bug-ExtUtils-MakeMaker [...] rt.cpan.org> |
From: | Michael G Schwern <schwern [...] pobox.com> |
See analysis on the makemaker list. Might be ok to replace quote_paren() with
quote_literal() and have quote_literal() quote parens.
Show quoted text
-------- Original Message --------
Subject: [Fwd: Re: '()' escaped to '\(\)' is breaking my build]
Date: Thu, 17 Dec 2009 13:46:11 -0800
From: Michael G Schwern <schwern@pobox.com>
To: makemaker <makemaker@perl.org>
Forwarding back to the list so its archived.
-------- Original Message --------
Subject: Re: '()' escaped to '\(\)' is breaking my build
Date: Thu, 17 Dec 2009 13:08:35 -0500
From: Dave Anderson <b10@davywavy.com>
To: Michael G Schwern <schwern@pobox.com>
References: <4B292F39.7090601@davywavy.com> <4B2988C2.3000807@pobox.com>
Hi,
I attached a .zip of Makefile.PL, Makefile, and error.txt which is text
from my command prompt.
Thanks!
Dave A
Michael G Schwern wrote:
> Dave Anderson wrote:
--
A: Yes.
>> The key line is:
>>
>
> Sorry about that.
>
> Please attach your Makefile and a copy of the build error, then we can
> get started investigating.
>
>
>>> LDDLFLAGS => '-libpath:"c:\Program Files (x86)\Microsoft
>>> Visual Studio 9.0\VC\lib"
>> The parenthesis are annoyingly escaped when creating the Makefile:
>>
>>> LDDLFLAGS = -libpath:"c:\Program Files \(x86\)\Microsoft Visual
>>> Studio 9.0\VC\lib" -libpath:"c:\Program Files\Microsoft
>>> SDKs\Windows\v6.0A\Lib"
>> Which breaks the build on Windows. The INC attribute doesn't do that
>> so why does LDDLFLAGS? I've tried moving those options into LD but it
>> has the same problem. For now I'm going to have to modify the
>> generated Makefile each time I call Makefile.PL.
> Q: Are you sure?
>> A: Because it reverses the logical flow of conversation.
>>> Q: Why is top posting annoying in email?
Message body not shown because it is not plain text.