Changes by Martin v. Löwis mar...@v.loewis.de:
--
resolution: - fixed
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8453
___
David Bolen db3l@gmail.com added the comment:
The buildbot user's shell is also bash, so not entirely sure yet why it's
behaving differently in my environment. I had completely forgotten about bash
having a default path.
I do agree that explicitly setting a minimal path is a good idea.
Ned Deily n...@acm.org added the comment:
+1. Thanks, all.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8453
___
___
Python-bugs-list mailing
R. David Murray rdmur...@bitdance.com added the comment:
I don't think bash itself has a default path, I think the default path is set
by the system bash profile, and is therefore system dependant. I could be
wrong, though.
--
nosy: +r.david.murray
New submission from Martin v. Löwis mar...@v.loewis.de:
The current build_installer fails to build dependencies, e.g. with
gcc-4.0 -arch i386 -arch ppc -isysroot /Developer/SDKs/MacOSX10.4u.sdk -o
bzip2 bzip2.o -L. -lbz2
collect2: cannot find 'ld'
collect2: cannot find 'ld'
lipo: can't open
Ned Deily n...@acm.org added the comment:
Odd, works for me on 10.4, 10.5, and 10.6 (but I have never tried running under
buildbot, if that is what is happening here).
For 10.4 with its most-recent Xcode installed:
$ /usr/bin/ld -v
Apple Computer, Inc. version cctools-622.9~2
$ /usr/bin/gcc
Ned Deily n...@acm.org added the comment:
I still don't understand why that isn't showing up in my environment (I've been
running with that change for over a year) and I can't see why ld would fail but
ar and ran don't. Can you verify the version of Xcode that has been installed?
Perhaps
Ned Deily n...@acm.org added the comment:
(er, ranlib)
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8453
___
___
Python-bugs-list mailing list
Martin v. Löwis mar...@v.loewis.de added the comment:
I personally can't verify what version of Xcode is installed. David?
In any case, David reported that he could build installers just fine on that
very machine before r80179, but not after.
--
nosy: +db3l
David Bolen db3l@gmail.com added the comment:
I believe it's XCode 2.4.1.
I know the script worked fine prior to the change that clears the environment,
and commenting out just that piece of the latest trunk copy continues to work.
To be honest, I'm not sure how the build even finds
Ronald Oussoren ronaldousso...@mac.com added the comment:
r80232 explicitly sets $PATH to the system default one, which hopefully fixes
the issue.
What would be interesting to know is which shell is the user shell on the
buildbot. The original patch worked for me because my shell is bash and
11 matches
Mail list logo
