Hello, Alexandre!
Thank you for quick reply!
On Fri, 2006-02-03 at 08:01 +0100, Alexandre Duret-Lutz wrote:
> >>> "PR" == Pavel Roskin <[EMAIL PROTECTED]> writes:
> PR> - How portable is $(<:.h=.ui) in the suffix rules?
>
> I think this should work.
d too, but Makefile was
very large because it had rules for every file.
--
Regards,
Pavel Roskin
rces.redhat.com/automake/";
. "automake.html#Extending%20aclocal\n"
By the way, wouldn't the "warn" function in Perl more appropriate? It's
used elsewhere in aclocal.in. It doesn't add "WARNING" though.
I also hope 1.8 will be released soon. I cannot wait for m4_include
support. Many thanks to the Automake team.
--
Regards,
Pavel Roskin
ake a fork, add a well-behaving shell to the
requirements and leave out everything else. I know a project with
configure script longer than 500k. Uncompressed sources of ash with
function support are smaller than that.
--
Regards,
Pavel Roskin
AUTHORS. There is no 1.7 branch there, so presumably the head branch will
become the 1.7 release.
If version 1.6.4 will be released, it will be released from the branch
called "branch-1-6".
--
Regards,
Pavel Roskin
Done. The new section in HACKING is called "Working with CVS". Please
have a look if you want to add something to this topic.
--
Regards,
Pavel Roskin
rictness of "make
distcheck".
At some point, "make distcheck" would simply call "make dist" and run the
standalone "distcheck" script with predefined DISTCHECK_FLAGS.
--
Regards,
Pavel Roskin
Hello!
warnopts.test fails randomly for me. I have just applied this patch
that fixes the problem:
* tests/warnopts.test: Fix random failures by removing Autoconf
cache directory when configure.in changes. Use the code and the
comment from tests/asm.test.
Hello, Alexandre!
> Pavel> Well, my package doesn't. Here's the test (full test
> Pavel> with copyright is attached):
>
> Thanks a lot! I'm installing the following fix.
The fix works. GNU Midnight Commander works with CVS Automake now. Thank
you!
--
Regards,
Pavel Roskin
was a preliminary version. This one actually works on
a clean CVS checkout.
--
Regards,
Pavel Roskin
bootstrap.gz
Description: GNU Zip compressed data
ed to autogen.sh or cvscompile or
whatever.
--
Regards,
Pavel Roskin
bootstrap.gz
Description: GNU Zip compressed data
ake/tests/testSubDir
Makefile.am:2: `foo_PROGRAMS' is used but `foodir' is undefined.
Makefile.am:6: unused variable: `foo_SOURCES'
FAIL: cond25.test
Automake 1.6.3 passes this test. I'm using Autoconf 2.54, bash 2.05a,
perl 5.6.1.
--
Regards,
Pavel Roskin
cond25.test.gz
Description: GNU Zip compressed data
pped if this option
is used.
For example, reiserfsprogs installs binaries to /sbin, and they has a good
reason for that. Using DESTDIR is the only way that reiserfsprogs passes
`make distcheck'. It's still better than `make dist' for making real
releases.
--
Regards,
Pavel Roskin
loop is for subdirectories - a failure
in the first of them would cause all other subdirectories to be skipped,
and only local commands outside the loop would be executed.
You can consider this as a low-priority feature request for Automake.
Perhaps it can be done by examining $(MAKE) for GNU make.
--
Regards,
Pavel Roskin
#x27;s already implemented in Mailman, it's just turned off. However, it
would be wrong to reject such messages withot review, and that takes time.
--
Regards,
Pavel Roskin
them by "cvs commit".
--
Regards,
Pavel Roskin
.test
+++ tests/yacc8.test
@@ -58,7 +58,7 @@
END
$AUTOMAKE -a
-test -f ./ylwrap
+test -f ./ylwrap || exit 1
cd sub
make foo/parse2.o
===
--
Regards,
Pavel Roskin
there are runaway
processes (CPU hogs) on the anoncvs.cygnus.com. Old versions of CVS can
create such processes on "cvs log -r," or something like that (I don't
want to check it).
Since the CVS server doesn't reply to "cvs version", I assume it's old.
--
Regards,
Pavel Roskin
lkmail:
X-Mailer:.*(Collector|Multi|Gammadyne|Mass|MMailer|AMLC|em5000|V3,|AOL|JCourier|Spam|Mach|Easy|GOTO|Arclab|Caretop)
X-EM-Version:
X-Courtesy-Of:
X-MSMail-Priority: High
--
Regards,
Pavel Roskin
INIT
AM_INIT_AUTOMAKE(nonesuch, nonesuch)
-AS='$(CC)'
-AC_SUBST(AS)
+CCAS='$(CC)'
+AC_SUBST(CCAS)
AC_PROG_CC
AC_OUTPUT(Makefile)
END
@@ -55,10 +55,10 @@
cat > configure.in << 'END'
AC_INIT
AM_INIT_AUTOMAKE(nonesuch, nonesuch)
-AS='$(CC)'
-AC_SUBST(AS)
+CCAS='$(CC)'
+AC_SUBST(CCAS)
AC_PROG_CC
-AC_SUBST(ASFLAGS)
+AC_SUBST(CCASFLAGS)
AC_OUTPUT(Makefile)
END
=
--
Regards,
Pavel Roskin
ccstdc.m4 cond.m4 depend.m4 depout.m4 \
dmalloc.m4 gcj.m4 header.m4 init.m4 install-sh.m4 lex.m4 lispdir.m4 \
=
Changelog:
* m4/Makefile.am (m4datadir): Use APIVERSION.
--
Regards,
Pavel Roskin
in the new form only.
> + Suggested by Pavel Roskin.
Thank you! It works for me.
I didn't know that there is a new form of AM_INIT_AUTOMAKE. However, to
use it in GNU Midnight Commander I'll need to be able to redefine
PACKAGE_TARNAME because I don't want any spaces in it
than Automake macro AM_INIT_AUTOMAKE. I would expect
Automake to respect its own macros more that the ones from Autoconf.
Maybe the GNU Coding Standards have changed so that spaces are not allowed
in the project names? But how about non-GNU projects using Autoconf and
Automake?
--
Regards,
Pavel Roskin
: Hahaha <[EMAIL PROTECTED]>
X-AD2000-Serial:
X-Bulkmail:
X-Mailer: Email Collector
X-EM-Version:
X-Courtesy-Of:
X-MSMail-Priority: High
Should be sufficient if require_explicit_destination is set.
--
Regards,
Pavel Roskin
we would reserve the true failures for the problems nobody is
aware of, so that they can be spotted and reported immediately.
--
Regards,
Pavel Roskin
e Autoconf-2.51 is another
question.
I personally don't want to risk, but if you think that you can make
Automake work with the "big macro" (maybe by releasing another
Automake-1.4-pX) without spending months on it then I'll support merging
the macros now.
--
Regards,
Pavel Roskin
cpp, so it's a good idea to test for the compiler
anyways.
> * In rare occasions, only a functional cpp is required, but a broken
> cc is tolerable (eg. to process *.S -> *.o)
If a broken cc is tolerable then you should have a mechanism to instruct
configure not to abort. This is quite orthogonal to the preprocessor test.
--
Regards,
Pavel Roskin
ay be necessary.
If you feel that you can handle it feel free to merge. It should be done
earlier or later anyways.
--
Regards,
Pavel Roskin
should
take less (or more?) hackerish approach.
Since Autoconf-2.50 has been released, it would be fair to drop support
for Autoconf-2.13 and use new facilities for attaching dependency code to
AC_PROG_CC (provided that they exist and I understand the problem
correctly).
--
Regards,
Pavel Roskin
d be
installed just in case or AM_DEPENDENCIES should be more quiet if it
cannot find depcomp.
Anyway, this test demonstrates error messages from "configure" - this
certainly shouldn't happen.
--
Regards,
Pavel Roskin
__
#! /bin/sh
# Test to
ot immediately as it used to be. It's PR/174.
--
Regards,
Pavel Roskin
logged in under my name "proski" but I don't have
edit access to Automake database.
> Ok, thanks.
> Could you see if the manual needs to be updated for this?
Yes. The submitted patch updates the documentation.
--
Regards,
Pavel Roskin
_
ar in
AM_CONDITIONAL
FAIL: gcj.test
===
1 of 1 tests failed
===
make[1]: *** [check-TESTS] Error 1
make[1]: Leaving directory `/usr/local/src/automake/tests'
make: *** [check-am] Error 2
--
Regards,
Pavel Roskin
ing constants.
-my $IGNORE_PATTERN = '^##([^#\n].*)?\n';
+my $IGNORE_PATTERN = '^\s*##([^#\n].*)?\n';
my $WHITE_PATTERN = '^\s*$';
my $COMMENT_PATTERN = '^#';
my $TARGET_PATTERN='[$a-zA-Z_.][-.a-zA-Z0-9_(){}/$]*';
_
Regards,
Pavel Roskin
HEAD branch) Automake and should be
fixed there.
> * Directories listed in EXTRA_DIST are now correctly included
> in the generated distribution tarball.
This is the reason why I would like to have "AUTOMAKE_OPTIONS = 1.4-p1" in
some projects.
--
Regards,
Pavel Roskin
ile $value")
+&define_variable ("LT$var", "\$(LIBTOOL) --mode=compile $value")
if $seen_libtool;
}
_
Regards,
Pavel Roskin
ey are fixed it will be possible to use "--Werror" in the testuite.
Or we can just add those tests to XFAIL_TESTS and enable "--Werror" now.
--
Regards,
Pavel Roskin
ry and then removing the old files using "cvs remove". This way,
the historic versions will have extra files in the subdirs but "make" will
not descent into them and neither will "make dist".
--
Regards,
Pavel Roskin
e top-level directory?
Try recent Autoconf or Libtool:
$ automake
$ ./configure --quiet
...
$ make dvi
make: Nothing to be done for `dvi'.
--
Regards,
Pavel Roskin
her.
- elsif (/^\@syncodeindex (\w+) \w+/)
+ elsif (/^\@syn(code)?index (\w+) \w+/)
{
- push @syncodeindexes, "$1s";
+ push @syncodeindexes, "$2s";
}
}
___
By the way, I discovered a terrible bug in CVS Automake while testing it -
"make dvi" doesn't propagate to the subdirectories.
--
Regards,
Pavel Roskin
Hello, Jim!
I was the first to send the patch but your description is better.
> 2001-04-30 Jim Meyering <[EMAIL PROTECTED]>
>
> * automake.in: Remove `/lib' from include directory.
Applied.
--
Regards,
Pavel Roskin
7;perllibdir'} || "@datadir@/@PACKAGE@";
unshift @INC, "$perllibdir";
}
_
Regards,
Pavel Roskin
e to look into this later. I'll be
grateful is somebody with better knowledge of texinfo checks my patch in
the meantime.
--
Regards,
Pavel Roskin
an another.
___
--
Regards,
Pavel Roskin
fatal signal 11
Unrelated question - why does the prototype use `$%' instead of `%'? We
are only using hashes as arguments. Actually, prototype checking seems to
be rather weak, but it's better than nothing.
--
Regards,
Pavel Roskin
these complaints from Perl.
-# So just forget about it now.
-XFAIL_TESTS = installsh.test man.test objc.test subobj2.test yaccvpath.test
+XFAIL_TESTS = man.test objc.test subobj2.test yaccvpath.test
TESTS =\
acinclude.test \
______
--
Regards,
Pavel Roskin
ake: *** [check-am] Error 2
The failure happens during the "automake" invocation. Makefile.in is
created and contains the following string twice:
@AMDEP@CXXDEPMODE = @CXXDEPMODE@
Regards,
Pavel Roskin
dd-missing; echo $?
automake: Makefile.am: required file `./NEWS' not found
2
Sorry, no patch.
Regards,
Pavel Roskin
Hello!
> ChangeLog:
> * Makefile.am (maintainer-check): Scan all *.am files and tests
> for invocations of `rm' without `-f'.
> * tests/mclean.test: Adjusted to prevent being caught by the
> above test.
I've checked it in.
Regards,
Pavel Roskin
installdirs)'; then \
--- tests/mclean.test
+++ tests/mclean.test
@@ -13,4 +13,4 @@
$AUTOMAKE || exit 1
-grep 'rm .*MAINTAINERCLEANFILES' Makefile.in
+grep 'rm -f .*MAINTAINERCLEANFILES' Makefile.in
Regards,
Pavel Roskin
.PHONY clean-am: clean-%DIR%JAVA:
clean-%DIR%JAVA:
- -rm *.class class%DIR%.stamp
+ -rm -f *.class class%DIR%.stamp
Regards,
Pavel Roskin
On 6 Mar 2001, Akim Demaille wrote:
> Pavel Roskin <[EMAIL PROTECTED]> writes:
>
> > .PHONY uninstall-am: uninstall-%DIR%SCRIPTS
>
> I fixed this typo (missing ?INSTALL?).
Thanks! I've removed noinstdir.test from XFAIL_TESTS.
Regards,
Pavel Roskin
st='$(%DIR%_SCRIPTS)'; for p in $$list; do \
- f="`echo $$p|sed '$(transform)'`"; \
- echo " rm -f $(DESTDIR)$(%NDIR%dir)/$$f"; \
- rm -f $(DESTDIR)$(%NDIR%dir)/$$f; \
- done
+?INSTALL?uninstall-%DIR%SCRIPTS:
+?INSTALL? @$(NORMAL_UNINSTALL)
+?INSTALL? @list='$(%DIR%_SCRIPTS)'; for p in $$list; do \
+?INSTALL?f="`echo $$p|sed '$(transform)'`"; \
+?INSTALL?echo " rm -f $(DESTDIR)$(%NDIR%dir)/$$f"; \
+?INSTALL?rm -f $(DESTDIR)$(%NDIR%dir)/$$f; \
+?INSTALL? done
## Uncomment line in handle_scripts when this is uncommented.
## check-%DIR%SCRIPTS:
__
Regards,
Pavel Roskin
Hello!
`make distcheck' is working again. No more questions from `rm'.
Regards,
Pavel Roskin
__
Index: ChangeLog
===
RCS file: /cvs/automake/automake/ChangeLog,v
retrieving revis
Hello!
CVS Automake attempts to install noinst_SCRIPTS. The following test fails:
___
#! /bin/sh
# Test to make sure that noinst_SCRIPTS are not installed.
# From Pavel Roskin.
. $srcdir/defs || exit 1
cat > Makefile.am << 'END'
noinst_SCRIPTS =
it's what you want to happen.
Regards,
Pavel Roskin
___
Index: ChangeLog
===
RCS file: /cvs/automake/automake/ChangeLog,v
retrieving revision 1.1143
retrieving revision 1.1144
diff -u -r1.1143 -r1
*** [check-TESTS] Error 1
make[1]: Entering directory `/home/proski/src/automake.v0/tests'
make[1]: Leaving directory `/home/proski/src/automake.v0/tests'
Regards,
Pavel Roskin
found should be declared by "use vars", but I
would prefer if the author does it. In fact, it may be a legitimate case
for a variable to be declared local.
Regards,
Pavel Roskin
; Yes. `make distclean' must leave the build directory as it was before
> configure. When `make distcheck' is failing in this test it is
> because distclean is not properly doing its job -- in a fresh build
> directory `configure ; make ; make distclean' must leave the directory
> empty.
I know what `make distclean' is supposed to do. Not creating distributable
files in the build directory would releave us from cleaning them there.
Regards,
Pavel Roskin
also please make some "unit testing" of your tests. For example,
YACC=bison had no chances to work even when configuring in the source
tree, since bison outputs files with different names.
Regards,
Pavel Roskin
____
--- ChangeLog
+++ ChangeLog
@@ -1,3 +1,12 @@
en "touch parse.y" can be moved below "configure", since the
later is guaranteed to take at least 1 second (see AM_SANITY_CHECK).
Regards,
Pavel Roskin
es
or no?
3) Out-of-date generated distributable files should be recreated in the
build directory. Always, never, only when no write permissions for srcdir?
4) "make distclean" should attempt to clean generated distributable files
that appear in the build directory. Yes or no?
Regards,
Pavel Roskin
"
export YACC
# Remove some files installed by defs.
@@ -61,6 +58,7 @@
bison -y parse.y
mv y.tab.c parse.c
+sleep 3
cat >> parse.y << 'END'
fubar : 'f' foobar {};
END
Regards,
Pavel Roskin
t look so to me:
> if install-sh is in current directory, why would Automake prefer
> and use ../../install-sh?
It's a complicated mix of several bugs and ancient traditions. I believe,
the best fix will be to have tests/defs to copy the right install-sh
instead of creating an empty file.
Regards,
Pavel Roskin
Hello, Tom and Alexandre!
On 27 Feb 2001, Tom Tromey wrote:
> >>>>> "Pavel" == Pavel Roskin <[EMAIL PROTECTED]> writes:
>
> Pavel> I don't quite understand whether your test is supposed to work
> Pavel> or not. It's failing for me (be
tall-dataDATA \
install-incldataHEADERS install-localstateDATA \
install-pkgdataDATA install-pkgdataSCRIPTS install-sbinSCRIPTS \
install-sysconfDATA
I'm using RedHat 7.0 with Perl 5.6.0.
Regards,
Pavel Roskin
test), unless I'm missing something.
Also please make sure that the test is ignored when bison and yacc are
not available.
Regards,
Pavel Roskin
> Nonetheless, given that we can never be sure to what extend the test
> suite exercise Automake, I would include it anyway: better have
> automake dying than make. Just imagine
>
> ?SOME-CONDITION-RARELY-TRUE? %SOME-PARAM-WE-FORGOT%.
Ok
Regards,
Pavel Roskin
PFX%DEPMODE@
>
> where ? means, automake-time Boolean, %, automake-time variable, @,
> configure-time variable.
Excellent!
Regards,
Pavel Roskin
harder since we share @ with AC_SUBST. I would really love to
> use %FOO% instead in Automake. Tom, what do you think? This would
> make it possible for automake to check what it outputs.
Are you suggesting AM_SUBST?
Regards,
Pavel Roskin
Hello!
The top-level Makefile.am on CVS Automake doesn't know anything about
install.am.
_
--- ChangeLog
+++ ChangeLog
@@ -1,3 +1,7 @@
+2001-02-26 Pavel Roskin <[EMAIL PROTECTED]>
+
+ * Makefile.am: Add install.am.
+
2001-02-26 Akim Demaille <[E
should not appear in Makefile.in. Something must be wrong in your
patches.
Regards,
Pavel Roskin
t providing a rule for it (foo).
It's not what Automake does.
The real usefulness on .PHONE if that "all" will be remade even if a file
named "all" exists for some reason in the current directory (or in VPATH).
Regards,
Pavel Roskin
D] for consistency with Autoconf. By
the way, it's not binaries, it's Perl code. Sometimes they look
confusingly similar :-)
Regards,
Pavel Roskin
e sure that they
don't change.
You have my full support if you do so.
Regards,
Pavel Roskin
-/foo
-./bar
-)
+
+cd obj
+../configure
+$MAKE
+./foo
+./bar
+cd ..
+
./configure
$MAKE
./foo
_
Regards,
Pavel Roskin
ild_triplet = @build@
+?HOST?host_alias = @host_alias@
+?HOST?host_triplet = @host@
+?TARGET?target_alias = @target_alias@
+?TARGET?target_triplet = @target@
______
Regards,
Pavel Roskin
7;';
> + foreach $val ( @curval )
> + {
> + $ret .= $val . " ";
> + }
How about this:
join(" ", @curval)
Everything else is fine. I'm sorry that I'm keeping bouncing your work,
but the Automake code should be of the highest quality.
Regards,
Pavel Roskin
ability to add missing files.
But this should be fixed in Autoconf, not in Automake.
Maybe tracing will help. We probably need a special macro, e.g.
AC_REQUIRE_FILE, so that the macros will be able to indicate what files
they need. The only question is whether it should be processed by
Autoconf, Automake or both.
Regards,
Pavel Roskin
yntax. However, I believe that the existing testsuite should catch
possible problems.
Some people are offended by this condition because it's _implied_. But now
we have to think how to fix the testsuite that already fails.
Regards,
Pavel Roskin
+ local @curval = &variable_value_as_list ($var, $cond);
Maybe I'm missing something, but I don't see any error protection here.
You are working with user input. What if the expression is invalid?
> +$AUTOMAKE || exit 1
> +
> +grep '^@TEST_TRUE@' Makefile.in || exit 1
> +exit 0
As I said before, this is not a test for pattern expansion.
Regards,
Pavel Roskin
Hello, Tom!
> Pavel> In the Automake CVS the target "all" is not longer PHONY. Is it
> Pavel> a bug or an intentional change? If the later, what was the
> Pavel> reason?
>
> Bug.
Thanks for the fix!
However, "all-am" is still not PHONY.
Regards,
Pavel Roskin
Hello!
In the Automake CVS the target "all" is not longer PHONY. Is it a bug or
an intentional change? If the later, what was the reason?
If the former, I'll try to find who's "guilty".
Regards,
Pavel Roskin
Hello, John!
On Tue, 13 Feb 2001, John Poltorak wrote:
> It contains old versions of config.guess and config.sub.
I was going to write exactly that!
I believe we need something like the "wget-update" target in Automake.
Maybe it should even be dist-hook.
Regards,
Pavel Roskin
ould be safe to remove "dnl".
Regards,
Pavel Roskin
Hello, Tom!
> I added another test to pr87.test to check for this failure.
I have fixed it so that it fails "correctly", not because foo/Makefile.in
is tested before being created :-)
Regards,
Pavel Roskin
--- ChangeLog
+++ ChangeLog
@@ -1,3 +1,
objections.
In fact, by having two ChangeLogs GNU Automake "endorses" its users to use
this style. This should be fixed.
Regards,
Pavel Roskin
if Automake doesn't control that
directory then it shouldn't care.
I don't like rules that rebuild something in a directory other than "."
and (in limited situations) $srcdir.
Maybe my understanding is too primitive, I don't know.
Regards,
Pavel Roskin
(handle_configure): Set dist_dirs entries at toplevel.
In fact it says directly: "Don't push @inputs onto the dist list."
Not good. Many programs rely on that.
Regards,
Pavel Roskin
he new test fails exactly how it should. I'm going to apply it unless you
come with something better.
Regards,
Pavel Roskin
Index: tests/ChangeLog
--- tests/ChangeLog
+++ tests/ChangeLog
@@ -1 +1,6 @@
+2001-02-07 Pavel Roskin <[EMAIL PROTECTED]
cat > foo/Makefile.am <<'END'
noinst_SCRIPTS = bar
END
touch foo/bar.in
$ACLOCAL || exit 1
$AUTOCONF || exit 1
$AUTOMAKE -a || exit 1
CC=gcc ./configure || exit 1
$MAKE || exit 1
$MAKE distcheck || exit 1
______
It fails even earlier when it creates an empty archive on "make dist".
This seems to be another bug.
Regards,
Pavel Roskin
ny changes against your will. If you don't change
you mind I don't want to push this idea. "ifdef" works for me.
Regards,
Pavel Roskin
ough it would catch just few errors, strict typing in large projects
(which Automake already is) is usually worth it.
Regards,
Pavel Roskin
m_include. I believe that user code should not do anything
with the names beginning with ac_ and am_.
Public names don't have any specific prefix: cross_compiling, SHELL,
program_suffix, x_libraries, M4, MISSING etc. It's too late to introduce
one.
Regards,
Pavel Roskin
libs).
I mean something like
AC_VERSION_CASE(
[<=2.13], [test "$FOO" = yes && tmp=foo; AC_CONFIG_SUBDIRS([$tmp])],
[default], [test "$FOO" = yes && AC_CONFIG_SUBDIRS([foo])])
We may do our best, but we cannot guarantee 100% backward compatibility.
Regards,
Pavel Roskin
aming AM_INCLUDE to AMINCLUDE everywhere? The patch is
attached. It fixes all tests.
Regards,
Pavel Roskin
___
--- ChangeLog
+++ ChangeLog
@@ -1,3 +1,10 @@
+2001-02-05 Pavel Roskin <[EMAIL PROTECTED]>
+
+ * automake.in (handle_dependencies): Rename AM
patch has been applied:
_
--- ChangeLog
+++ ChangeLog
@@ -1,3 +1,8 @@
+2001-02-04 Pavel Roskin <[EMAIL PROTECTED]>
+
+ * automake.in (handle_dist_worker): Remove a line that is now
+ in distdir.am.
+
2001-02-04 Kevin Ryde <[EMAIL PROTECTED]
l have to be dropped. Alternatively, AC_CANONICAL_TARGET should
implement it if the values set by (the former) AC_ARG_PROGRAM are pristine
(i.e. the transform rule is trivial).
Regards,
Pavel Roskin
Autoconf is handling the issue is not nice. People run the
testsuite on Tru64 v5.1 to find a problem with "the Cat in the Hat" that
can be reproduced on every system.
Regards,
Pavel Roskin
he default behavior, but since the output of
autoreconf is intended mostly for humans, it shouldn't be an issue.
Regards,
Pavel Roskin
1 - 100 of 144 matches
Mail list logo
