>[Anders Qvist] >> 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. > >--Guido van Rossum (home page: http://www.python.org/~guido/) /usr/ccs was a semi-standard location introduced in the System V days, probably not before SVR4. ccs = C Compilation System, don't know whether to blame Sun or USL for this innovation :-) which used to give me lots of support problems because nobody ever had these things in their path. These days it can be fun when people try to run gcc without binutils on Solaris, since again some key stuff may not be in the path. Don't see that it would hurt to have the configure script try there, perhaps limited by OS type? The only one of the above I know about is Solaris, though.
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