| Index: ChangeLog
| from Akim Demaille [EMAIL PROTECTED]
|
| * autoconf.sh (finalize.awk): Don't discard comments when looking
| for unexpanded tokens.
| Adjust Autoconf and its test suite.
I think there should be at least a small debate about this one. What
"Patrick" == Patrick Welche [EMAIL PROTECTED] writes:
Patrick What is foreign.at:24: AT_CHECK([libtoolize | sed -n
Patrick ["s,^.*\`\(/[^']*\)'.*,\1,p"] at-path], 0, [], ignore)
Patrick trying to do?
Patrick For me:
Patrick quartz% libtoolize --version libtoolize (GNU libtool) 1.3c
Patrick
"Akim" == Akim Demaille [EMAIL PROTECTED] writes:
Akim do not use it.
Fixed, go ahead.
Sorry for this OTish post, but I figured the list has excellent
expertise in this area ...
I need to implement a configure check for waitpid(). While this by
itself is trivial, are there any known abnormalities/non-POSIXisms
I need to consider? Also, are there any concrete examples of
On Thu, Jan 18, 2001 at 11:14:50AM +0100, Akim Demaille wrote:
Could you run
cd tests/
./testsuite -d -v -x 173
# it should fail, but run this anyway:
libtoolize 2/dev/null
quartz% ./testsuite -d -v -x 172
Testing suite for GNU Autoconf 2.49c
| ./foreign.at:25: libtoolize | sed -n "s,^.*\`\(/[^']*\)'.*,\1,p" at-path
| + at_status=0
| + set +vx
| + libtoolize
| + sed -n s,^.*`\(/[^']*\)'.*,\1,p
| libtoolize: `configure.in' does not exist
Waf waf waf! Stupid me. Yeah, of course, libtoolize does not know
about configure.ac (yet).
On Jan 18, 2001, Akim Demaille [EMAIL PROTECTED] wrote:
| Index: ChangeLog
| from Akim Demaille [EMAIL PROTECTED]
|
| * autoconf.sh (finalize.awk): Don't discard comments when looking
| for unexpanded tokens.
| Adjust Autoconf and its test suite.
I
"Russ" == Russ Allbery [EMAIL PROTECTED] writes:
Russ Assar Westerlund [EMAIL PROTECTED] writes:
And I've not merged my brain with m4 but it wasn't obvious to me
that I needed to add some m4-code inside the test just because I
used a string starting with AF* in my C-code.
Russ I think it's
| I'd like to request the following changes in file names for some future
| version of autoconf:
|
| -) use acversion.in, not acversion.m4.in
|reason: not all systems support multiple dots in filenames
|
| A similar problem exists in the man directory (the config.guess and
| config.sub man
"Tim" == Tim Van Holder [EMAIL PROTECTED] writes:
Tim As part of my DJGPP patches (still being refined), I made this a
Tim variable (ac_test_f), which defaults to '-f'. Site files can then
Tim override this (so systems like DOS or NT can simply put
Tim ac_test_f='-x' in their config.site and
Alexandre, help!
"Lars" == Lars J Aas [EMAIL PROTECTED] writes:
Lars I've attached a config.log that shows more problems with exit().
Lars The problem is that the Visual C++ compiler thinks exit is
Lars declared to be exported from the library it is compiling, and
Lars not to be imported from
"Alexandre" == Alexandre Oliva [EMAIL PROTECTED] writes:
Alexandre How about an additional -W flag that would enable searching
Alexandre for macro names within comments? It would be disabled by
Alexandre default, but we'd use it in our own testsuite.
Yep, that's proposal number 2 :) Well, as
On Jan 18, 2001, "Lars J. Aas" [EMAIL PROTECTED] wrote:
I've attached a config.log that shows more problems with exit().
We should probably move the '' case first. This will probably work
with VC++, and will be fine for most existing C++ compilers.
--
Alexandre Oliva Enjoy Guarana', see
"Alexandre" == Alexandre Oliva [EMAIL PROTECTED] writes:
Alexandre On Jan 18, 2001, "Lars J. Aas" [EMAIL PROTECTED] wrote:
I've attached a config.log that shows more problems with exit().
Alexandre We should probably move the '' case first. This will
Alexandre probably work with VC++, and
On Jan 18, 2001, Akim Demaille [EMAIL PROTECTED] wrote:
I'd be OK with making this a warning, at least that's much more
conventional and understandable. And WARNINGS=error restores the old
behavior.
Agreed.
-W forbidden-tokens
-W forbidden-tokens-in-comments
Yep.
--
Alexandre Oliva
On Jan 18, 2001, Akim Demaille [EMAIL PROTECTED] wrote:
| I'd like to request the following changes in file names for some future
| version of autoconf:
|
| -) use acversion.in, not acversion.m4.in
|reason: not all systems support multiple dots in filenames
|
| A similar problem
On Thu, Jan 18, 2001 at 02:52:33PM +0100, Akim Demaille wrote:
: I have no problem with adding in Autoconf a list of common
: exceptions. If you want it to be silent with AF_INET, fine, I'm ready
: to check this exception in. Just send me a list of valid tokens
: looking like unexpanded macros.
"Alexandre" == Alexandre Oliva [EMAIL PROTECTED] writes:
Alexandre Not if acversion.m4.in appears after acversion.m4 in the
Alexandre tar-file. In this case, it would be overwritten.
Pfff.
Nevertheless, you'll see that the test suite uses config.hin to
make your life easier.
Alexandre How
"Lars" == Lars J Aas [EMAIL PROTECTED] writes:
Lars I believe `AR_FLAGS' has been mentioned in the same context a
Lars couple of times. `AS_FLAGS' for the assembler?
Right.
Up to now AF_INET, A[RS]_FLAGS.
| On Jan 18, 2001, Akim Demaille [EMAIL PROTECTED] wrote:
| I'd be OK with making this a warning, at least that's much more
| conventional and understandable. And WARNINGS=error restores the old
| behavior.
|
| Agreed.
|
| -W forbidden-tokens
| -W forbidden-tokens-in-comments
|
| Yep.
On Thu, Jan 18, 2001 at 03:13:02PM +0100, Akim Demaille wrote:
: "Alexandre" == Alexandre Oliva [EMAIL PROTECTED] writes:
:
: Alexandre On Jan 18, 2001, "Lars J. Aas" [EMAIL PROTECTED] wrote:
: I've attached a config.log that shows more problems with exit().
:
: Alexandre We should probably
"Lars" == Lars J Aas [EMAIL PROTECTED] writes:
Lars I noticed that when I moved '' first, the first exit(42) test
Lars didn't include stdlib.h - is that right?
Yes, it does, but you didn't see it because it didn't fail. The test
goes in two steps:
do
Akim Demaille [EMAIL PROTECTED] writes:
I have no problem with adding in Autoconf a list of common exceptions.
If you want it to be silent with AF_INET, fine, I'm ready to check this
exception in. Just send me a list of valid tokens looking like
unexpanded macros.
That works. Thanks! You
"Russ" == Russ Allbery [EMAIL PROTECTED] writes:
Russ That works. Thanks!
No need to thank me, on the contrary it seems I was the problem, not
the answer :)
Here's what I'm checking in.
Index: ChangeLog
from Akim Demaille [EMAIL PROTECTED]
* acgeneral.m4 (AC_PLAIN_SCRIPT):
-Original Message-
From: Akim Demaille [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 18, 2001 3:32 PM
To: Lars J. Aas
Cc: Russ Allbery; Autoconf List
Subject: Re: undefined macro: AF_INET ?
"Lars" == Lars J Aas [EMAIL PROTECTED] writes:
Lars I believe `AR_FLAGS' has
Just cvs updated, and this time got a new:
Testing suite for GNU Autoconf 2.49c
69. ./syntax.at:27: testing AC_F77_WRAPPERS...
+ cat
+ set +vx
./syntax.at:27: autoconf --autoconf-dir .. -l $at_srcdir
+ at_status=0
+ set
Arg, answered too fast, didn't pay attention to the fact you were
presenting a different failure :*(
Expect a libtool failure, but any other failure is wrong. But if you
used `-x'.
| Just cvs updated, and this time got a new:
|
| Testing suite for GNU Autoconf 2.49c
|
| 69. ./syntax.at:27: testing AC_F77_WRAPPERS...
| + cat
| + set +vx
| ./syntax.at:27: autoconf --autoconf-dir .. -l $at_srcdir
| +
"Bernard" == Bernard Dautrevaux [EMAIL PROTECTED] writes:
Bernard I know we also use AT_, but that's for autotest, so I'm not
Bernard sure its useful for autoconf to check these are all expanded:
Bernard if they aren't, the test will fail anyway :-)
Sure, but the point is also in reserving the
Akim Demaille wrote:
Alexandre, help!
"Lars" == Lars J Aas [EMAIL PROTECTED] writes:
Lars I've attached a config.log that shows more problems with exit().
Lars The problem is that the Visual C++ compiler thinks exit is
Lars declared to be exported from the library it is compiling,
Lars Hecking [EMAIL PROTECTED] writes:
Sorry for this OTish post, but I figured the list has excellent
expertise in this area ...
I need to implement a configure check for waitpid(). While this by
itself is trivial, are there any known abnormalities/non-POSIXisms
I need to consider?
On Thu, Jan 18, 2001 at 05:06:19PM +0100, Akim Demaille wrote:
Arg, answered too fast, didn't pay attention to the fact you were
presenting a different failure :*(
Expect a libtool failure, but any other failure is wrong. But if you
used `-x'.
I don't know what I'm doing! So, this time
On Jan 18, 2001, Akim Demaille [EMAIL PROTECTED] wrote:
"Lars" == Lars J Aas [EMAIL PROTECTED] writes:
Lars I noticed that when I moved '' first, the first exit(42) test
Lars didn't include stdlib.h - is that right?
Yes, it does, but you didn't see it because it didn't fail. The test
goes
"Patrick" == Patrick Welche [EMAIL PROTECTED] writes:
Patrick On Thu, Jan 18, 2001 at 05:06:19PM +0100, Akim Demaille
Patrick wrote:
Arg, answered too fast, didn't pay attention to the fact you were
presenting a different failure :*(
Expect a libtool failure, but any other failure is
In particular, it would be very useful if you knew what the answer is
expected to be. Since you seem to use G77 and GCC, I expect you
should have the same answer as I have (but I'm running Linux, maybe
that makes a difference? Don't know).
Just in case it might help someone help us :), my log
On Thu, Jan 18, 2001 at 05:30:13PM +0100, Akim Demaille wrote:
Patrick I don't know what I'm doing! So, this time without -x (and it
Patrick passed yesterday..):
Do you still have yesterday's Autoconf? If so, it might help us
understanding what happened by diffing the two outputs on
Akim Demaille wrote:
"Alexandre" == Alexandre Oliva [EMAIL PROTECTED] writes:
Alexandre Not if acversion.m4.in appears after acversion.m4 in the
Alexandre tar-file. In this case, it would be overwritten.
Pfff.
Nevertheless, you'll see that the test suite uses config.hin to
make
Having one semi-functional compiler wrapper for MS Visual C++, and
another one for Borland C++ coming along nicely, I've started thinking
of how this should be integrated with the Auto-tools.
What I have come up with is a scheme something like this:
1) The scripts are installed in $auxdir.
2)
From: Lars Hecking [EMAIL PROTECTED]
Date: Thu, 18 Jan 2001 11:06:40 +
I need to implement a configure check for waitpid(). While this by
itself is trivial, are there any known abnormalities/non-POSIXisms
I need to consider?
Not as far as I know, if you confine yourself to the
Not only gross, it wouldn't work on DOS anyway. DOS has a 8.3 filename
limit. I think these kind of limitations will have to resort to cross
building to the non-compliant systems. Leave it alone.
Actually, on DJGPP (and I think this is currently the only DOS environment
that is unixy enough
Hello Everyone,
From the CVS autoconf documentation, it appears that you can preset
certain compiler/linker names and flags before running configure by
doing the following:
./configure CC=/usr/local2/bin/gcc
I need to find a comprehensive list of variables that you can set in
this way.
"Lars J. Aas" wrote:
Having one semi-functional compiler wrapper for MS Visual C++, and
another one for Borland C++ coming along nicely, I've started thinking
of how this should be integrated with the Auto-tools.
What I have come up with is a scheme something like this:
1) The scripts
If this thread had to do about the report I sent in where I was getting
strange collisions when building outside of the srcdir, I have been
unable to repeat the problem.
I recall sending an email saying that the problem was probably related
to an environmen change and some build scripts we use
Folks have recently discussed things like "egcs_update" and other
related scripts that attempt to check out/update certain "master" files
before doing a checkout of "derived" files.
I was thinking about this, as I've hacked egcs_update for 2 other
project to get around the same problem on
Michael Bletzinger wrote:
From the CVS autoconf documentation, it appears that you can preset
certain compiler/linker names and flags before running configure by
doing the following:
./configure CC=/usr/local2/bin/gcc
I need to find a comprehensive list of variables that you can set in
45 matches
Mail list logo
