[snipped totally correct reasoning]
So, for potential efficiency purposes, should we rewrite this line to use:
as_lineno_stack=$as_lineno_stack=as_lineno_stack
Actually as_lineno_stack=${as_lineno_stack}as_lineno_stack=
or maybe even write AS_APPEND([var],[text]), which expands to a shell
Much to my surprise, the only testcase that tries using multiple
languages in the Autoconf testsuite is... the Libtool integration test!
And I'm not even sure it does with Libtool 2.x.
So, I'm pushing this one.
Paolo
2008-10-15 Paolo Bonzini [EMAIL PROTECTED]
* tests/compile.at
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Eric Blake on 10/13/2008 5:55 AM:
AUTOTEST = $(AUTOM4TE) --language=autotest
-$(TESTSUITE): $(srcdir)/testsuite.at
+$(TESTSUITE): $(srcdir)/package.m4 $(srcdir)/testsuite.at
This looks like a correct dependency (at any rate, GNU
While trying to figure out whether m4_curry will be a win or not, I noticed
this low-hanging fruit. It dropped the speed of 'autoconf -f' on coreutils
from 16.441s to 15.786s (or about 4% improvement).
$ autoconf --trace _m4_text_wrap:'$n' | wc -l
882
$ autoconf --trace m4_qlen:'$n' | wc -l
Here is a prepare-commit-msg hook to make commit messages from ChangeLog
entries.
Paolo
#!/bin/sh
#
# An example hook script to prepare the commit log message.
# Called by git-commit with the name of the file that has the
# commit message, followed by the description of the commit
# message's
Brian Dessent wrote:
Barry Leslie wrote:
It would be really useful if there was a configure option that would allow
you to point to another location and tell configure to get it's settings
from there.
If you just want to get the content of variables from a foreign build
dir you can run
(Note: I wanted use this to provide different implementations of
AC_COMPILE_IFELSE for different languages. I think I can also do
without it, but I thought I'd write nevertheless about a more general
m4sugar problem).
The m4sugar.m4 file mentions the possibility to use:
1) that this requires a contract between the macros: if the definition
uses m4_provide([$0($@)]), the caller should use m4_require_with_args;
otherwise, it should use m4_require.
Perhaps we could redefine m4_require to always supply () (equivalent to 1
empty argument)
... And m4_defun to
Hi!
I just noticed, that when i enable a config.cache that is used by more
than one package is problematic, when the first on checks for the build
system type only, and the second for both build and host system type.
This is, because the host system type check uses ac_cv_build_alias,
which is set
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Eric Blake on 10/13/2008 5:55 AM:
AUTOTEST = $(AUTOM4TE) --language=autotest
-$(TESTSUITE): $(srcdir)/testsuite.at
+$(TESTSUITE): $(srcdir)/package.m4 $(srcdir)/testsuite.at
This looks like a correct dependency (at any rate, GNU
Hi,
My solution to this problem was to get the CC flags I wanted from the MySQL
MakeFile instead of trying to get them out of config.status.
It is still a bit frustrating when you know all the data you need is in
config.status but you cannot get it. Something that would solve this problem
would
* Barry Leslie wrote on Thu, Oct 16, 2008 at 04:45:05PM CEST:
My solution to this problem was to get the CC flags I wanted from the MySQL
MakeFile instead of trying to get them out of config.status.
It is still a bit frustrating when you know all the data you need is in
config.status but
Hi!
I just noticed, that when i enable a config.cache that is used by more
than one package is problematic, when the first on checks for the
build
system type only, and the second for both build and host system type.
This is, because the host system type check uses ac_cv_build_alias,
YES!!
That is what I wanted to hear!
THANK YOU!
Barry
On 10/16/08 7:50 AM, Ralf Wildenhues [EMAIL PROTECTED] wrote:
* Barry Leslie wrote on Thu, Oct 16, 2008 at 04:45:05PM CEST:
My solution to this problem was to get the CC flags I wanted from the MySQL
MakeFile instead of trying to
Hi all, this is *the* patch to add shell functions to Autoconf at last.
I am submitting it in one piece for testing, but I'm not really calling
for review; for that, I'll submit it split in 12 pieces. Also, the zsh
issue has to be understood better (and could be a deal breaker, though I
don't
Paolo Bonzini bonzini at gnu.org writes:
First thought, before I even begin a thorough review:
# AC_CHECK_FUNC(FUNCTION, [ACTION-IF-FOUND], [ACTION-IF-NOT-FOUND])
# -
AC_DEFUN([AC_CHECK_FUNC],
-[AS_VAR_PUSHDEF([ac_var],
What do you think?
Agreed on everything.
BTW, I think it's best for your sanity if you wait for the 12 separate
patches. :-) This is just a call for test; the basic idea won't change
even if the implementation details of the shell functions (and not of
the calls) change, so it is safe to do it
Hello Markus,
thanks for the reports.
* Duft Markus wrote on Thu, Oct 16, 2008 at 03:46:51PM CEST:
I just noticed, that when i enable a config.cache that is used by more
than one package is problematic, when the first on checks for the build
system type only, and the second for both
Ralf Wildenhues Ralf.Wildenhues at gmx.de writes:
It is still a bit frustrating when you know all the data you need is in
config.status but you cannot get it. Something that would solve this problem
would be to have an option like --showtag then I could run config,status
as:
You can do
On 2008-10-16, Ralf Wildenhues [EMAIL PROTECTED] wrote:
How do you get two concurrent configure scripts updating the same
config.cache file?
Open terminal (or screen) windows for two subdirectories of the combined
tree and in each modify a file which causes configure to be rerun (e.g.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Olly Betts on 10/16/2008 7:40 PM:
Hello Olly,
On 2008-10-16, Ralf Wildenhues [EMAIL PROTECTED] wrote:
How do you get two concurrent configure scripts updating the same
config.cache file?
Open terminal (or screen) windows for two
Sorry. This was hidden by the sh.test failure -- I did try testing
Libtool, but it didn't run the Autotest-based testsuite.
I didn't investigate it very much, but this fixes it and is conceptually
correct: we're expanding stuff in place in _AS_PREPARE, and we're taking
care of the ordering
22 matches
Mail list logo