GNU bug report logs - #13524
Improving user experience for non-recursive builds

Previous Next

Full log

Message #172 received at 13524 <at> debbugs.gnu.org (full text, mbox):

From: Stefano Lattarini <stefano.lattarini <at> gmail.com>
To: Bert Wesarg <bert.wesarg <at> googlemail.com>
Cc: 13524 <at> debbugs.gnu.org, Peter Rosin <peda <at> lysator.liu.se>,
	automake-patches <at> gnu.org, Bob Friesenhahn <bfriesen <at> simple.dallas.tx.us>,
	Eric Blake <eblake <at> redhat.com>, Miles Bader <miles <at> gnu.org>
Subject: Re: bug#13524: [PATCH 1/2] preproc: add support for relative names
	in included fragments
Date: Mon, 11 Mar 2013 10:46:55 +0100

On 03/11/2013 10:31 AM, Bert Wesarg wrote:
> Hi,
> 
> I have one more question here:
> 
> On Thu, Feb 14, 2013 at 1:39 PM, Stefano Lattarini
> <stefano.lattarini <at> gmail.com> wrote:
>> On 02/14/2013 01:20 PM, Bert Wesarg wrote:
>>> Hi,
>>>
>>> On Thu, Feb 14, 2013 at 11:26 AM, Stefano Lattarini wrote:
>>> What definitily will not work ist something like this, right?
>>>
>>> here = %reldir%
>>> target = %canon_reldir%/foo
>>>
>>>         bin_PROGRAMS += ${here}/foo
>>>         ${target}_SOURCES = ${here}/bar.c
>>>
> 
> I have the impression that variable references in filenames aren't
> supported anyway, right?
> 
Wrong, actually.  What isn't supported are variable references in
variable/primary names:

    $ cat > Makefile.am <<-END
        foo = bin
        $(foo)_PROGRAMS = bar
    END
    $ automake -a
    Makefile.am:2: bad characters in variable name `$(foo)_PROGRAMS'
    Makefile.am:2: `$(foo)_PROGRAMS' is used but `$(foo)dir' is undefined

Best regards,
  Stefano

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.