| Akim,
Hi! Thanks Harlan!
| chmod +x testsuite-tmp
| mv testsuite-tmp testsuite
| /bin/sh testsuite
| /bin/sh: illegal io
| /bin/sh: illegal io
| /bin/sh: illegal io
That was to be expected. If you could send a snippet of sh -x
testsuite maybe we could fix the test suite on Ultrix, which wo
> "Ralf" == Ralf Corsepius <[EMAIL PROTECTED]> writes:
Ralf> => Random (== BROKEN) behaviour.
No, undefined == undefined.
This has *never* been part of Autoconf, and the lack of sense of
2.13's answers are quite a demonstration of it.
My sentence was `Garbage in, garbage out'.
Even if w
> "Alexandre" == Alexandre Oliva <[EMAIL PROTECTED]> writes:
Alexandre> The issue raised by Ralf Corsepius is a very important one,
Alexandre> IMO.
Arg, forgot to CC you in the answer I just sent.
On Jan 24, 2001, Akim Demaille <[EMAIL PROTECTED]> wrote:
Ralf> * The CONFIG_FILES section trashes variables a user explicitly
Ralf> sets in AC_CONFIG_COMMANDS.
> Huh? I'll reread your message about that. But of course if the user
> uses Autoconf variables... :)
srcdir should not be trashed.
> "Alexandre" == Alexandre Oliva <[EMAIL PROTECTED]> writes:
Alexandre> srcdir should not be trashed. My understanding is that it
Alexandre> is. Maybe I mis-read Ralf's posting?
Nope, I probably did. I fix this right away.
>> Where is it?
Alexandre> http://gcc.gnu.org/cgi-bin/cvsweb.cgi
Here is my proposal. I ran the foo-0 package from Ralf and it
consistently leaves top_srcdir undefined, and srcdir points to
configure.in when (i) ./configure, (ii), ../configure, (iii)
/tmp/foo-0/configure.
Index: acgeneral.m4
===
Err, maybe $INSTALL should be preserved too?
The improved version. make check is running and up to 50 (i.e.,
torture is passed), everything is fine. My previous questions still
apply :)
Index: ChangeLog
from Akim Demaille <[EMAIL PROTECTED]>
While preserved in configure, srcdir is trashed in config.status.
Reported by R
Akim Demaille wrote:
>
> Err, maybe $INSTALL should be preserved too?
Let me put it this way: All well-known (may they be explictly
documented or not :) shell-variables should be preserved.
This comprises includedir, libdir, target, host, build, prefix,
exec_prefix and many more.
AFAIS from my
> "Ralf" == Ralf Corsepius <[EMAIL PROTECTED]> writes:
Ralf> Akim Demaille wrote:
>> Err, maybe $INSTALL should be preserved too?
Ralf> Let me put it this way: All well-known (may they be explictly
Ralf> documented or not :) shell-variables should be preserved.
I agree.
Ralf> This comprises
On Jan 24, 2001, Akim Demaille <[EMAIL PROTECTED]> wrote:
> My previous questions still apply :)
:-)
I agree with Ralf. No visible variables should be modified.
> While preserved in configure, srcdir is trashed in config.status.
> Reported by Ralf Corsepius.
Ok after you arrange
> "Alexandre" == Alexandre Oliva <[EMAIL PROTECTED]> writes:
Alexandre> Ok after you arrange for INSTALL to be preserved too :-)
OK, the patch will follow this one.
> "Akim" == Akim Demaille <[EMAIL PROTECTED]> writes:
Akim> As for INSTALL, I'll do that in a separate patch, that one is
Akim> big enough as is.
FYI:
Index: ChangeLog
from Akim Demaille <[EMAIL PROTECTED]>
Preserve INSTALL too.
* acgeneral.m4 (_AC_OUTPUT_FILES): Use ac_I
On Tue, Jan 23, 2001 at 04:32:21PM -0800, Russ Allbery wrote:
: Akim Demaille <[EMAIL PROTECTED]> writes:
: > Hm, why not. Nice suggestion. I'd propose `AC_PROG_PERL' since
: > that's an already common means to `quote'.
:
: I'd recommend against standardizing on *new* stuff that has the uneven
speak now!
I intend to make it in the end of the French afternoon, i.e., within,
say, 4 hours.
There is apparently a bug in autoconf: when calling AC_CHECK_LIB, it uses -l and -L in
the wrong order. It does not disturb gcc or Tru64's cc, but it fails with Sun's cc.
With the configure.in attached, this fails:
./configure --with-ssl=$HOME
with the following config.log:
configure:795: cc
@defvar LDFLAGS
@ovindex LDFLAGS
Stripping (@option{-s}), path (@option{-L}), and any other miscellaneous
options for the linker. Don't use this variable to pass library names
(@option{-l}) to the linker, use @code{LIBS} instead. If it is not set
in the environment when @code{configure} runs, th
On Jan 24, 2001, Stephane Bortzmeyer <[EMAIL PROTECTED]> wrote:
> Because -L was put too late.
It should probably be in LDFLAGS, not LIBS.
> Indeed, the fault seems to be in acgeneral.m4, when defining AC_CHECK_LIB:
> LIBS="-l$1 $5 $LIBS"
> IMHO, it should be:
> LIBS="$LIBS -l$1 $5"
Nope.
The following message is a courtesy copy of an article
that has been posted to gnu.utils.bug as well.
The Autoconf team is extremely proud (and quite relieved) to announce
the birth of Autoconf 2.49c, our release candidate. The core Autoconf
is not expected to change before the release, while t
I'd like to add (at some point) a macro that detects the path separator
used on the _build_ system. This is important for:
a) the path walking macros; they set IFS to ':' assuming this will
break up the PATH into its constituent directories.
b) MANY makefiles, which often use PATH=../src:$PA
Akim Demaille wrote:
> [...] Autoconf 2.49c, our release candidate. The core Autoconf
> is not expected to change before the release, while the documentation
> and minor details still need some work.
> [...]
> Autoconf can be downloaded from
>
> ftp://alpha.gnu.org/gnu/autoconf/autoconf
> "Tim" == Tim Van Holder <[EMAIL PROTECTED]> writes:
Tim> I'd like to add (at some point) a macro that detects the path
Tim> separator used on the _build_ system.
It's fine with me. I'd check a patch implementing it into automake.
I don't know the answer to your problems though.
Tom
Why can't I use AS_* macros from configure.in?
Derek
--
Derek Price CVS Solutions Architect ( http://CVSHome.org )
mailto:[EMAIL PROTECTED] OpenAvenue ( http://OpenAvenue.com )
--
Were we directed from Washington when to sow and when to reap, we would soon
want bread.
"Derek R. Price" wrote:
> Why can't I use AS_* macros from configure.in?
Oh. I can't call them from Automake macros... anyone know why that doesn't
work? It generates the following error:
[dprice@empress ccvs-automake]$ autoconf
configure:6517: error: undefined macro: AS_MKDIR_P
Derek
--
D
"Derek R. Price" wrote:
> > Why can't I use AS_* macros from configure.in?
>
> Oh. I can't call them from Automake macros... anyone know why that doesn't
> work? It generates the following error:
>
> [dprice@empress ccvs-automake]$ autoconf
> configure:6517: error: undefined macro: AS_MKDIR_P
Akim,
I installed that version of autoconf and put your script in a file
called "foo":
stenn@porkypine> sh foo
configure: loading cache /dev/null
configure: creating ./config.status
config.status: creating file
config.status: creating header.h
BAR
/* header.h. Generated automatically by configu
Akim,
Here's the sh -x testsuite snippet.
Harlan
---
...
+ cd ..
+ pwd
at_top_srcdir=/home/stenn/src/gnu/autoconf
+ pwd
at_path=/home/stenn/src/gnu/autoconf/tests
at_IFS_save=
IFS=:
+ cd ..
sh: illegal io
at_dir=
+ test -n
+ cd /usa/stenn/bin
sh: illegal io
at_dir=
+ test -n
+ cd /usr/local/bi
27 matches
Mail list logo
