* Ben Pfaff wrote on Thu, Aug 21, 2008 at 07:47:27AM CEST:
Eric Blake [EMAIL PROTECTED] comments:
That's true of any program that uses temporary files; it seems
like documentation is the right solution (since you obviously
can't hook SIGKILL to do cleanup). This could be as simple as
* Eric Blake wrote on Wed, Aug 20, 2008 at 09:46:15PM CEST:
Ralf Wildenhues Ralf.Wildenhues at gmx.de writes:
Yep. It's a timing problem: the `script' from the first test has the
same time stamp as the `script.as' from the second test, tricking
autom4te to think that its output is
Ralf Wildenhues wrote:
+On HP-UX, the default C compiler is not ANSI C compatible. If GNU CC is
s/GNU CC/GCC/? Wondering because GCC is used elsewhere in the document.
In my understanding, GCC designates the GNU compiler collection (= all of
gcc, g++, gcj, g77), whereas here I mean the GNU
* Bruno Haible wrote on Thu, Aug 21, 2008 at 11:26:41AM CEST:
Ralf Wildenhues wrote:
+On HP-UX, the default C compiler is not ANSI C compatible. If GNU CC is
s/GNU CC/GCC/? Wondering because GCC is used elsewhere in the document.
In my understanding, GCC designates the GNU compiler
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Ralf Wildenhues on 8/21/2008 12:05 AM:
- Log -
commit 96e601a1596f116c52e5d13529850f0d6c61f943
Author: Ralf Wildenhues [EMAIL PROTECTED]
Date: Wed Aug 20 21:10:17 2008
Ralf Wildenhues Ralf.Wildenhues at gmx.de writes:
The SHELL wording tweaking is fine with me, please apply.
Done. In testing it, I found another make SHELL bug, fixed in GNU make 3.81
but broken in many other implementations. I added this commit to the series:
From: Eric Blake [EMAIL
Ralf Wildenhues Ralf.Wildenhues at gmx.de writes:
The log says one thing,
but the ChangeLog another,
Sure enough I forgot to 'git add' again after the change, still lying
around in my git-ssh tree. Thanks for catching that!
Don't feel too bad. I did the exact same thing myself this
* Eric Blake wrote on Thu, Aug 21, 2008 at 06:58:39PM CEST:
Ralf Wildenhues Ralf.Wildenhues at gmx.de writes:
Is there such a thing as a pre-push hook?
This just came up on the git list[1].
Thanks.
One of the suggestions was adding this to your .git/config:
Yeah. If I have to remember
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Ralf Wildenhues on 8/21/2008 11:14 AM:
One of the suggestions was adding this to your .git/config:
Yeah. If I have to remember to use 'alias' for one repo but not
another, then I may just as well remember to check for clean tree
Hi Eric,
I'm looking through a bunch of the O(n) patches, and asking myself:
The fact that rescanning is avoided (by one means for m4-1.4.x and
another in m4-1.6.x), does that add a slight backward incompatibility
if the macro arguments contains side-effects? I'm thinking of stuff
like m4_syscmd
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Ralf Wildenhues on 8/21/2008 5:12 PM:
Hi Eric,
I'm looking through a bunch of the O(n) patches, and asking myself:
The fact that rescanning is avoided (by one means for m4-1.4.x and
another in m4-1.6.x), does that add a slight
Please consider the included patch. It fixes the warning and error messages'
capitalization and punctuation as per the GNU Coding Standards.
diff --git a/ChangeLog b/ChangeLog
index 7fdd897..20a2e01 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,10 @@
+2008-08-21 Peter Eisentraut [EMAIL
Eric Blake ebb9 at byu.net writes:
Hmm, I guess that means I should beef up the testsuite, as well as
patching these misfits to guarantee exactly one expansion of side effects.
Then the manual should indeed call this out as a design rule of thumb when
working with quoted lists - all side
Hello all,
As I couldn't find anything on this specific issue, better ask...
After being able to compile my code with help of autotools, now i want to
deliver it as a package. In this case I dont want to give out my configure.ac
and Makefile.ams in order to avoid some extra fiddling from others.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to [EMAIL PROTECTED] on 8/21/2008 5:34 AM:
Hello all,
As I couldn't find anything on this specific issue, better ask...
After being able to compile my code with help of autotools, now i want to
deliver it as a package. In this case I
On Thu, 21 Aug 2008, Eric Blake wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to [EMAIL PROTECTED] on 8/21/2008 5:34 AM:
Hello all,
As I couldn't find anything on this specific issue, better ask...
After being able to compile my code with help of autotools, now i want to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to [EMAIL PROTECTED] on 8/21/2008 6:51 AM:
If it's _his_ source code (and assuming that _he_ licensed it GPL), he can
distribute whatever set of files he chooses. The restriction applies for
files that he gets from someone else.
yes
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bob Friesenhahn wrote:
On Thu, 21 Aug 2008, Thomas Dickey wrote:
If it's _his_ source code (and assuming that _he_ licensed it GPL), he
can distribute whatever set of files he chooses. The restriction
applies for files that he gets from someone
On Thu, 2008-08-21 at 18:07 +0200, [EMAIL PROTECTED] wrote:
Well till i get things running, i dont want to get anyone fiddle around with
the build system, that's all. After that, i'd appreciate if anyone comes up
with a patch, change whatever it is. Help is always welcomed to give
and take.
Hello,
* Eric Blake wrote on Thu, Aug 07, 2008 at 03:20:53AM CEST:
According to Bruno Haible on 8/6/2008 4:41 PM:
| Could this be made customizable somehow? Either through a variable that the
| developer could set in his configure.ac before the invocation of AC_PROG_CC,
| or through a macro
Hi,
I found the following problem with autoconf version 2.62.
When taking the minimal example with a configure.ac:
AC_INIT(foo, 1.0)
AC_CONFIG_FILES([foo-$PACKAGE_VERSION:foo.in])
AC_OUTPUT
and a file foo.in containing e.g.:
@PACKAGE_VERSION@
When running configure it
21 matches
Mail list logo
