Hi Noah,
* Noah Misch wrote on Mon, Apr 10, 2006 at 11:18:16PM CEST:
There's little harm in having Makefile.in older than Makefile.am if
the updated Makefile.in would not change.
True if you are a developer and have the right Autoconf and Automake
versions installed; wrong if you are an
Hi Stepan,
* Stepan Kasal wrote on Mon, Apr 10, 2006 at 11:55:41PM CEST:
Reading the patch, two questions came to my mind:
1) It was said here that MSYS supports file hard links on NT filesystems.
So it is possible that under some circumstances, LN=ln will be selected
there. Is this
Hi Keith,
* Keith MARSHALL wrote on Tue, Apr 11, 2006 at 10:54:44AM CEST:
Ralf Wildenhues wrote, quoting Stepan Kasal:
1) It was said here that MSYS supports file hard links on NT
filesystems. So it is possible that under some circumstances,
LN=ln will be selected there. Is this
Hi Keith,
Thank you for your persistence!
* Keith MARSHALL wrote on Tue, Apr 11, 2006 at 01:18:47PM CEST:
To (hopefully) put this to bed, here's how MSYS handles various
possibilities on NTFS:
$ ln [dir1/]file dir2 ; # fails
Does this also fail if `dir2' is `.'? I'm a
Hi Eric,
* Eric Blake wrote on Fri, Apr 07, 2006 at 11:57:34PM CEST:
This resubmittal is tested with
./testsuite -d -k 'C keywords' CFLAGS='-std=c89 -Wall -Werror'
and fixes the C89 regression I made in the first version. I
understand if you decide to delay this patch until after the alpha
Hi Eric,
* Ralf Wildenhues wrote on Mon, Apr 10, 2006 at 01:34:01PM CEST:
* Eric Blake wrote on Sun, Apr 09, 2006 at 03:17:36PM CEST:
Erm, instead of the
:; $1
could we just have
m4_default([$1], [:])
please? This avoids the size overhead incurred for the
Hi Eric,
Replying to two of your messages:
* Eric Blake wrote on Sat, Apr 08, 2006 at 04:57:11PM CEST:
My earlier patch (AS_MKDIR_P instead of mkdir, because rm can fail)
is tested by the fact that I call ./run from within the directory (effectively
locking it on cygwin, as a good way to
Ralf Wildenhues [EMAIL PROTECTED] writes:
* lib/m4sugar/m4sh.m4 (_AS_LN_S_PREPARE): If `ln -s file1 file2'
succeeded, but `ln -s file dir' failed, take care to remove the
leftover target before the next test, to prevent its spurious
failure; also make sure `ln file
On Tue, Apr 11, 2006 at 09:25:53AM +0200, Ralf Wildenhues wrote:
* Noah Misch wrote on Mon, Apr 10, 2006 at 11:18:16PM CEST:
There's little harm in having Makefile.in older than Makefile.am if
the updated Makefile.in would not change.
True if you are a developer and have the right
Hello Ralf,
Ralf Wildenhues [EMAIL PROTECTED] writes:
* lib/m4sugar/m4sh.m4 (_AS_LN_S_PREPARE): If `ln -s file1 file2'
succeeded, but `ln -s file dir' failed, take care to remove the
leftover target before the next test, to prevent its spurious
failure; also make sure `ln
Hi Stepan,
* Stepan Kasal wrote on Tue, Apr 11, 2006 at 09:48:28PM CEST:
Attached please find an implmentation of this change, to be applied
against current CVS.
Go ahead.
Cheers,
Ralf
2006-04-11 Stepan Kasal [EMAIL PROTECTED]
* lib/m4sugar/m4sh.m4 (_AS_LN_S_PREPARE): Simplify
Hi Noah,
* Noah Misch wrote on Tue, Apr 11, 2006 at 09:04:03PM CEST:
If you need to advance the time stamp of `Makefile.in' in CVS and have no need
to change its contents, use this approach: change `Makefile.in' trivially (add
white space to a comment), commit, revert your change, commit
Hi Ralf,
I read your patch the way that this more than 2 exit statuses proposal
isn't immediately necessary any more, right?
Indeed, and so I won't propose anything on this front until after 2.60.
Yes, or similarly. I traced back why Akim did it back then the way it
was documented until
`automake' can generate a Makefile.in that does not fit `configure' if the
version of Autoconf it uses to trace `configure.ac' differs from the version
used to generate `configure'.
Suppose you'll unpack and configure a software distribution bootstrapped with
Autoconf 2.60 and Automake 1.9.6.
Hello,
On Tue, Apr 11, 2006 at 06:11:22PM +0200, Ralf Wildenhues wrote:
http://lists.gnu.org/archive/html/bug-autoconf/2006-03/msg00038.html
FYI, Noah and Stepan were kind enough to analyse this issue, and revert
the AC_CONFIG_COMMANDS (sorry for that typo above) behavior back to be
Ed Hartnett wrote:
In a similar situation, I first check to see if CFLAGS is set, then
only muck with it if it has not been set:
Yes, we do something similar in FFTW.
To those on this list who think that configure should never set CFLAGS,
realize that optimizing CFLAGS can be very important
Hi,
I have 2 projects, CGDB and libgdbmi. CGDB depends on libgdbmi. I would
like to make libgdbmi an autoconf package so that other people can
benefit from it.
Is there a nice way to have CGDB's package use libgdbmi's package as if
it were all 1 package? I would like to avoid having to run
Bob Rossi wrote:
Hi,
I have 2 projects, CGDB and libgdbmi. CGDB depends on libgdbmi. I would
like to make libgdbmi an autoconf package so that other people can
benefit from it.
Is there a nice way to have CGDB's package use libgdbmi's package as if
it were all 1 package? I would like to avoid
Hello again,
* Ralf Wildenhues wrote on Wed, Mar 29, 2006 at 11:30:43PM CEST:
We'd like to make you aware of an issue with the AC_CONFIG_FILES macro
that affects the AX_PREFIX_CONFIG_H macro as it is in the autoconf
archive:
19 matches
Mail list logo