Hi Bruno,
* Bruno Haible wrote on Fri, May 22, 2009 at 01:37:42AM CEST:
> * Call the `AM_SILENT_RULES' macro from within the
> `configure.ac' file."
>
> I'm trying to use the second option, because I'm using AM_INIT_AUTOMAKE
> in the old 2-arguments form.
>
> After running 'acl
Hi,
The automake 1.11 documentation says that to enable silent rules:
"The developer needs to do either of the following:
* Add the `silent-rules' option as argument to
`AM_INIT_AUTOMAKE'.
* Call the `AM_SILENT_RULES' macro from within the
`configure.ac'
Hi Thien-Thi,
* Thien-Thi Nguyen wrote on Thu, May 21, 2009 at 12:29:06PM CEST:
> Please find attached specflg10.log;
> is there any other info that can be of help?
>
> I suspect this is related to absense of g++ on the computer.
Yep. Fixed as follows. Thanks for the report!
Cheers,
Ralf
Please find attached specflg10.log;
is there any other info that can be of help?
I suspect this is related to absense of g++ on the computer.
thi
specflg10.log
Description: Binary data
Ralf Wildenhues wrote:
> Hi Matthias, Peter,
>
> * Matthias Klose wrote on Thu, May 21, 2009 at 08:11:49AM CEST:
>> Peter O'Gorman schrieb:
>>> This patch works for me. Thoughts?
>
>>> 2009-??-?? Peter O'Gorman
>>> m4/python.m4: Ensure that pythondir and pyexecdir are below
>>> ${prefix
Hi Matthias, Peter,
* Matthias Klose wrote on Thu, May 21, 2009 at 08:11:49AM CEST:
> Peter O'Gorman schrieb:
> > This patch works for me. Thoughts?
> > 2009-??-?? Peter O'Gorman
> > m4/python.m4: Ensure that pythondir and pyexecdir are below
> > ${prefix}.
>
> why special case /usr an
