Hello automakers.
In the git master branch:
$ grep '\source\' lib/depcomp
source Source file read by `PROGRAMS ARGS'.
if test -z $depmode || test -z $source || test -z $object; then
echo depcomp: Variables source, object and depmode must be set 12
# the object too, otherwise
Hello Pippijn.
On Saturday 13 November 2010, Pippijn van wrote:
On Mon, Nov 01, 2010 at 08:18:44PM +0100, Ralf Wildenhues wrote:
Ideally, I would like to see testsuite coverage for each code path
(branch coverage) for new code. I understand that only Stefano is
able to produce this in
Another testsuite patch, based off of maint, but to be merged
in master only.
I will wait the customary 72 hours before pushing.
Regards,
Stefano
-*-*-*-
Extend and improve tests on DejaGnu support.
* tests/dejagnu.test: Do not create useless dummy test script.
Add trailing `:' command.
* Stefano Lattarini wrote on Sun, Nov 14, 2010 at 01:36:16PM CET:
But it's not like I have a silver bullet to write proper tests
which attain complete branch coverage; I just proceed by common
sense, trying to maximize such coverage. That's all, sadly.
A while ago I posted instructions on how
On Sunday 14 November 2010, Ralf Wildenhues wrote:
* Stefano Lattarini wrote on Sun, Nov 14, 2010 at 01:36:16PM CET:
But it's not like I have a silver bullet to write proper tests
which attain complete branch coverage; I just proceed by common
sense, trying to maximize such coverage.
Hi Paolo,
* Paolo Bonzini wrote on Tue, Nov 09, 2010 at 08:14:39PM CET:
This patch simplifies the overly complicated rules for ACLOCAL_PATH
vs. @automake_includes and @system_includes, by stating that
ACLOCAL_PATH will override even @automake_includes. The simplest
way to achieve this is to
Apparently, dash 0.5.5.1 has some problems with avoiding expansion in
case patterns when unusual characters are involved. I'm committing the
following patch to maint to let these tests PASS instead of SKIP with
this shell.
Thanks,
Ralf
tests: work around dash quoting issue in case
* Ralf Wildenhues wrote on Mon, Nov 01, 2010 at 10:25:02PM CET:
Fix install-strip when $(STRIP) contains several words.
* lib/am/install.am (install-strip): Update comment. Use
separate sub-make invocations for empty and nonempty $(STRIP),
to fix quoting issues.
*
On 11/14/2010 05:46 PM, Ralf Wildenhues wrote:
Hi Paolo,
* Paolo Bonzini wrote on Tue, Nov 09, 2010 at 08:14:39PM CET:
This patch simplifies the overly complicated rules for ACLOCAL_PATH
vs. @automake_includes and @system_includes, by stating that
ACLOCAL_PATH will override even
I'm committing this to maint, and merging to branch-1.11 and master.
Thanks,
Ralf
Rebuild menus in the manual.
* doc/automake.texi: Rebuild menus (using ^C ^U ^A in emacs).
Thanks to Ian Lance Taylor for the suggestion.
diff --git a/doc/automake.texi b/doc/automake.texi
index
Hi Stefano,
* Stefano Lattarini wrote on Mon, Sep 13, 2010 at 10:59:22AM CEST:
But since we are at it, we can do better, extending coverage and
making existing tests more semantic. See the attached patch (for
maint).
ansi2knr is a really dying (and ugly) feature; when have we last seen
a
* Stefano Lattarini wrote on Thu, Nov 11, 2010 at 03:52:39PM CET:
Pinging this patch again, following this:
http://lists.gnu.org/archive/html/automake-patches/2010-11/msg3.html
Patch is OK. I didn't check whether any of the tests contained
constructs problematic for set -e.
I'll wait
Hello Stefano,
I think it is time to reevaluate some of the work that has been done in
the last few weeks. I'd like to ask you to postpone pushes of pending
stuff that has a clock ticking, and look at the lots of new failures
that a testsuite run shows on a few hosts; you can find them in some
On Sunday 14 November 2010, Ralf Wildenhues wrote:
Hello Stefano,
I think it is time to reevaluate some of the work that has been done in
the last few weeks. I'd like to ask you to postpone pushes of pending
stuff that has a clock ticking, and look at the lots of new failures
that a
On Sunday 14 November 2010, Ralf Wildenhues wrote:
Hello Stefano,
I think it is time to reevaluate some of the work that has been done in
the last few weeks. I'd like to ask you to postpone pushes of pending
stuff that has a clock ticking, and look at the lots of new failures
that a
[Reposting with a better subject. Sorry for the noise.]
On Sunday 14 November 2010, Ralf Wildenhues wrote:
Hello Stefano,
I think it is time to reevaluate some of the work that has been done in
the last few weeks. I'd like to ask you to postpone pushes of pending
stuff that has a clock
Please disregard; answer to the message
Testsuite failures on Solaris 2.10 on SPARC
instead.
Sorry for the noise,
Stefano
On Sunday 14 November 2010, Ralf Wildenhues wrote:
Hello Stefano,
I think it is time to reevaluate some of the work that has been done in
the last few weeks.
Do you mean go and fix the newly introduced regressions before doing
other testsuite work, or reconsider the advisability of doing
On Sunday 14 November 2010, Ralf Wildenhues wrote:
Hello Stefano,
I think it is time to reevaluate some of the work that has been done in
the last few weeks. I'd like to ask you to postpone pushes of pending
stuff that has a clock ticking, and look at the lots of new failures
that a
On Sunday 14 November 2010, Ralf Wildenhues wrote:
Hello Stefano,
I think it is time to reevaluate some of the work that has been done in
the last few weeks. I'd like to ask you to postpone pushes of pending
stuff that has a clock ticking, and look at the lots of new failures
that a
On Monday 15 November 2010, Peter Rosin wrote:
Running MSVC on osfX.Y is not interesting. I'd write a patch to skip
the test
Yeah, I agree this is the best option.
but I can't then test the result.
Me neither (I don't have access to a True64/OSF system).
So I won't...
Neither will I ;-)
On Sunday 14 November 2010, Ralf Wildenhues wrote:
Hello Stefano,
I think it is time to reevaluate some of the work that has been done in
the last few weeks. I'd like to ask you to postpone pushes of pending
stuff that has a clock ticking, and look at the lots of new failures
that a
I'm seeing this failure in test yaccdry.test at the Hydra continuous
build system for automake:
http://hydra.nixos.org/build/745050/log
FAIL: yaccdry.test (exit: 2)
On Sunday 14 November 2010, Ralf Wildenhues wrote:
Hi Stefano,
* Stefano Lattarini wrote on Mon, Sep 13, 2010 at 10:59:22AM CEST:
But since we are at it, we can do better, extending coverage and
making existing tests more semantic. See the attached patch (for
maint).
ansi2knr is a
* Stefano Lattarini wrote on Mon, Nov 15, 2010 at 12:19:00AM CET:
On Sunday 14 November 2010, Ralf Wildenhues wrote:
I think it is time to reevaluate some of the work that has been done in
the last few weeks.
Do you mean go and fix the newly introduced regressions before doing
other
Hello Pippijn.
On Saturday 13 November 2010, Pippijn van wrote:
On Mon, Nov 01, 2010 at 08:18:44PM +0100, Ralf Wildenhues wrote:
Ideally, I would like to see testsuite coverage for each code path
(branch coverage) for new code. I understand that only Stefano is
able to produce this in
* Stefano Lattarini wrote on Sun, Nov 14, 2010 at 01:36:16PM CET:
But it's not like I have a silver bullet to write proper tests
which attain complete branch coverage; I just proceed by common
sense, trying to maximize such coverage. That's all, sadly.
A while ago I posted instructions on how
Hello Russell,
* Russell Shaw wrote on Sun, Nov 14, 2010 at 02:49:07AM CET:
In a Makefile.in generated by automake 1.9.6, it defines
top_builddir ok, but builddir is used but not defined in there.
This causes problems, because the automake manual says:
— Variable: builddir
Rigorously
On Sunday 14 November 2010, Ralf Wildenhues wrote:
* Stefano Lattarini wrote on Sun, Nov 14, 2010 at 01:36:16PM CET:
But it's not like I have a silver bullet to write proper tests
which attain complete branch coverage; I just proceed by common
sense, trying to maximize such coverage.
On 15/11/10 01:10, Ralf Wildenhues wrote:
Hello Russell,
* Russell Shaw wrote on Sun, Nov 14, 2010 at 02:49:07AM CET:
In a Makefile.in generated by automake 1.9.6, it defines
top_builddir ok, but builddir is used but not defined in there.
This causes problems, because the automake manual
Hello Ryan,
* Ryan Lortie wrote on Sat, Nov 13, 2010 at 05:49:57PM CET:
I recently filed a bug against a freedesktop.org component because it
didn't honour the ACLOCAL_FLAGS environment variable. That bug got
closed, telling me to use ACLOCAL like so:
ACLOCAL='aclocal -I
Hello,
في ح، 07-11-2010 عند 09:12 +0300 ، كتب Andrey Borzenkov:
Automake assumes the .c files generated by vala are distributed with the
source, and this isn't true when building from git. A solution is to do
an in-tree build, make distclean, and re-run your out-of-tree
32 matches
Mail list logo
