Suppose I have something like:
AC_DEFUN(FOO, [AC_CONFIG_FILES($1/Makefile)])
FOO(somedir)
This works fine with autoconf, but is there some way to convince
automake about this construct? Is there an alternate way to do the
same thing?
/Johan
Akim Demaille <[EMAIL PROTECTED]> writes:
> What kind of warnings are you referring to? I tried on a couple of
> packages and didn't find many related to Automake.
AC_OUTPUT_COMMANDS and friends, AC_CHECK_TOOL_PREFIX, AC_LANG_SAVE,
AC_DECL_YYTEXT.
/Johan
What's the deal? If you run autoconf -W obsolete you get a bunch of
warnings for automake stuff.
/Johan
[EMAIL PROTECTED] (Sascha Demetrio) writes:
> I've seen -q for ``Quiet mode'' and -q for ``Question mode''
> (i.e. check if the target is up-to-date without building it).
Care to give an example of a make where -q means quiet?
The historically interested can note what Stuart Feldman's 7th editi
Alexandre Oliva <[EMAIL PROTECTED]> writes:
> You may want to ask Michael Sokolov <[EMAIL PROTECTED]>, the
> current maintainer of 4.3BSD. If it works on 4.3BSD, it can
> probably work anywhere :-)
3BSD had it.
/Johan
John Fremlin <[EMAIL PROTECTED]> writes:
> > Please don't use glob. It's broken.
>
> Sorry, I don't understand how )-:
There are many problems. One problem not mentioned is that csh (on
some platforms) like to stat just about every file it can find. This
is not a big deal on most machines, but
John Fremlin <[EMAIL PROTECTED]> writes:
> + local @list = glob($relative_dir);
Please don't use glob. It's broken.
/Johan
