Re: "make dist" calls "autoheader" ? duh...

[Alexandre Duret-Lutz]

>>> "gd" == Guido Draheim <address@hidden> writes:

 gd> Alexandre Duret-Lutz wrote:
 >> 
 >> Actually, the first build after each run of aclocal will trigger
 >> this (in your story that would be `make', not `make dist', so
 >> maybe I'm commenting something else :)).
 >> 
 gd> sadly, you do :))
 gd> auto:
 gd> aclocal && autoconf && autoheader && automake
 gd> cross-make.sh auto
 gd> configure && make && make dist AUTOHEADER=false
 gd> ... booom!!

I'm still not convinced we are not speaking about the same thing.

Doesn't

| cross-make.sh auto
| configure && make AUTOHEADER=false

fail too?  I believe it should.

However, I think that 

| cross-make.sh auto
| cross-make.sh
| configure && make && make dist AUTOHEADER=false

should work, because the second cross-make.sh will update the
stamp files.

 gd> (as a side-note, you know that cross-make.sh from libsdl.org, and
 gd> I just configure newstuff autotools to end up in local/cross-tools)

Looks like a rather strange decision to me.

(BTW, regarding cross-compilation, why do you need cross-make.sh
at all? It adds /usr/local/cross-tools/i386-mingw32msvc/bin to
the PATH which I found an evil thing to do for a maintainer: an
autoconfiscated project ought to be able to cross-compile
without changing the PATH.)

[...]

 gd> but now I'm going to see a bit of the sun out there,

*sun*?  Were in Germany do you live to have sun? :) That's quite
rare in France these days.  (Moreover my umbrella is broken.  It
always rains when your umbrella has a release critical bug.)
-- 
Alexandre Duret-Lutz