(no subject)

[Vincent Torri-2]

Hey,

in a subdirectory, we generate a file. First we want to delete it, then
fill it with >>. So we use that rule:

$(builddir)/eina_amalgamation.c: $(sources_used) Makefile
  -rm -f $(builddir)/eina_amalgamation.c

(it is followed by the creation of the file)

With automake 1.10 or 1.11, there is no problem. But with automake 1.9,
builddir seems empty and the command:

rm -f /eina_almagamation.c

is executed.

Does someone know why ? And what would be the correct thing to do ?

thank you

Vincent Torri

[Ralf Wildenhues]

* Vincent Torri wrote on Wed, Oct 14, 2009 at 07:48:35AM CEST:
> $(builddir)/eina_amalgamation.c: $(sources_used) Makefile
> -rm -f $(builddir)/eina_amalgamation.c

$(builddir) is always equal to '.'; also, non-GNU makes don't identify
FILE and ./FILE; so you are better off omitting '$(builddir)/', in both
target name and command text.

> With automake 1.10 or 1.11, there is no problem. But with automake
> 1.9, builddir seems empty and the command:
>
> rm -f /eina_almagamation.c
>
> is executed.

No idea why that happens though.  Might have forgotten the reason.

Cheers,
Ralf

[Vincent Torri-2]

On Wed, 14 Oct 2009, Ralf Wildenhues wrote:

> * Vincent Torri wrote on Wed, Oct 14, 2009 at 07:48:35AM CEST:
>> $(builddir)/eina_amalgamation.c: $(sources_used) Makefile
>> -rm -f $(builddir)/eina_amalgamation.c
>
> $(builddir) is always equal to '.'; also, non-GNU makes don't identify
> FILE and ./FILE; so you are better off omitting '$(builddir)/', in both
> target name and command text.

ok. I feared that it could break distcheck without $(builddir) but it
seems not, at least with automake 1.10.

>> With automake 1.10 or 1.11, there is no problem. But with automake
>> 1.9, builddir seems empty and the command:
>>
>> rm -f /eina_almagamation.c
>>
>> is executed.
>
> No idea why that happens though.  Might have forgotten the reason.

maybe someone will remember :)

thank you

Vincent Torri