[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [GNU Autoconf 2.63] testsuite: 166 failed
From: |
Ralf Wildenhues |
Subject: |
Re: [GNU Autoconf 2.63] testsuite: 166 failed |
Date: |
Fri, 10 Oct 2008 21:35:13 +0200 |
User-agent: |
Mutt/1.5.18 (2008-05-17) |
[ in case you're not subscribed: ]
<http://thread.gmane.org/gmane.comp.sysutils.autoconf.bugs/6319/focus=6320>
Hi Eric, Thomas,
* Eric Blake wrote on Fri, Oct 10, 2008 at 09:20:47PM CEST:
> Hmmm. This is potentially buggy, anyway. It is unsafe to call cd "$srcdir"
> if
> $srcdir is a relative path, does not contain /, and CDPATH is set in the
> environment (POSIX requires that it output the destination path as discovered
> by the CDPATH lookup). Of course, configure has already tried to unset
> CDPATH,
> but what if the user declared it to be a read-only variable?
I think we've at one time declared the user deserving the consequences
if she sets CDPATH to be read-only. There is lots more code in
autotools that can break in this case, and not much you can do about it.
I'm not sure whether letting configure barf over read-only CDPATH
(if it can portably be tested, that is) would be a good idea.
As long as CDPATH contains only paths that don't deal with this code,
users could rightfully(?) complain about that. Maybe a big fat warning
instead?
Thomas, is read-only CDPATH the issue here BTW?
Thanks for looking at this, BTW, Eric.
Cheers,
Ralf