Eric Blake writes:
> Help! I can't release autoconf 2.69 until I figure out how to work
> around this patch. After updating to the latest shared files, as well
> as applying this patch, I'm now stuck with output going to a literal
> file named '-' instead of going to stdout. I suspect that the
On 04/24/2012 05:17 PM, Stefano Lattarini wrote:
> Hi Eric, Russ.
>
> On 04/25/2012 01:08 AM, Eric Blake wrote:
>> On 04/24/2012 04:50 PM, Russ Allbery wrote:
>>> Eric Blake writes:
>>>
Help! I can't release autoconf 2.69 until I figure out how to work
around this patch. After updatin
Hi Stefano,
> I went for a different and more reliable fix, i.e., using $(libdir)
> instead of $(prefix)/lib, and similarly for the other $(foodir) variables.
>
> So, does the attached patch fix the problem for you?
Yes, it fixes the test failures of
t/posixsubst-libraries.sh
t/posixsubst-l
Hi Eric, Russ.
On 04/25/2012 01:08 AM, Eric Blake wrote:
> On 04/24/2012 04:50 PM, Russ Allbery wrote:
>> Eric Blake writes:
>>
>>> Help! I can't release autoconf 2.69 until I figure out how to work
>>> around this patch. After updating to the latest shared files, as well
>>> as applying this p
On 04/24/2012 04:50 PM, Russ Allbery wrote:
> Eric Blake writes:
>
>> Help! I can't release autoconf 2.69 until I figure out how to work
>> around this patch. After updating to the latest shared files, as well
>> as applying this patch, I'm now stuck with output going to a literal
>> file named
> * lib/Automake/XFile.pm: Update comments and POD documentation to
> suggest a more idiomatic/modern usage.
> (open): Be more robust in detecting whether the created file handle
> is being opened for writing.
> * lib/Automake/FileUtils.pm (update_file, contents): Call the
> 'Automake::XFile' and '
