Front page | perl.perl5.porters |
Postings from August 2009
Re: 5.10.1-RC1 is released
From:
Dave Mitchell
Date:
August 11, 2009 15:12
Subject:
Re: 5.10.1-RC1 is released
Message ID:
20090811221151.GY4204@iabyn.com
On Mon, Aug 10, 2009 at 11:38:23AM +0200, H.Merijn Brand wrote:
> On Mon, 10 Aug 2009 09:54:50 +0100, Dave Mitchell <davem@iabyn.com>
> wrote:
>
> > On Sun, Aug 09, 2009 at 09:28:59AM +0200, H.Merijn Brand wrote:
> > > On Sun, 9 Aug 2009 01:13:41 -0400, "Chas. Owens" <chas.owens@gmail.com>
> > > wrote:
> > >
> > > > On Sat, Aug 8, 2009 at 03:49, Vincent Pit<perl@profvince.com> wrote:
> > > > > I've checked it on x86/linux with the Intel CC and saw no issues besides
> > > > > the Test::Deep one.
> > > > >
> > > > > Vincent
> > > >
> > > > The only problem I had on OS X 10.5.7 so far was related to
> > > > [PERL_UNICODE being set to SDL][1]. Should Configure check for
> > > > environment variables that are known to cause problems for the build?
> > >
> > > I don't think so, unless, like $OBJECT_MODE on AIX, it *ONLY* affects
> > > the compiler or linker. $PERL_UNICODE also affects RUNTIME, so
> > > Configure should NOT check. Just my € 0.01
> >
> > (I note this problem was present in 5.10.0).
> > Perhaps we need a note in INSTALL?
>
> I'd prefer that to be done by someone with higher English skills, as it
> is prone to wrong interpretation.
>
> --8<---
> Configure does not check for environment variables that have (major)
> influence on how perl is built or tested. e.g. $OBJECT_MODE on AIX
> determines the way the compiler and linker deal with their objects,
> but this is a variable that only influences build-time behaviour, and
> should not affect the perl scripts that are eventually executed by the
> perl binary. Other variables, like $PERL_UNICODE, $PERL5LIB, and
> $PERL5OPTS will influence the behaviour of the test suite.
> -->8---
Okay, I've added the following for now, in the 'head2 What if it doesn't
work?' section. I'd be happy if anyone wants to improve upon it.
(Oh and I forgot to credit you in the commit: -( )
commit 06aa495b2e26cd6963648651410909a6682df5b9
Author: David Mitchell <davem@iabyn.com>
AuthorDate: Tue Aug 11 23:09:01 2009 +0100
Commit: David Mitchell <davem@iabyn.com>
CommitDate: Tue Aug 11 23:09:01 2009 +0100
INSTALL: mention that env vars can affect tests
Affected files ...
M INSTALL
Differences ...
diff --git a/INSTALL b/INSTALL
index 89707cf..308ffff 100644
--- a/INSTALL
+++ b/INSTALL
@@ -1401,6 +1401,18 @@ The latter is especially useful if you see something like this
at Perl startup.
+=item other environment variables
+
+Configure does not check for environment variables that can sometimes
+have a major influence on how perl is built or tested. For example,
+OBJECT_MODE on AIX determines the way the compiler and linker deal with
+their objects, but this is a variable that only influences build-time
+behaviour, and should not affect the perl scripts that are eventually
+executed by the perl binary. Other variables, like PERL_UNICODE,
+PERL5LIB, and PERL5OPTS will influence the behaviour of the test suite.
+So if you are getting strange test failures, you may want to try
+retesting with the various PERL variables unset.
+
--
Red sky at night - gerroff my land!
Red sky at morning - gerroff my land!
-- old farmers' sayings #14