Gary V. Vaughan wrote:
> Hi Jim,
...
>>> -# Override this in cfg.mk if you use a non-standard build-aux directory.
>>> -build_aux ?= $(srcdir)/build-aux
>>> +ifneq ($(build_aux),)
>>> + $(error '*** set $$(_build-aux) relative to $$(srcdir) instead of
>>> $$(build_aux)')
>>
>> That line is longer t
Hi Jim,
On 27 Oct 2011, at 22:02, Jim Meyering wrote:
> Gary V. Vaughan wrote:
>> On 25 Oct 2011, at 15:18, Gary V. Vaughan wrote:
>>> On 25 Oct 2011, at 15:05, Jim Meyering wrote:
Actually, I think we can both get what we want.
I suggest to adjust your patch so that make is guaranteed t
Gary V. Vaughan wrote:
> Hi Jim,
>
> On 25 Oct 2011, at 15:18, Gary V. Vaughan wrote:
>> On 25 Oct 2011, at 15:05, Jim Meyering wrote:
>>> Actually, I think we can both get what we want.
>>> I suggest to adjust your patch so that make is guaranteed to fail
>>> with a nice diagnostic for anyone who
Hi Jim,
On 25 Oct 2011, at 15:18, Gary V. Vaughan wrote:
> On 25 Oct 2011, at 15:05, Jim Meyering wrote:
>> Actually, I think we can both get what we want.
>> I suggest to adjust your patch so that make is guaranteed to fail
>> with a nice diagnostic for anyone who defines build_aux in cfg.mk.
>
Hi Jim,
Looks like our messages crossed, please disregard my last reply.
On 25 Oct 2011, at 15:05, Jim Meyering wrote:
> [please configure your mail client to stop including both plain
> and html versions of each message]
If you know of an option to do that on the iPad with iOS5 mobile mail
I'll
Hi Jim,
On 25 Oct 2011, at 00:37, Jim Meyering wrote:
> Gary V. Vaughan wrote:
>>
>> _build-aux = libltdl/build-aux
>
> Wouldn't that break things for those who customize build_aux?
Ah, I see what you mean now (will it break for clients who are
customizing with build_aux already).
No, I don't
[please configure your mail client to stop including both plain
and html versions of each message]
Gary V. Vaughan wrote:
> To what advantage over factoring out the duplication entirely at the
> source of the problem with the patch I submitted?
Not breaking some project's existing set-up when
th
Hi Jim,
On 25 Oct 2011, at 00:37, Jim Meyering wrote:
> Gary V. Vaughan wrote:
>> I was wondering why 'make stable' would always use a stale version unless
>> I manually updated my .version file first. It turns out that if you use
>> a non-standard build-aux location, you have to tell GNUmakefil
Gary V. Vaughan wrote:
> I was wondering why 'make stable' would always use a stale version unless
> I manually updated my .version file first. It turns out that if you use
> a non-standard build-aux location, you have to tell GNUmakefile by setting
> _build-aux to get the .version dist-hook machi
Hi all,
I was wondering why 'make stable' would always use a stale version unless
I manually updated my .version file first. It turns out that if you use
a non-standard build-aux location, you have to tell GNUmakefile by setting
_build-aux to get the .version dist-hook machinery, and that you als
10 matches
Mail list logo
