Guido van Rossum <guido@python.org> writes: > > Several machines in the snake farm fail to build libpython2.3 because > > they don't have ar in their path. ar, ld and the like live in > > /usr/ccs/bin, which seems to be some kind of standard (for generous > > values of standard) as both SunOS 5.8, AIX 4.3 and HP/UX 11.00 seems > > ot have this dir. > > > > Should the configure script try with /usr/ccs/bin/ar and ld if none is > > explicitly supplied? > > This may be a good idea, but I don't know zit about this area. I'm > cc'ing python-dev, maybeo someone there understands this. Trying ar from /usr/ccs/bin might be reasonable, but it *must* try ar from PATH before that. I fail to see what common scenario this would fail for, though: If you don't have ar(1) in your path, how do you find make(1)? In no case configure should try /usr/ccs/bin/ld: Invoking ld directly is always incorrect (except for archaic systems). Regards, Martin
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4