Re: Rule naming

[Юрий Пухальский]

Good night, Ralf!

No bugs, no see:)))
Well, i think i have little something in some weird case but still had
no time to put my hands on it, probably some time soon i'll write
again:)

In this very case i was worried about VPATH builds, so i was
specifying @srcdir@ and @builddir@ explicitly everywhere. Should the
rule of the thumb be to omit @builddir@ while referring to the built
objects in current directory?

2010/7/12 Ralf Wildenhues <address@hidden>:
> Hi Yuri,
>
> long time no see.  Welcome back!
>
> * Юрий Пухальский wrote on Mon, Jul 12, 2010 at 11:36:59AM CEST:
>> I don't know whether this may be considered a bug or not, but the
>> following problem exists with native makes on AIX and HP-UX platforms.
>> Automake is 1.11 on linux.
>> I make two libraries like this:
>> noinst_LTLIBRARIES = a.la b.la
>>
>> And then i use one of them. If i specify @builddir@ explicitly:
>> a_la_LIBADD = @builddir@/b.la
>>
>> Then i have <path>/b.la (e.g. ./b.la) in _DEPENDENCIES, and b.la as a target.
>>
>> While GNU make can cope with this and correctly understands that the
>> goal is the same, on AIX native make cannot find the rule:
>
> Exactly.  AIX make doesn't know that FILE and ./FILE are the same thing.
> So just use one spelling, consistently, throughout.  Since @builddir@ is
> always '.', you can just omit @builddir@/ throughout, for example.
>
>> To be one the safe side it's easiest to add two targets doing the
>> same, one with builddir prepended and one without. But there could be
>> @builddir@/../<dir>/ something... Probably it cannot be solved without
>> analyzing the paths of dependencies.
>
> Having both FILE and ./FILE as targets isn't safe, either, because then
> GNU make will complain about duplicate targets.
>
> Cheers,
> Ralf
>



-- 
«The good thing about standards is there are so many to choose from.»