[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: back quotes and double quotes must not be escaped?
From: |
Andrew Suffield |
Subject: |
Re: back quotes and double quotes must not be escaped? |
Date: |
Mon, 4 Nov 2002 14:32:02 +0000 |
User-agent: |
Mutt/1.4i |
On Mon, Nov 04, 2002 at 09:09:50AM +0100, Akim Demaille wrote:
> | configure.ac:27: warning: back quotes and double quotes must not be escaped
> in: $as_me:$LINENO: WARNING: \`$CC' requires \`$lt_cv_prog_cc_shlib' to build
> shared libraries
> | configure.ac:27: warning: back quotes and double quotes must not be escaped
> in: $as_me: WARNING: \`$CC' requires \`$lt_cv_prog_cc_shlib' to build shared
> libraries
> | configure.ac:27: warning: back quotes and double quotes must not be escaped
> in: $as_me:$LINENO: WARNING: add \`$lt_cv_prog_cc_shlib' to the CC or CFLAGS
> env variable and reconfigure
>
> This is not automake, but autoconf speaking. 2.55 will re-disable
> this warning until Libtool has this fixed :( Sorry.
This seems to be a common source of confusion. Would it be unrealistic
to ask that autoconf/automake insert $0 into warning/error messages?
Something like
configure.ac:27: autoconf: warning: ...
--
.''`. ** Debian GNU/Linux ** | Andrew Suffield
: :' : http://www.debian.org/ | Dept. of Computing,
`. `' | Imperial College,
`- -><- | London, UK
pgpf2dnzP2ovw.pgp
Description: PGP signature