> 7 mar 2015 kl. 03:18 skrev David Holmes <david.hol...@oracle.com>: > > > >> On 7/03/2015 12:50 AM, Magnus Ihse Bursie wrote: >>> On 2015-03-04 22:03, Martin Buchholz wrote: >>> I agree that configure should not mess with user's PATH and should >>> "auto-find" programs in /usr/ccs/bin only as a last resort. >>> >>> It would be reasonable, when configure fails on Solaris, to notice >>> that the >>> user does not have /usr/ccs/bin on PATH and suggest appending. >> >> I have opened https://bugs.openjdk.java.net/browse/JDK-8074557. >> >> Adding a warning to failed configure on Solaris due to missing build >> tools that presumably resides in /usr/ccs/bin seems like quite a lot of >> work. >> >> I suggest the following: >> Instead of prepending, append /usr/ccs/bin, so any binaries in the >> user's specified PATH are picked first. This will allow a properly set >> PATH to function, but it will still provide the "best effort" approach >> of configure to look in "well-known locations" for tools. >> >> Does that seem like an acceptable solution? > > Yes if not for that fact that there seems to have been an explicit reason for > pre-pending in the first place. But if noone can recall what that was ...
I think I know what it was but it is no longer relevant. The reason was to get the configure based build to work out of the box on certain machine configurations in Oracle, where the old build picked up tools from /usr/ccs/bin automatically. However, since Solaris machines in the Oracle setting should be using the devkit, this is no longer an issue. /Magnus > > Thanks, > David > >> /Magnus
