Seema Alevoor wrote: > > That is why the cc path was hardcoded in earlier releases (/opt/SUNWspro/bin > was the default path before IPS package was introduced). > But there were users who preferred non-hardcoded value.
So which of the discussed approaches are you taking? Reading through 6774187 it seems you're going with plain 'cc' and let it find whatever is in PATH, even if gcc in which case it fails? > Yeah...since /opt/SUNWspro/bin is no longer the default path. Note that these same Apache bits go into Nevada and OpenSolaris. For OpenSolaris the default is /opt/SunStudioExpress since that comes from the IPS-available studio package. For Nevada at this moment the answer is still to manually install Studio, so people are going to end up with it in /opt/SUNWspro. There's also a recent case to add a version of Studio by default under /usr (LSARC/2009/017). That's probably the best default to pick after it shows up but that doesn't help you right now ;-( > As suggested by Basant (but with the reverse logic), first check for cc in > the path. > If it is Sun compiler use it. Else check for /opt/SunStudioExpress/bin. If > not found, > check in /opt/SUNWspro/bin. That sounds reasonable. > We can also handle this with a two step approach. > For this release, have it as "cc" without additional checks and let us > document > the need for Sun Studio compiler in the path. > Then in the subsequent release, add additional checks to reduce the > possibility > of non-Sun compiler usage. If that is approach, be sure there's a CR filed to track this.. -- Jyri J. Virkki - jyri.virkki at sun.com - Sun Microsystems
