Somehow I got this autoconf warning:
configure.ac:127: warning: AC_REQUIRE: `AM_ICONV' was expanded before it was
required
AM_ICONV is AC_REQUIREd in many places, but documented as an invokable macro in
the gettext documentation. Therefore it makes sense to use AC_DEFUN_ONCE. I'm
applying this
In a case where I want to use the absolute-header macro, it does not
work because it uses the CPPFLAGS from the beginning of the configure
run. But some macros augment CPPFLAGS.
In order to make the macro more usable, I'm extracting its core into
a separate macro.
Can someone explain why the argu
James Youngman wrote:
> --- a/users.txt
> +++ b/users.txt
> @@ -1,5 +1,6 @@
> The following packages appear to be using gnulib and gnulib-tool:
>
> + CSSChttp://git.savannah.gnu.org/cgit/cssc.git
>Net::CDPhttp://search.cpan.org/src/MCHAPMAN/Net-CDP-0.09/libcdp/
>OPeN
Bruno Haible wrote:
>> Now I've tried harder, and this does the job:
>
> Thanks a lot for getting to this so quickly! I can now single-step through
> the test in the documented way.
>
> One line in the patch looks strange: In the test whether the current shell
> is OK you test for an exit code 9; t
Hi Jim,
> > 2) The use of "$0". It is meant to denote the test-sh filename. This
> > CANNOT
> >work when single-stepping, because the statements are not contained in a
> > file
> >but are executed interactively, one by one.
>
> I don't see how this can cause a problem.
>
> The only
Hi Jim,
> Now I've tried harder, and this does the job:
Thanks a lot for getting to this so quickly! I can now single-step through
the test in the documented way.
One line in the patch looks strange: In the test whether the current shell
is OK you test for an exit code 9; then in the loop you te
---
users.txt |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/users.txt b/users.txt
index 9f76a5f..e3c8f83 100644
--- a/users.txt
+++ b/users.txt
@@ -1,5 +1,6 @@
The following packages appear to be using gnulib and gnulib-tool:
+ CSSChttp://git.savannah.gnu
Bruno Haible wrote:
> Two things are wrong here:
...
> 2) The use of "$0". It is meant to denote the test-sh filename. This
> CANNOT
>work when single-stepping, because the statements are not contained in a
> file
>but are executed interactively, one by one.
I don't see how this can
Bruno Haible wrote:
> On a glibc system, I cannot single-step unit tests that are built upon
> tests/init.sh any more. This is blocking.
...
> Two things are wrong here:
> 1) If I'm already using bash, it MUST NOT do an 'exec', because that kills the
>ability to do single-stepping.
Thanks for
Ben Pfaff wrote:
> This fixes the build in the case where both libintl and PSPP's
> Gnulib define __printf__. But it broke the build in the
> previously working case where libintl did not define __printf__
> but PSPP's Gnulib did and no longer does. This is the case on,
> for example, FreeBSD 7.3
Hi,
A week ago, Jim wrote:
> + init.sh: enable MALLOC_PERTURB_
> + * tests/init.sh: Enable glibc's malloc-perturbing option.
This triggers a SKIP for test-verify.sh on openSUSE Linux 11.0 systems:
test-verify.sh: skipped test: cannot compile error-free
SKIP: test-verify.sh
The reaso
Hi Jim,
On a glibc system, I cannot single-step unit tests that are built upon
tests/init.sh any more. This is blocking.
I got this skipped test on a glibc system:
test-verify.sh: skipped test: cannot compile error-free
SKIP: test-verify.sh
and cannot investigate it!
Here's my attempt at doi
12 matches
Mail list logo
