Bruno Haible wrote:
Jim Meyering wrote:
It comes from tests/Makefile:
TESTS_ENVIRONMENT = \
tmp__=$$TMPDIR; test -d $$tmp__ || tmp__=.; \
TMPDIR=$$tmp__; export TMPDIR;\
export\
VERSION='$(VERSION)'
Bruno Haible wrote:
Eric Blake wrote:
The grep test framework is borrowing
from gnulib's tests/init.sh, which should already be re-exec'ing under a
shell that supports $().
Ah, right. Here's a simpler patch then.
2011-11-11 Bruno Haible br...@clisp.org
Fix high-bit-range test
Jim Meyering wrote:
Bruno Haible wrote:
Jim Meyering wrote:
It comes from tests/Makefile:
TESTS_ENVIRONMENT = \
tmp__=$$TMPDIR; test -d $$tmp__ || tmp__=.; \
TMPDIR=$$tmp__; export TMPDIR;\
export\
Jim Meyering wrote:
+it is probably because you are using non-GNU-make with an old /bin/sh. If
so,
sed 's/with an old/or an old/
The workaround is to use GNU make *and* a different SHELL.
Bruno
--
In memoriam Nicholas Owen http://en.wikipedia.org/wiki/Nicholas_Owen_(martyr)
Hi Bruno.
On Saturday 12 November 2011, Bruno Haible wrote:
Jim Meyering wrote:
+it is probably because you are using non-GNU-make with an old /bin/sh. If
so,
sed 's/with an old/or an old/
The workaround is to use GNU make *and* a different SHELL.
My understanding is that, in your
Bruno Haible wrote:
Jim Meyering wrote:
2011-11-11 Bruno Haible br...@clisp.org
Fix test suite execution failure on OSF/1 5.1.
* tests/Makefile.am (TESTS_ENVIRONMENT): Use only the portable form
of
the 'export' shell built-in.
Thanks, but I'd like to find a way
Stefano Lattarini wrote:
This might cause annoying slow-downs on systems where forks are more
expensive (i.e., MinGW and Cygwin). What about doing something like
this instead, so that the extra forks are avoided when the shell is
Bash (as is the usual case under MinGW and Cygwin, if I'm not
Stefano Lattarini wrote:
On Saturday 12 November 2011, Jim Meyering wrote:
Thanks for the suggestion.
I was leaning towards accepting it, but then checked...
When /bin/sh is a link to bash, that envvar is not set here (F16):
Because it's not an environment variable, but only a shell
[adding autoconf]
On 11/11/2011 01:38 PM, Bruno Haible wrote:
The syntax export VAR=VALUE is not guaranteed by this shell.
Either write env VAR=VALUE ..., or VAR=VALUE; export VAR; ...
Strangely enough, this portability problem of the 'export' built-in
is well-known, but not mentioned in
Bruno Haible wrote:
On OSF/1 5.1:
make succeeds, but make check fails:
$ make check
No suffix list.
Making check in po
Making check in lib
make check-recursive
Making check in doc
Making check in src
Making check in tests
make get-mb-cur-max
`get-mb-cur-max' is up to date.
make
Hi Eric.
On Friday 11 November 2011, Eric Blake wrote:
[adding autoconf]
On 11/11/2011 01:38 PM, Bruno Haible wrote:
The syntax export VAR=VALUE is not guaranteed by this shell.
Either write env VAR=VALUE ..., or VAR=VALUE; export VAR; ...
Strangely enough, this portability
Jim Meyering wrote:
It comes from tests/Makefile:
TESTS_ENVIRONMENT = \
tmp__=$$TMPDIR; test -d $$tmp__ || tmp__=.; \
TMPDIR=$$tmp__; export TMPDIR;\
export\
VERSION='$(VERSION)' \
...
Past these two hurdles, all grep
tests pass and 2 gnulib tests fail (test-exclude2.sh, test-exclude5.sh).
Heh. That was with bash as shell. But without fiddling with the SHELL
variable, I get this failure:
FAIL: high-bit-range
The reason is that this shell's printf built-in does not interpret
On 11/11/2011 03:26 PM, Bruno Haible wrote:
$ bash -c printf '\\x81' | od -t x1
The next revision of POSIX (code-named Issue 8; POSIX 2008 is Issue 7)
will require support for $'\xXX', but you are correct that POSIX does
not require 'printf \xXX'. So we should definitely fix this one.
While
Eric Blake wrote:
The grep test framework is borrowing
from gnulib's tests/init.sh, which should already be re-exec'ing under a
shell that supports $().
Ah, right. Here's a simpler patch then.
2011-11-11 Bruno Haible br...@clisp.org
Fix high-bit-range test failure on OSF/1 5.1.
15 matches
Mail list logo
