On Tue, 24 Feb 2009 12:01:03 -0500 Jeff Trawick <Jeffrey.Trawick at Sun.COM> wrote:
> Seema Alevoor wrote: > > Hi, > > > > Webrev for the following CRs is at > > http://cr.opensolaris.org/~seema/6761354/ > > 6774187 APR and HTTPD build files contain hard-coded compiler path > > This issue bugs me a bit. Installing SUNWgcc puts cc in the default > PATH, and that cc won't handle our cflags (and apxs/apr-1-config > should use a compiler matching the build anyway). > > Two compilers are delivered with OpenSolaris: > SUNWgcc in /usr/gnu/bin and sunstudioexpress in > /opt/SunStudioExpress/prod/bin Too many versions. On my 2008.11 it's /opt/SUNWspro/bin. Apache gets gcc by default. > The latter is the one which is suitable for use. The current > hard-coding of /opt/SUNWspro doesn't match either of those. > > A few possible changes: > [chop] > This issue is worth discussion to see if there are more ideas and > select the best trade-offs. How about punting the definition of CC to an included file, to narrow it down to one place the path needs setting. Then run a test in there: try different CC paths on a HelloWorld, and set it to whatever works or complain and bail out if nothing worked. Or maybe it isn't even necessary to compile HelloWorld, and it might be sufficient to test that $(candidate-CC) is an executable? -- Nick Kew Application Development with Apache - the Apache Modules Book http://www.apachetutor.org/
