On Tue, Sep 05, 2000 at 11:26:56AM +0200, Akim Demaille wrote:
> > "Tom" == Tom Tromey <[EMAIL PROTECTED]> writes:
>
> Tom> We should automate this process. I've wanted to for a long time.
> Tom> Does autoconf have the hooks we need?
>
> Yes it has:
>
> - Macro: AC_CONFIG_COMMANDS_PRE(CMD
Subject: Blind fix for wierd test ordering in configure
From: "Gary V. Vaughan" <[EMAIL PROTECTED]>
Date: Sat, 9 Sep 2000 14:03:00 +0100
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
User-Agent: Mutt/1.2.5i
In libtool.m4 in CVS HEAD, without this patch, the tests for AC_EXEEXT
and a couple of other
On Sep 9, 2000, Richard Stallman <[EMAIL PROTECTED]> wrote:
> However on systems with shared libraries you can't just "promote" a
> linked program from /usr/bin to /bin -- you have to link it statically
> -- i.e. the build has to know from the beginning that you're intending
> to
On Sat, Sep 09, 2000 at 10:19:53PM -0300, Alexandre Oliva wrote:
> The point of having binaries in `/bin' instead of `/usr/bin' is so
> that you can run them without mounting /usr. Instead of figuring out
> which shared libraries they depend on, copying them to /lib and
> remembering to do so eve
Let me take the example of a2ps. a2ps uses a configuration file which
is installed in syscondir. To find it the path is hard coded in a2ps,
and a natural means to do that would be
AC_DEFINE_UNQUOTED([A2PS_CONFIG_FILE], ["$sysconfdir/a2ps.cfg"])
The natural way to implement it a
So since configure supports VAR=VAL, since this is a perfect scheme
which is completely extendible, I was noting that this scheme was
enough to support all the foodir variables we might need.
We will stay with the --foo syntax for configure options. We should
not change the configure
On Sep 10, 2000, Richard Stallman <[EMAIL PROTECTED]> wrote:
> So since configure supports VAR=VAL, since this is a perfect scheme
> which is completely extendible, I was noting that this scheme was
> enough to support all the foodir variables we might need.
> We will stay with the -
