* Stefano Lattarini wrote on Thu, May 06, 2010 at 12:47:02PM CEST:
Enable the shell `errexit' flag in `tests/dejagnu7.test', so that
previously unchecked failures now cause the whole test to fail.
Also, avoid unportable use of fgrep option `-e'.
From 9b487b1e65ca5d0e3361c484fe624a729c9245fc
* Stefano Lattarini wrote on Sun, May 23, 2010 at 02:08:20PM CEST:
At Sunday 23 May 2010, Ralf Wildenhues wrote:
Well, that's once again difference between the author date of the
patch and the commit date. The patches were committed on
2010-04-25, and GCS generally recommend using
Long ago:
http://lists.gnu.org/archive/html/automake-patches/2010-02/msg00017.html
* Ralf Wildenhues wrote on Sat, Feb 20, 2010 at 05:42:30PM CET:
* Stefano Lattarini wrote on Sat, Feb 20, 2010 at 04:49:37PM CET:
I've written a small patch adding some tests. Note that they are mostly
For maint.
Cheers,
Ralf
Fix unportable sed script in maintainer-check test.
* Makefile.am (sc_tests_Exit_not_exit): Rewrite sed script to
not contain semicolon after 'b' or brace commands, for NetBSD.
diff --git a/Makefile.am b/Makefile.am
index c487874..bbcc882 100644
---
Another spurious testsuite failure with NetBSD make.
Committed to master.
Cheers,
Ralf
Relax silent8.test for NetBSD make.
* tests/silent8.test: Accept ./foo.info in output as well.
diff --git a/tests/silent8.test b/tests/silent8.test
index 2546775..6833840 100755
---
* Stefano Lattarini wrote on Sun, Mar 07, 2010 at 05:15:24PM CET:
Generated tests are now just a thin layer around other tests.
* tests/Makefile.am: Rewrite the rule to generate the `*-p.test'
test scripts so that any of them simply includes the corresponding
`*.test' script (after setting
[ http://lists.gnu.org/archive/html/automake-patches/2010-04/msg00121.html ]
* Stefano Lattarini wrote on Fri, Apr 30, 2010 at 05:21:03PM CEST:
At Friday 30 April 2010, Eric Blake wrote:
On 04/30/2010 08:56 AM, Stefano Lattarini wrote:
Apparently, Automake configure script tells that
* Stefano Lattarini wrote on Sun, May 23, 2010 at 02:41:24PM CEST:
At Sunday 23 May 2010, Ralf Wildenhues wrote:
http://lists.gnu.org/archive/html/automake-patches/2010-02/msg00017.html
Unfortunately that turned out to be too optimistic. I'm pushing
this followup to maint. Tested
* Stefano Lattarini wrote on Sun, May 23, 2010 at 03:11:28PM CEST:
At Sunday 23 May 2010, Ralf Wildenhues ralf.wildenh...@gmx.de wrote:
By the way, adding an AC_PREREQ call in Automake's own
configure.ac would be nice IMHO; I didn't do that because I don't
know what is the minimal
* Eric Blake wrote on Mon, Apr 26, 2010 at 05:44:35PM CEST:
Thanks for the report. I'll push this patch shortly for
git-version-gen, but there are other culprits (MODULES.html.sh,
gnupload, m4/get{delim,line}.m4, m4/javacomp.m4, posix-modules) that are
still ascii-specific.
Thanks for the
* Stefano Lattarini wrote on Sun, May 23, 2010 at 03:01:20PM CEST:
At Sunday 23 May 2010, Ralf Wildenhues wrote:
Got lucky and intuition saved me from regressing branch-1.11 with
this one. I'm applying the fix below on top of this patch and
merging to master. The nontrivial point
Hi Eric,
* Eric Blake wrote on Sat, May 15, 2010 at 01:41:08AM CEST:
Right now, either you use foo_DEPENDENCIES and have to list everything
yourself, or you omit it, and automake does a good job. But what about
the case where you want automake to do its automatic dependencies, and
then you
Hi Bruno,
* Bruno Haible wrote on Sat, May 15, 2010 at 03:13:07PM CEST:
I'm trying to build a slightly modified libunistring-0.9.3
on OpenBSD 4.5. With GNU make, there is no problem. But with
/usr/bin/make, I get this error:
Thanks for the good bug report and analysis.
[...]
(1) all:
Hello David,
* David Bond wrote on Tue, Apr 27, 2010 at 07:54:02PM CEST:
I'm working on a project that we are converting to autotools and I
had a question. If this is the wrong place to ask these please
direct me to the right location.
This is the right place to ask, but we might be a little
Hi Stefano,
* Stefano Lattarini wrote on Sat, May 01, 2010 at 06:40:41PM CEST:
OK, I must admit to be stuck here. How can I know what objects files
are expected to be compiled from, say, a bar.c file, in turn generated
from a bar.l file?
Or (e.g.) how can I distinguish the following
Hello Trevor,
* Trevor Harmon wrote on Wed, Apr 28, 2010 at 09:18:37AM CEST:
My project lives in a source code repository (Subversion), and I'm
trying to keep all generated files out of it. This would be easier if
there were a built-in way of deleting anything and everything
generated by
Hello Matěj,
* NightStrike wrote on Wed, Apr 28, 2010 at 12:49:56AM CEST:
On Tue, Apr 27, 2010 at 4:20 PM, Matěj Týč wrote:
What I would like to have is some integration of autogen with autoconf
like YACC and LEX have.
Which means that I would like to specify the template and definitions
* Stefano Lattarini wrote on Mon, Apr 26, 2010 at 10:59:50AM CEST:
By the way, I didn't understand if you're going to amend the patches
yourself, or if I should do that instead...
I can do that, but it's likely going to not be before the weekend.
Cheers,
Ralf
Hello Stefano,
* Stefano Lattarini wrote on Mon, Apr 26, 2010 at 02:05:19PM CEST:
Extend tests on `nostdinc' automake option.
* tests/nostdinc.test: Make the grepping of the generated
Makefile.in slighty stricter. Enable `errexit' shell flag.
Related and unrelated minor changes.
Also,
* Stefano Lattarini wrote on Wed, Apr 21, 2010 at 02:30:46PM CEST:
At Wednesday 21 April 2010, Ralf Wildenhues wrote:
If you have a pointer to a similar
make implementation without the heirloom-specific quirks, I'd be
happy to use it instead.
Yes: Solaris make. I'm guessing
* Stefano Lattarini wrote on Thu, Apr 22, 2010 at 02:25:08PM CEST:
At Tuesday 20 April 2010, Ralf Wildenhues wrote:
Yeah, heirlooom make has a .l.o rule that triggers before our .l.c
and .c.o rule chains.
I guess this could be worked around by adding explicit rules (at
least that's
Hello Stefano,
* Stefano Lattarini wrote on Wed, Apr 21, 2010 at 01:59:51PM CEST:
In fact, I'm inclined to keep the patches enabling `set -e' separated
for three reasons:
1. To make the analysis of these patches simpler (as they are very
short); this should tendentially lead to more
Hi Stefano,
* Stefano Lattarini wrote on Fri, Apr 23, 2010 at 07:23:03PM CEST:
Myabe this is a stupid question, but I've not been not able to figure
out what's the role of the following trailing lines in `cscope.test':
$MAKE || Exit 77
This line was added in a1d5239b5e to cope with absent
Hi Stefano,
* Stefano Lattarini wrote on Thu, Apr 22, 2010 at 10:31:24PM CEST:
Subject: [PATCH 5/5] Improved test silent5.test.
* tests/silent5.test: Removed by hand all generated C files after
non-verbose builds, to ensure the following builds are clean.
A couple of greps of make's output
* Stefano Lattarini wrote on Thu, Apr 22, 2010 at 10:51:49PM CEST:
Subject: [PATCH] Minor improvements in comments of silent3.test.
* tests/silent3.test: Tell to keep it in sync with `silent9.test'
too.
Thanks!
* Stefano Lattarini wrote on Sun, Apr 25, 2010 at 04:28:43PM CEST:
At Sunday 25 April 2010, Ralf Wildenhues wrote:
--- a/tests/silent5.test
+++ b/tests/silent5.test
@@ -116,7 +119,7 @@ do
$MAKE stdout || { cat stdout; Exit 1; }
cat stdout
grep ' -c' stdout Exit 1
* Stefano Lattarini wrote on Sun, Apr 25, 2010 at 02:42:04PM CEST:
At Sunday 25 April 2010, Ralf Wildenhues wrote:
For what it's worth, since git this issue should be fairly moot.
You can keep branches for a long time, and merge them into your
devel-branch-du-jour for testing them. You can
a greeting from the language police. ;-)
Pushing to master.
Cheers,
Ralf
Fix placing of ellipses in English text and synopses.
* Makefile.am: Be sure to add a space before `...' in natural
language text.
* automake.in (scan_autoconf_traces): Likewise.
*
For maint.
Cheers,
Ralf
Fix typo in manual.
* doc/automake.texi (Simple Tests using parallel-tests): Add missing
closing parenthesis.
diff --git a/doc/automake.texi b/doc/automake.texi
index ae5e364..939ea00 100644
--- a/doc/automake.texi
+++ b/doc/automake.texi
@@ -8716,7
This fixes a theoretical bug introduced with incomplete renaming in a
2003-05-25 patch. I do not know how to trigger the failure path except
by actually introducing the bug in automake.in (tested by replacing the
'if' condition with one that evaluates to true).
For maint.
Cheers,
Ralf
Fix
for f in tests/*test
do
sed = $f |
sed -n 'N
s/\n/:/
/2 *stderr/{
N
N
s/[^\n]*\n//
s/\n/:/
/cat stderr/!p
}' |
sed s|^|$f:|
done
found another couple of missed verbose printing of captured output,
one
I missed a couple of duplicate message prefixes in the 2010-04-11
changes to master. Fixing thusly.
Cheers,
Ralf
Fix more duplicate message prefixes.
* lib/Automake/XFile.pm (seek): Do not prepend $me.
($me): Remove now-unused package-global.
* aclocal.in (check_acinclude):
Some more trivial cleanup for GNU Coding Standards requirements in
message formatting, and blunders like trailing newlines in messages.
I'm not actually sure what to do when messages consist of two sentences.
For now I kept the period at the end of the first and the capitalization
of the second.
* Stefano Lattarini wrote on Mon, Apr 26, 2010 at 12:15:33AM CEST:
--- a/tests/silent6.test
+++ b/tests/silent6.test
@@ -99,5 +99,3 @@ $AUTOMAKE
grep 'AM_V_GEN' Makefile.in
$AUTOMAKE --force -Wno-all -Wportability
grep 'AM_V_GEN' Makefile.in
-
-:
Please don't remove trailing ':' or
Hello Xochitl,
* Xochitl Lunde wrote on Thu, Apr 22, 2010 at 05:48:20PM CEST:
I have a problem with my dependency tracking in my auto tools build. I
have a program like this for an embedded target:
pald_LDADD = $(am_ldadd)
am_ldadd = \
-lstartup
There are more libraries in
* NightStrike wrote on Sat, Apr 24, 2010 at 02:08:43AM CEST:
On Mon, Apr 19, 2010 at 2:25 PM, John Calcote john.calc...@gmail.com wrote:
A problem I foresee is providing the globbing functionality to makefile
commands. We'd almost need a new auxiliary script (like install-sh) to
generate
Hi Stefano,
* Stefano Lattarini wrote on Tue, Apr 20, 2010 at 04:50:54PM CEST:
While trying out the Automake testsuite using Heirloom make as $MAKE.
I encounterd a failure in test `subobj9.test'. Attached here are the
test log and the testscript-generated Makefile and Makefile.in heirloom
* Stefano Lattarini wrote on Tue, Apr 20, 2010 at 10:52:41PM CEST:
At Tuesday 20 April 2010, Ralf Wildenhues wrote:
I'm trying to understand which of these lines this make interprets
wrongly:
include file
include ./file
include .//file
This one is sufficient o trigger the bug
* Stefano Lattarini wrote on Tue, Apr 20, 2010 at 04:31:05PM CEST:
I encounterd the following failure when trying out the Automake
testsuite using Heirloom make as $MAKE:
$ strings /opt/heirloom/bin/make | grep '@(#)'
@(#)make.sl 1.40 (gritter) 3/15/07
The failure is not spurious,
* Ralf Wildenhues wrote on Tue, Apr 20, 2010 at 11:25:41PM CEST:
I'm guessing this has to do with chains of inference rules not being
detected or so.
Yeah, the make has a .l.o rule that triggers before our .l.c and .c.o
rule chains.
I guess this could be worked around by adding explicit rules
* Stefano Lattarini wrote on Wed, Apr 21, 2010 at 12:41:21AM CEST:
At Tuesday 20 April 2010, Ralf Wildenhues wrote:
Yeah, the make has a .l.o rule that triggers before our .l.c and
.c.o rule chains.
Do you know if this happens also with Solaris make, or is just a quirk
specific
Hi Stefano,
* Stefano Lattarini wrote on Tue, Apr 20, 2010 at 12:14:51PM CEST:
At Tuesday 20 April 2010, Ralf Wildenhues wrote:
Thanks. This and newer patches of yours should all be applied now.
Please speak up if I've overlooked any again.
I guess that you're talking about overlooked
* Stefano Lattarini wrote on Tue, Apr 20, 2010 at 12:22:48PM CEST:
Mmhh... I thought that you had already applied this patch, but
perusing the git logs of latest master I saw that this is not the
case.
Thus I rebased the patches and amended them to follow your
suggestions. The new
* Russ Allbery wrote on Tue, Apr 20, 2010 at 09:23:41AM CEST:
Ole Tange writes:
Ralf Wildenhues wrote:
I wish automake could warn about leading whitespace damage;
unfortunately, the parser would need to be quite a bit smarter
for such a warning to work reliably.
Could it be extended
* Stefano Lattarini wrote on Sun, Apr 18, 2010 at 06:17:29PM CEST:
Recently, I stumbled upon a weird behaviour of automake: apparently,
even when given the `-Werror' flag, it doesn't fail on warnings of type
`unsupported' which concern the copresence of `configure.ac' and
`configure.in'.
* Stefano Lattarini wrote on Sun, Apr 18, 2010 at 06:17:29PM CEST:
Recently, I stumbled upon a weird behaviour of automake: apparently,
even when given the `-Werror' flag, it doesn't fail on warnings of type
`unsupported' which concern the copresence of `configure.ac' and
`configure.in'.
* Stefano Lattarini wrote on Sat, Apr 17, 2010 at 03:56:05PM CEST:
At Sunday 11 April 2010, Ralf Wildenhues wrote:
* Stefano Lattarini wrote on Fri, Apr 09, 2010 at 05:11:44PM CEST:
* tests/confh5.test: In the generated Makefile.am: do not use
`test ! -e FILE' to check for the non
Hello Ole, Russ,
* Russ Allbery wrote on Fri, Apr 16, 2010 at 10:27:11PM CEST:
Ole Tange writes:
$ cat src/Makefile.am
dist_bin_SCRIPTS = parallel
man_MANS = parallel.1
parallel.1: parallel
pod2man --release='$(PACKAGE_VERSION)' --center='$(PACKAGE_NAME)' \
then,
ppl.hh is listed in noinst_HEADERS but not in include_HEADERS.
The patch below fixes that.
You should be able to reproduce the issue with the configure option
cited in the mantis entry.
Cheers,
Ralf
2010-04-19 Ralf Wildenhues ralf.wildenh...@gmx.de
* src/Makefile.am (BUILT_SOURCES
Hello,
* NightStrike wrote on Mon, Apr 19, 2010 at 05:09:04PM CEST:
Is this possible? Is there anyone willing to do it?
Addendum: A big benefit for me (other than many other things) is that
it lets automake handle figuring out dependencies. In my example,
libx.a doesn't depend on
* Ralf Wildenhues wrote on Mon, Apr 19, 2010 at 06:55:30PM CEST:
* Russ Allbery wrote on Fri, Apr 16, 2010 at 10:27:11PM CEST:
Ole Tange writes:
$ cat src/Makefile.am
dist_bin_SCRIPTS = parallel
man_MANS = parallel.1
parallel.1: parallel
pod2man --release
* Russ Allbery wrote on Mon, Apr 19, 2010 at 08:39:48PM CEST:
Ralf Wildenhues ralf.wildenh...@gmx.de writes:
* Ralf Wildenhues wrote on Mon, Apr 19, 2010 at 06:55:30PM CEST:
* Russ Allbery wrote on Fri, Apr 16, 2010 at 10:27:11PM CEST:
parallel.1: parallel
pod2man --release
Hi John,
* John Calcote wrote on Mon, Apr 19, 2010 at 08:25:22PM CEST:
Since the current implementation of the JAVA primary is not managing
individual source/object dependencies (something that's difficult to
do anyway because of inner and anonymous class definitions), would
it not be prudent
* John Calcote wrote on Mon, Apr 19, 2010 at 09:52:51PM CEST:
I can certainly see how we may want to stick with the Automake
static source file specification rules for the reasons you point
out. In this case, it becomes more of an evangelistic documentation
issue. :) That is, we might be wise
* Steffen Dettmer wrote on Wed, Apr 14, 2010 at 11:53:56AM CEST:
On Wed, Apr 14, 2010 at 7:53 AM, Ralf Wildenhues ralf.wildenh...@gmx.de
wrote:
would it be a potential possibility instead to `overwrite and
specialize' some macro?
With some macro, you mean some prepended or appended
Hello Philip,
* Philip A. Prindeville wrote on Thu, Apr 15, 2010 at 05:35:37AM CEST:
I have the following trivial automake sequence in
21 SYMFILES = $(srcdir)/uni.h $(shell $(CC) $(CFLAGS) -E $(srcdir)/header.c
| $(AWK) -f $(srcdir)/script.awk)
but when I run automake on this, I get:
* Steffen Dettmer wrote on Tue, Apr 13, 2010 at 10:14:54PM CEST:
On Tue, Apr 13, 2010 at 7:53 PM, Ralf Wildenhues ralf.wildenh...@gmx.de
wrote:
* Xavier MARCELET wrote on Tue, Apr 13, 2010 at 09:38:36AM CEST:
For example, we could have a couple of macros
# AM_MAKEFILE_PREPEND([FRAGMENT
Hello Shizheng,
please don't top-post, thank you.
* isulsz wrote on Tue, Apr 13, 2010 at 05:02:09AM CEST:
I have another question regarding to the flag of the g++ compiler. I want to
debug the code carefully so I want to add -O0 option to the g++ so that it
will not optimize the code. Here is
* Xavier MARCELET wrote on Tue, Apr 13, 2010 at 09:38:36AM CEST:
Lets say that the file my_include.am declares a rule to generate
documentation :
$cat my_include.am
doc :
INPUT=. doxygen doxygen.cfg
Now, I wish to include this rule in every Makefile generated from
Makefile.in that are
Hello Xavier,
* Xavier MARCELET wrote on Mon, Apr 12, 2010 at 03:58:33PM CEST:
I have an include file (named 'my_include.am') that I want to append
in all the Makefile.in of my project
as if it was included in all my Makefile.am.
I don't want to edit all the makefile.am files (even through a
Hello,
* Jim Meyering wrote on Mon, Apr 12, 2010 at 11:44:01AM CEST:
Pavel Sanda wrote:
For my use, xz -9 is far too slow for anything except the
final make dist I run just prior to a release.
For a release, I run this, via one of the
alpha, beta or stable targets in gnulib's maint.mk:
* Andreas Jellinghaus wrote on Mon, Apr 12, 2010 at 09:41:44PM CEST:
Am Montag 12 April 2010 20:31:22 schrieb Ralf Wildenhues:
My idea would be to implement this for master, and revert the recent
xz -9 patch on branch-1.11. Comments, criticism?
if the environment variables can be used
Hello Pavel,
* Pavel Sanda wrote on Wed, Apr 07, 2010 at 01:22:06PM CEST:
the newly added dist-xz target produce worse compressed archives
than lzma-dist. The reason is that automake call lzma with
best compression while it won't use -9 level for xz.
Is this intention or bug?
Bug, I guess.
Hello Stefano,
* Stefano Lattarini wrote on Sun, Apr 04, 2010 at 08:57:19PM CEST:
At Sunday 04 April 2010, Ralf Wildenhues wrote:
* Stefano Lattarini wrote on Fri, Apr 02, 2010 at 12:29:49AM CEST:
By the way, how is the Automake-generated Makefile expected to
behave if a file in e.g
* Stefano Lattarini wrote on Fri, Apr 09, 2010 at 02:19:32AM CEST:
Avoid possible false negatives in cond46.test.
* tests/cond46.test: Enable shell `errexit' flag (and bumped
copyright years). Due to this change, the testcase should now
fail on unexpected failures in calls to
* Stefano Lattarini wrote on Fri, Apr 09, 2010 at 05:11:44PM CEST:
* tests/confh5.test: In the generated Makefile.am: do not use
`test ! -e FILE' to check for the non-existence of a file, since
that is not supported by Solarish/Heirloom Sh.
Applied to maint.
Thanks!
Ralf
Hello Stefano,
* Stefano Lattarini wrote on Fri, Apr 09, 2010 at 07:25:31PM CEST:
-$ACLOCAL || Exit 1
-$AUTOMAKE || Exit 1
+$ACLOCAL
+$AUTOMAKE
there is no need to actually remove these. They may not be strictly
required any more with 'set -e', but they may still serve as visual
reminder
Hello Andreas,
* Andreas Jellinghaus wrote on Sun, Apr 11, 2010 at 09:37:13PM CEST:
isn't xz extremely slw with -9?
maybe it wasn't a bug, bit intentionally not used,
as that huge extra amount of time doesn't result in
that many bytes saved.
Well, does somebody have numbers (memory,
Hello Bruno, all,
I'm sure it was you who requested this feature, but I can't find the
reference to this issue now. Anyway, here's a small patch series to
let automake and aclocal consistenly prefix warning and error messages,
applied to git master.
I wasn't completely sure about the case of
|6 +++---
6 files changed, 22 insertions(+), 12 deletions(-)
diff --git a/ChangeLog b/ChangeLog
index 9a0b332..6ed3c6f 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,13 @@
2010-04-11 Ralf Wildenhues ralf.wildenh...@gmx.de
+ Fix capitalization of error messages, reword one message
: Adjust expected
error messages.
* tests/comment5.test: Likewise. Also, include stack notes
should not start with `error:'.
* tests/location.test: Likewise. Also, try both -Werror and
-Wno-error.
* NEWS: Update.
Report by Bruno Haible.
Signed-off-by: Ralf Wildenhues ralf.wildenh...@gmx.de
variable to avoid false positive.
Signed-off-by: Ralf Wildenhues ralf.wildenh...@gmx.de
---
I didn't want to let the sc_tests_logs_duplicate_prefixes rule depend
upon 'check' because that would make 'maintainer-check' very expensive.
Introducing a toplevel GNUmakefile, we could safely use 'make
.
* tests/location.test: Adjust expected output with -Werror.
* tests/werror4.test: New test.
* tests/Makefile.am: Update.
* NEWS: Update.
Signed-off-by: Ralf Wildenhues ralf.wildenh...@gmx.de
---
ChangeLog| 11 +++
NEWS |2 +-
lib/Automake/Channels.pm
* Stefano Lattarini wrote on Sun, Apr 11, 2010 at 10:30:19PM CEST:
At Sunday 11 April 2010, Ralf Wildenhues wrote:
Being verbose is fine for things that are unobvious, but you may
assume that developers know autoconf.info.
Quite right. However, as you said when discussing my proposed patch
Hello Pavel,
* Pavel Sanda wrote on Wed, Apr 07, 2010 at 01:22:06PM CEST:
the newly added dist-xz target produce worse compressed archives
than lzma-dist. The reason is that automake call lzma with
best compression while it won't use -9 level for xz.
Is this intention or bug?
Bug, I guess.
Hello Andreas,
* Andreas Jellinghaus wrote on Sun, Apr 11, 2010 at 09:37:13PM CEST:
isn't xz extremely slw with -9?
maybe it wasn't a bug, bit intentionally not used,
as that huge extra amount of time doesn't result in
that many bytes saved.
Well, does somebody have numbers (memory,
Hello William,
* William Pursell wrote on Mon, Apr 12, 2010 at 04:34:48AM CEST:
Stefano Lattarini wrote:
Strictly speaking, AC_PROG_INSTALL is redundant here, being already
AC_REQUIRE'd by AM_INIT_AUTOMAKE (this should hold from Automake 1.4
at least, I think).
Yes, I thought the
Hello,
* isulsz wrote on Mon, Apr 12, 2010 at 04:38:08AM CEST:
But I have a new problem. When I try to make the project, I get this
error:
*** No rule to make target `../../src/Random/librng.a', needed by
`MultiSour'. Stop.
You probably need to reorder your SUBDIRS entry in the Makefile.am
Hello,
* NightStrike wrote on Sat, Apr 10, 2010 at 12:32:37AM CEST:
http://mingw-w64.svn.sourceforge.net/viewvc/mingw-w64/trunk/mingw-w64-crt/Makefile.am?revision=2163view=markup
Down at lines 937 to 941, there are two sets of rules, one for 3
specific files and one for the rest of the libs
Hello Jarek,
* jarek wrote on Wed, Apr 07, 2010 at 08:55:44AM CEST:
I have a c/c++ project with some number of intermediate files generated
from ASN.1 sources.
At the moment I'm building intermediate .cpp/.h sources like this:
regen: regenerate-from-asn1-source
* Stefano Lattarini wrote on Sun, Apr 04, 2010 at 09:17:53PM CEST:
At Sunday 04 April 2010, Ralf Wildenhues wrote:
Another ChangeLog style remark: please don't list all files if you
really adjust all files. In that case it is sufficient to say 'All
tests adjusted.' or so, and only list
* Stefano Lattarini wrote on Wed, Mar 31, 2010 at 02:11:16PM CEST:
Generated tests are now just a thin layer around other tests.
* tests/Makefile.am: Rewrite the rule to generate the `*-p.test'
test scripts so that any of them simply includes the corresponding
`*.test' script (after
Hello Ed,
* Ed Hartnett wrote on Fri, Apr 02, 2010 at 07:15:34PM CEST:
We don't want all this to happen when the user builds netcdf, so I have
a line in the Makefile.am:
# These files will be included with the dist.
EXTRA_DIST = netcdf.m4 $(pdf_docs) $(html_mans) $(txt_docs) $(dvi_docs)
* Jef Driesen wrote on Fri, Apr 02, 2010 at 11:45:20AM CEST:
On 01/04/10 20:31, Ralf Wildenhues wrote:
* Jef Driesen wrote on Thu, Apr 01, 2010 at 02:34:29PM CEST:
Since the .git-version file is a generated file, I would think it
belongs in the build directory, where all other generated files
* Jef Driesen wrote on Thu, Apr 01, 2010 at 02:34:29PM CEST:
On 31/03/10 22:45, Ralf Wildenhues wrote:
* Jef Driesen wrote on Wed, Mar 31, 2010 at 02:49:48PM CEST:
Shouldn't the .git-version file be created inside the build directory,
rather than the source directory?
No. I want the .git
* Stefano Lattarini wrote on Tue, Mar 30, 2010 at 09:50:52PM CEST:
At Tuesday 30 March 2010, Ralf Wildenhues wrote:
I'm not sure I understand. We are not putting any symlinks into
$(distdir), why would this be needed?
First, mostly for consistency with other cleanup rules (those in
`tests
* Jef Driesen wrote on Wed, Mar 31, 2010 at 02:49:48PM CEST:
On 30/03/10 20:57, Ralf Wildenhues wrote:
There is a point to using FORCE over .PHONY: were you to mark
$(srcdir)/.git-version as phony, then the compilation of version.c would
always be emitted by 'make', even if the .git-version
Hello Stefano,
* Stefano Lattarini wrote on Tue, Mar 30, 2010 at 05:50:28PM CEST:
However, I noticed that a lot of failures crop up with `make path-check',
either with or without my patches installed (these failures are listed
below). So I have a question: is the `path-check' target still
Hi Stefano,
thanks for the patch.
* Stefano Lattarini wrote on Tue, Mar 30, 2010 at 05:52:21PM CEST:
* Makefile.am (path-check): To be safe, do not use `chmod -R' on
$(distdir) before removing it (as Solaris `chmod -R' touches
symlink targets). Instead, use the cleanup strategy used in
Hi Lance,
thanks for the feedback.
* Lance Westerhoff wrote on Mon, Mar 29, 2010 at 08:52:58PM CEST:
That's the approach I ended up taking (hacking something of my own). A
couple of items did come up though:
(1) We support multiple compilers (icc and gcc), so having a mechanism
that
* Karl Berry wrote on Fri, Mar 19, 2010 at 10:42:14PM CET:
Is the intention that even the n...@acronym{gnu} cases should be
replaced? Then what purpose is the @acronym keyword for?
I wrote about that earlier. Minor typographic change which is rarely
used in GNU manuals. De facto
Hello Lance,
* Lance Westerhoff wrote on Wed, Mar 24, 2010 at 05:39:13PM CET:
I searched the automake list archives (along with anywhere else I
could find), and it appears that nothing has really happened with
standardizing precompiled headers support in the tool chain as there
hasn't been
A late hello,
* Robert J. Hansen wrote on Tue, Mar 23, 2010 at 12:12:46AM CET:
On 3/22/10 6:50 PM, John Calcote wrote:
Reuben, you've just hit upon one of the two most significant problems
with Javadoc and the like (including doxygen, man pages, and info pages):
Agreed -- which is why I
Hello Brian,
* Brian J. Murrell wrote on Thu, Mar 25, 2010 at 06:30:59PM CET:
We are seeing the following in trying to build our package(s) with some
versions of autoconf/automake:
libcfs/libcfs/autoMakefile.am:88: variable `DIST_SOURCES' is defined but no
program or
Hello Reuben,
* Reuben Thomas wrote on Mon, Mar 22, 2010 at 04:44:17PM CET:
2010/3/22 Russell Shaw:
Steffen Dettmer wrote:
* On Sun, Mar 21, 2010 at 10:27 AM, Ralf Wildenhues wrote:
BTW, execution of built programs like this makes your package unsuitable
for cross-compilation. Just so
Hello William,
* William Drozd wrote on Mon, Mar 22, 2010 at 03:48:58PM CET:
I have configured/make/make install on autoconf with no problems.
I have run automake's configure with no problems.
However, when I run make while trying to install automake I get the error:
-bash-3.1$ make
Hello Russell,
* Russell Shaw wrote on Sun, Mar 21, 2010 at 07:06:00AM CET:
I want the unimain program built first, then use it to generate
unidata.tab.c, which is then compiled and linked into librunicode.la
bin_PROGRAMS = unimain
unimain_SOURCES = unimain.c
unidata.tab.c:
* Russell Shaw wrote on Sun, Mar 21, 2010 at 09:26:44AM CET:
Ralf Wildenhues wrote:
* Russell Shaw wrote on Sun, Mar 21, 2010 at 07:06:00AM CET:
bin_PROGRAMS = unimain
unimain_SOURCES = unimain.c
unidata.tab.c: unimain$(EXEEXT) /usr/share/unicode/UnicodeData.txt
./unimain
* Russell Shaw wrote on Sun, Mar 21, 2010 at 08:16:03AM CET:
Ralf Wildenhues wrote:
Furthermore, please don't hard-code absolute paths like
/usr/share/unicode/UnicodeData.txt
in your makefiles. Make them configurable by configure. Maybe your
users don't have root rights on their system
* Russell Shaw wrote on Sun, Mar 21, 2010 at 11:18:03AM CET:
Ralf Wildenhues wrote:
Use noinst_PROGRAMS instead of bin_PROGRAMS. Be encouraged to read the
fine manual.
But it is somewhat big, and i had already searched through the online
one a lot first. It is no wonder it takes noobs so
901 - 1000 of 3140 matches
Mail list logo