This is the mail archive of the
mailing list for the GCC project.
Re: GCC_NO_EXECUTABLES in libbanshee/configure.in
- From: Daniel Jacobowitz <drow at false dot org>
- To: Andreas Jaeger <aj at suse dot de>
- Cc: Diego Novillo <dnovillo at redhat dot com>, gcc-patches at gcc dot gnu dot org
- Date: Fri, 26 Mar 2004 10:51:55 -0500
- Subject: Re: GCC_NO_EXECUTABLES in libbanshee/configure.in
- References: <firstname.lastname@example.org> <email@example.com>
On Fri, Mar 26, 2004 at 09:21:32AM +0100, Andreas Jaeger wrote:
> Diego Novillo <firstname.lastname@example.org> writes:
> > Andreas,
> > According to cvs ann, you added GCC_NO_EXECUTABLES to configure.in back
> > in Feb29. We get an error from that line when configuring the branch
> > src/libbanshee/configure: line 2882: GCC_NO_EXECUTABLES: command not found
> > However, things seem to work just the same.
> > Could you take a look?
> Oops, I've never seen that before - but it appears here also.
> Can you try the appended patch? I'm CC'ing gcc-patches to get your
> approval ;-)
> This patch works for me (just tested on x86_64-linux-gnu).
> Ok to commit?
> +# The autoconf 2.5x version of the no-executables hack.
In Autoconf 2.59, we can probably use AC_NO_EXECUTABLES instead. It
should be basically the same as GCC_NO_EXECUTABLES.
But why does libbanshee need this at all? It's not a target library;
if all you want is $GCC, then AC_PROG_CC will set it.
MontaVista Software Debian GNU/Linux Developer