Tom Tromey <[EMAIL PROTECTED]> wrote
Fri, 4 Feb 2000 15:01:20 -0800 (PST):
Linus> We are working with Autoconf based configuration for GMP.
I have a certain amount of interest in this. I'd like to make sure it
is possible to build GMP as a target library so that we can build it
(
Alexandre Oliva <[EMAIL PROTECTED]> wrote
16 Feb 2000 02:21:44 -0200:
On Feb 16, 2000, NIIBE Yutaka <[EMAIL PROTECTED]> wrote:
> You know, "unknown" does not look good, specifically, it's unclear
> that it is intended or not.
Well, it's used in the exact situation you describe
Alexandre Oliva <[EMAIL PROTECTED]> wrote
23 Feb 2000 03:37:23 -0300:
> How do one get on the [EMAIL PROTECTED] list?
It's not a mailing list, just an alias for whoever is the current
maintainer of those files.
Ah. Do you know where the ``official'' version of config.guess is
expec
Akim Demaille <[EMAIL PROTECTED]> wrote
16 Mar 2000 19:16:48 +0100:
In fact if someone has broken IFS, typically lacking nl, then the
sanity check from Automake will fail, telling the there is a severe
clock skew, while it's only the
set X `ls -Lt $srcdir/configure conftestfile
Akim Demaille <[EMAIL PROTECTED]> wrote
17 Mar 2000 16:05:33 +0100:
I preferred the former order because so that the white chars are never
last on the line.
IFS="
"
is more explicit than
IFS="
"
It may look good, but I don't think it's worth it sin
Giving a shell variable to AC_CONFIG_LINKS like this doesn't work in
recent CVS versions of Autoconf:
foo="link:file"
AC_CONFIG_LINKS($foo)
I assume it's because `config_links' is set in config.status by
configure doing
cat >$CONFIG_STATUS <<\EOF
[...]
co
Akim Demaille <[EMAIL PROTECTED]> wrote
25 May 2000 18:26:51 +0200:
Is it really important for you to be able to use variables?
Yes. We symlink a number of source files to the build directory. The
number of files may vary for different targets. The source file name
varies depending on wh
