The index and search of the docs only yields this:
`AM_PROG_CC_C_O'
This is like `AC_PROG_CC_C_O', but it generates its results in the
manner required by automake. You must use this instead of
`AC_PROG_CC_C_O' when you need this functionality, that is, when
using per-target fl
* Bruce Korb wrote on Mon, Apr 30, 2007 at 12:04:53AM CEST:
> The index and search of the docs only yields this:
>
> `AM_PROG_CC_C_O'
> This is like `AC_PROG_CC_C_O', but it generates its results in the
> manner required by automake. You must use this instead of
> `AC_PROG_CC_C_O'
Hello John,
* John Faith wrote on Fri, Apr 27, 2007 at 07:07:19PM CEST:
> I am trying to configure Inkscape on OS X 10.3.9 with autoconf 2.61
> from MacPorts. In config.log, I see:
> INTLTOOL_MSGFMT='/opt/local/bin/msgfmt'
>
> , but later:
> MSGFMT=''
>
> , which causes the build to fail sinc
Ralf Wildenhues <[EMAIL PROTECTED]> writes:
> * Bruce Korb wrote on Mon, Apr 30, 2007 at 12:04:53AM CEST:
>> The index and search of the docs only yields this:
>> `AM_PROG_CC_C_O'
>> This is like `AC_PROG_CC_C_O', but it generates its results in the
>> manner required by automake. You
Quoting Ralf Wildenhues <[EMAIL PROTECTED]>:
Presumably, AC_PROG_INTLTOOL comes from
GNOME's intltool package, and the MSGFMT setting from some gettext
macros.
*sighs*
When will people understand the concept of pseudo-reserved-namespace?
Is there any reason why autoconf does not emit a warning
