Solaris compiler setup ?

[Magnus Ihse Bursie]

On 2012-10-26 13:17, David Holmes wrote:
>
> > which /usr/sfw/bin/gmake
> /usr/sfw/bin/gmake

Well that looked good at least. :)
>
>> I have just pushed a patch to build-infra that will detect if this is
>> the case, and if so just use /usr/sfw/bin/gmake directly. You are
>> encouraged to pull the latest build-infra and try it. :-)
>
> checking for gmake... /usr/sfw/bin/gmake
> configure: Testing potential make at /usr/sfw/bin/gmake, found using 
> gmake in PATH
> configure: Resolving FOUND_MAKE (as /usr/sfw/bin/gmake) with 'which' 
> failed, using /usr/sfw/bin/gmake directly.
> configure: Using GNU make 3.81 (or later) at /usr/sfw/bin/gmake 
> (version: GNU Make 3.81)

However, this is not the result configure is getting. It claims the 
result of running "which /usr/sfw/bin/gmake" is empty. Can you check the 
configure log which "which" binary that configure located? It should say 
something like
checking for which... /usr/bin/which

If it does, what does running "/usr/bin/which /usr/sfw/bin/gmake" tell 
you? And is it that outputted to stdout or stderr?
> But then it fails because it thinks I'm on a mac ;-)
Apparently we test for OBJC on all platforms except Windows (!). Don't 
know who wrote that or what he had been smoking. :-)
Nevertheless, autoconf seems buggy. If it determines that it can't find 
GNU Objective C compiler, then it shouldn't set OBJC=gcc. We've probably 
run clear of this before since all our test systems still had a gcc 
lurking somewhere.
> Pretty sure I don't need objective-C on Solaris :-)
I have a fix for that already. :-) But I'll want to double check that on 
our test systems before I push it, so I don't put the current 
integration in jeopardy.

> FYI the autoconf detection logic didn't seem to work right as it tried 
> to run autogen.sh even though I don't have autoconf on Solaris:
>
> Configure source code has been updated, checking time stamps
> Warning: The configure source files is newer than the generated files.
> Running autogen.sh to correct the situation

Probably the "which" witch hunting us again. I'm doing this test:
   if test "x`which autoconf 2> /dev/null`" = x; then
     echo "Cannot locate autoconf, unable to correct situation."
...
   else
     echo "Running autogen.sh to correct the situation"
...
   fi

/Magnus