* Stefano Lattarini wrote on Tue, Sep 07, 2010 at 06:00:04PM CEST:
> Darn, I've been sloppy: I should have also asked you to provide
> us with the (tarred) content of the temporary test directory
> `tests/silent5.dir'. Could you kindly send this over to the list
> too?
>
> ( to self and to Ralf:
Hello,
* Yavor Doganov wrote on Tue, Sep 07, 2010 at 10:17:07AM CEST:
> В Mon, 06 Sep 2010 11:32:54 +0100, Roger Leigh написа:
>
> > I'd like to suggest that the best way to tackle the problem is to
> > simply stop generating the source file/line number comments by
> > default; I'm already doing
Hi Paolo,
* Paolo Bonzini wrote on Tue, Sep 07, 2010 at 07:10:39PM CEST:
> While looking around at the most common shell idioms in otherwise
> "simple" configure.ac files, I found a very common one:
>
> AC_ARG_ENABLE([something], [--enable-somethingxyz],,
>[enable_something=no])
> AM_COND
On Tue, 7 Sep 2010, Stefano Lattarini wrote:
You've got it Toyota!
Sorry?
Here in the USA, we were inundated for many years by adds from Toyota
with the above message. :-)
And by looking at the files `tests/silent5.dir/Makefile' and
`tests/silent5.dir/config.log', it's easy to detect the
While looking around at the most common shell idioms in otherwise
"simple" configure.ac files, I found a very common one:
AC_ARG_ENABLE([something], [--enable-somethingxyz],,
[enable_something=no])
AM_CONDITIONAL([SOMETHING, [test "$enable_something" != no])
What would you think about on
В Mon, 06 Sep 2010 11:32:54 +0100, Roger Leigh написа:
> I'd like to suggest that the best way to tackle the problem is to
> simply stop generating the source file/line number comments by
> default; I'm already doing this in some of my projects by adding
> "--no-location" to XGETTEXT_OPTIONS in po
