[...] > It says: > > If you use AC_PROG_INSTALL, you must include either install-sh or > install.sh in your distribution; otherwise configure produces an error > message saying it can't find them, even if the system you're on has a > good install program. This check is a safety measure to prevent you > from accidentally leaving that file out, which would prevent your > package from installing on systems that don't have a BSD-compatible > install program. > > so it even says why. Somewhere there is a system where it will be used, > if it works. Autotools is about being able to build on systems that are > ancient, hybrid, or just plain weird. I think it's behaving as designed > and that the design makes sense. > > I also think that you can't expect configure to work in a brand-new > checkout unless the project explicitly says that it will (in which case > the project is fine with checking in built files, like configure). There > is almost always a need for some sort of "prepare" step. > > Sorry for rant, touched a nerve.
Hi Eric, rants allowed (since as you can tell the original problem also touched a nerve). But if the install-sh is distributed with autoconf why can't it use it? Install it in autopconf's data area and go look there if it isn't present in . or .. or ../.. And copy it into the distribution if it is needed by make dist. But don't enforce what might be a project requirement on users whose systems have a perfectly workable install, its not their fault. Cheers Lex > > Eric > -- -- You received this message because you are subscribed to the Google Groups "asciidoc" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/asciidoc?hl=en.
