Re: Test suite failures on static build (was: 5.0.2-test-2 is available)

[Axel Beckert <abe@xxxxxxxxxxxxxxx>]

Hi,

On Mon, Dec 02, 2013 at 08:43:29AM -0800, Bart Schaefer wrote:
> } On Mon, Dec 02, 2013 at 04:01:33PM +0000, Peter Stephenson wrote:
> } > On Mon, 02 Dec 2013 16:51:19 +0100
> } > Axel Beckert <abe@xxxxxxxxxxxxxxx> wrote:
> } > > JFTR: Probably not that important, but I get the following test-suite
> } > > failures when doing a static build:
> } > > Error output:
> } > > (eval):pushd:5: no such file or directory: /home/abe/zsh/zsh/obj-static/testhome
> } > 
> } > Could the exported value of HOME be funny?
> } 
> } I don't think so:
> 
> I can't come up with any other explanation for this, either.  There is
> nowhere in the normal zsh "make" process that would reference a
> "testhome" path.  *Something* is exporting that into the
> environment.

Ah, thanks for that hint. I was looking at the wrong place, sorry.

The build scripts for the Debian package indeed change $HOME for the
test-suite:

HOME="$(CURDIR)/obj-static/testhome" dh_auto_test -B obj-static --parallel || true

But they do it also for the dynamically linked build where everything
seems to go fine:

HOME="$(CURDIR)/obj/testhome" dh_auto_test -B obj --parallel

		Kind regards, Axel
-- 
/~\  Plain Text Ribbon Campaign                   | Axel Beckert
\ /  Say No to HTML in E-Mail and News            | abe@xxxxxxxxxxxxxxx  (Mail)
 X   See http://www.asciiribbon.org/              | abe@xxxxxxxxx (Mail+Jabber)
/ \  I love long mails: http://email.is-not-s.ms/ | http://noone.org/abe/ (Web)