[PATCH] doc: clarify DJGPP shell 'return' bug spelling

2016-02-29 Thread Pavel Raiskup
* doc/autoconf.texi (Shell Functions): Fix spelling so the "command substitution" is related to function, not the 'return' statement. --- doc/autoconf.texi | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/autoconf.texi b/doc/autoconf.texi index 9ea67cc..cdf58bf 100644

Re: [PATCH] Autom4te: don't de-duplicate 'verb' and 'fatal' output

2016-02-29 Thread Pavel Raiskup
On Monday 19 of January 2015 16:42:54 Pavel Raiskup wrote: > This commit was proposed to not hide the second 'aclocal' run > during 'autoreconf -vfi'. Similar patch applied in GNU Automake > as commit fe3850. Ping. Pavel

Re: Shellology: ksh93 from OpenIndiana ${1+"$@"}

2016-01-10 Thread Pavel Raiskup
On Sunday 13 of December 2015 20:07:59 Paul Eggert wrote: > On 12/10/2015 05:55 AM, Pavel Raiskup wrote: > > Is this issue worth documenting in Shellology section > > withing autoconf.info? This probably should be fixed somehow in libtool, > > but I'm not yet sure w

Shellology: ksh93 from OpenIndiana ${1+"$@"}

2015-12-10 Thread Pavel Raiskup
Bob sent me a bug report that libtool's testsuite is currently broken on Open Indiana, this the underlying problem: $ cat test.sh #! /bin/sh f () { echo "arguments: $#" } f ${1+"$@"} $ ./test.sh a arguments: 1 $ ./test.sh a b arguments: 2 $ ./test.sh a b ""

Re: PATCH: remove config.{guess,sub} man pages

2015-12-09 Thread Pavel Raiskup
Hi Ben, On Wednesday 25 of November 2015 21:09:39 Ben Elliston wrote: > Remove config.{guess,sub} man pages. These are now kept in the master > source tree for config.{guess,sub}. after this patch -- the manual pages are not installed with autoconf anymore (I tried 'make install'). Is that

Re: bug#19539: [1.15] AC_CONFIG_AUX_DIR should be called early

2015-01-30 Thread Pavel Raiskup
[+cc autoconf as this should be done in cooperation] On Thursday 08 of January 2015 16:43:02 Pavel Raiskup wrote: Hi, automake-1.15 behaves differently when AC_CONFIG_AUX_DIR is specified after AC_USE_SYSTEM_EXTENSIONS (example attached which worked with automake-1.14.1): $ autoreconf -vfi

[PATCH] Autom4te: don't de-duplicate 'verb' and 'fatal' output

2015-01-19 Thread Pavel Raiskup
This commit was proposed to not hide the second 'aclocal' run during 'autoreconf -vfi'. Similar patch applied in GNU Automake as commit fe3850. * lib/Autom4te/ChannelDefs.pm: Set 'uniq_part' to UP_NONE for 'verb' and 'fatal' channel. --- lib/Autom4te/ChannelDefs.pm | 5 +++-- 1 file changed, 3

[PATCH] testsuite: fix race conditions in ltdl dryrun

2014-12-15 Thread Pavel Raiskup
/autoreconf.in#n356 Pavel racy-tests.tar.gz Description: application/compressed-tar From 2ad0598f0d8cd8c8532a2c34ea1b06c71901047d Mon Sep 17 00:00:00 2001 From: Pavel Raiskup prais...@redhat.com Date: Mon, 15 Dec 2014 13:42:25 +0100 Subject: [PATCH] tests: fix race in aclocal/autoheader calls Put

[PATCH] docs: gnuconfig manual page generating

2014-11-12 Thread Pavel Raiskup
Don't generate empty manual pages when config.sub/config.guess files are updated in distribution tarball and help2man is not installed; don't fail either. Resist on not 'touch'ing the old pre-generated manual page to not hide the problem, however. Also for git builds stay fatal and enforce

Re: [Bug-tar] testsuite.log too large for mailing lists

2014-01-09 Thread Pavel Raiskup
On Wednesday, January 08, 2014 23:52:47 Karl Berry wrote: Hi Sergey/all - when make check fails, it advises the user to email testsuite.log to bug-tar. That is nice in theory, but the log is big these days, and there are a lot of people on bug-tar, ie, we're talking a lot of bandwidth to

[PATCH] tests: ignore config.site in 'configure directories'

2013-11-19 Thread Pavel Raiskup
Original bugreport: https://bugzilla.redhat.com/994725 * tests/base.at (configure directories): Export CONFIG_SITE=NONE. --- tests/base.at | 1 + 1 file changed, 1 insertion(+) diff --git a/tests/base.at b/tests/base.at index 87a0417..84e35e5 100644 --- a/tests/base.at +++ b/tests/base.at @@

Re: [RFC] getting rid of the config.guess/sub problem when bootstrapping new ports/systems

2013-05-22 Thread Pavel Raiskup
It's what I've done for years. Does it get rid of the problem? I don't think so but for legacy code that is no longer being maintained, either you maintain it, or the problem exists into infinity with a hard stop when someone does maintain it. I think the battle is trying to overcome

Re: [RFC] getting rid of the config.guess/sub problem when bootstrapping new ports/systems

2013-05-21 Thread Pavel Raiskup
Works for me. But we [distros] do want to mandate autoreconf anyway in the general case: it is the *only* way to keep upstream honest about the much hated build system not bitrotting until it decides to blow up right when we need it for a security update. I know. But there is a lot of

Re: [RFC] getting rid of the config.guess/sub problem when bootstrapping new ports/systems

2013-05-20 Thread Pavel Raiskup
pros: we are able to easily patch also old packages (no-need to autoreconfigure) There would still be a long bootstrap period where old tarballs would not have any way of running a modern config.sub/guess other than copying them in from the system versions. I meant that you are able to

Re: [RFC] getting rid of the config.guess/sub problem when bootstrapping new ports/systems

2013-05-20 Thread Pavel Raiskup
Works for me. But we [distros] do want to mandate autoreconf anyway in the general case: it is the *only* way to keep upstream honest about the much hated build system not bitrotting until it decides to blow up right when we need it for a security update. I know. But there is a lot of

Re: [RFC] getting rid of the config.guess/sub problem when bootstrapping new ports/systems

2013-05-19 Thread Pavel Raiskup
+cc config-patc...@gnu.org, Ben Elliston b...@air.net.au IME, it is much better when any override mechanism make use of environment variables. Yes, it was mentioned multiple times in this thread already and it was always forgotten. Please consider this approach. One thing was not mentioned

Re: Bad pwd detection in generated 'configure'

2013-05-14 Thread Pavel Raiskup
Would there be possible to use something like this? It would pretty easily work-around the issue: # When building in place, set srcdir=. -if test $ac_abs_confdir = $ac_pwd; then +if test `$readlink -f $ac_abs_confdir` = `$readlink -f $ac_pwd`; then Sorry, but 'readlink' is not

Bad pwd detection in generated 'configure'

2013-05-13 Thread Pavel Raiskup
Hello, currently, configure scripts are badly detecting whether the build is done in place (pwd == $srcdir). One problem (spotted in RH bugzilla) is this: $ PWD=`pwd`/ ./configure In case of Bash, there we are hitting a bug (or feature? .. ksh also has this one..): $ cd /tmp $ PWD=`pwd`/

configure.in still mentioned in autoupdate manpage

2013-03-04 Thread Pavel Raiskup
Hi, there is small artifact in man/autoupdate.x: diff --git a/man/autoupdate.x b/man/autoupdate.x index 40d24e2..4182cd1 100644 --- a/man/autoupdate.x +++ b/man/autoupdate.x @@ -1,2 +1,2 @@ [name] -autoupdate \- Update a configure.in to a newer Autoconf +autoupdate \- Update a configure.ac to a

[PATCH] autotest: do not fail when make throws warnings

2013-02-13 Thread Pavel Raiskup
Related to commit d902536. On Fedora 17 having installed latest git autoconf and automake, testsuite failed on 'C unit tests'. The problem was that tested 'make' was unable to run jobserver and was throwing warning. As this is not the tested feature we can simply ignore warnings. *

[PATCH] autotest: do not fail when make throws warnings

2013-02-13 Thread Pavel Raiskup
Related to commit d902536. On Fedora 17 having installed latest git autoconf and automake, testsuite failed on 'C unit tests'. The problem was that tested 'make' was unable to run jobserver and was throwing warning. As this is not the tested feature we can simply ignore warnings. *