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. On Wed, Mar 4, 2015 at 12:31 AM, David Holmes <david.hol...@oracle.com> wrote: > On 4/03/2015 6:24 PM, Erik Joelsson wrote: > >> At least when we were building on Solaris 10 I think we needed to add >> that to be sure to get the right tools. It might not be needed on >> Solaris 11. >> > > It's not needed on Solaris 10 if you already have the right tools in your > path. :( Comment suggests it was needed because the wrong tools were being > found in someone's path. Augmenting the path should be the last resort > though, not the first. > > Cheers, > David > > > /Erik >> >> On 2015-03-04 01:12, David Holmes wrote: >> >>> toolchain.m4 prepends /usr/ccs/bin to the PATH on Solaris, which is a >>> bad thing if you already have your path set up to the correct >>> toolchain! I expect there is some history here, but it seems wrong to me. >>> >>> Thanks, >>> David >>> >> >>
