>>> "Tom" == Tom Tromey <[EMAIL PROTECTED]> writes:
>>>>>> "adl" == Alexandre Duret-Lutz <[EMAIL PROTECTED]> writes:
[...]
Tom> If there is no vendor install program, autoconf will choose
Tom> install-sh. The path to install-sh might be a relative path, because
Tom> $srcdir might be relative. However if we set INSTALL_PROGRAM and
Tom> invoke $(MAKE), the new value will be passed to subdir Makefiles --
Tom> where it will be wrong.
Your explanation is clear, but now I'm confused :) Because
before sending the patch I configured my package with
../configure --host=i386-mingw32msvc and did `make
install-strip' with success. If I'm correct, running ../configure
implies $srcdir = .. and thus $install_sh is relative. However
install-strip succeded! I will double check tonight to be sure;
anyway I now have to understand *why* it works :o)
[...]
adl> `install -s' does not work on cross-compiled programs. Therefore,
adl> when configuring a package for cross-compilation, check for some
adl> suitable `strip' and arrange the Makefiles so that `install-strip'
adl> will run `install-sh' with `STRIPPROG' set to the detected `strip'.
Tom> One nit: comments like this should go in the code, not in the
Tom> ChangeLog.
I will put more comments in the code. But since the changes are
dispersed through automake, the comments will be dispersed as
well. So may be it would be nice to find a place to put
such a sumary (well, maybe in that case it's not really needed,
but in general I find verbose ChangeLog entries helpful).
Tom> In order to install a patch of this size I'll definitely need
Tom> paperwork from you. Unfortunately the FSF has changed the procedure
Tom> recently, and I still don't know the new method. It will be a few
Tom> days until I dig up the new procedure and get the information to you
Tom> :-(.
No problem.
Tom> (Unless you've already filled it out and I've simply
Tom> forgotten, which is a definite possibility.)
No, I have not.
--
Alexandre Duret-Lutz
