Solaris compiler setup ?
David Holmes
david.holmes at oracle.com
Fri Oct 26 04:17:39 PDT 2012
On 26/10/2012 8:13 PM, Magnus Ihse Bursie wrote:
> On 2012-10-23 04:41, David Holmes wrote:
>> On 23/10/2012 10:13 AM, Magnus Ihse Bursie wrote:
>>> The compiler detection has changed a lot lately. Is this still a
>>> problem for you? If so, do you get a more descriptive output?
>>
>> I can't tell as the make discovery logic is now broken:
>>
>> checking for gmake... /usr/sfw/bin/gmake
>> configure: Testing potential make at /usr/sfw/bin/gmake, found using
>> gmake in PATH
>> configure: The path of FOUND_MAKE, which resolves as
>> "/usr/sfw/bin/gmake", is not found.
>> configure: error: Cannot locate the the path of FOUND_MAKE
>>
>> But gmake is there:
>>
>> > which gmake
>> /usr/sfw/bin/gmake
>
> This is a bit odd. My guess is that we're doing the following, and it
> fails: "which /usr/sfw/bin/gmake". (Maybe you can try that manually?)
> which /usr/sfw/bin/gmake
/usr/sfw/bin/gmake
> 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)
--
So now I get up to the compilers part, which seems to be fixed for CXX:
checking for cc... /java/devtools/i386/SUNWspro/SS12u1/bin/cc
configure: Resolving CC (as /java/devtools/i386/SUNWspro/SS12u1/bin/cc)
with 'which' failed, using /java/devtools/i386/SUNWspro/SS12u1/bin/cc
directly.
checking resolved symbolic links for CC...
/java/devtools/i386/SUNWspro/SS12u1/prod/bin/cc
checking if CC is disguised ccache... no, keeping CC
configure: Using Sun Studio C compiler version 5.10 (located at
/java/devtools/i386/SUNWspro/SS12u1/prod/bin/cc)
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... no
checking whether /java/devtools/i386/SUNWspro/SS12u1/prod/bin/cc accepts
-g... yes
checking for /java/devtools/i386/SUNWspro/SS12u1/prod/bin/cc option to
accept ISO C89... none needed
checking for cl... no
checking for CC... /java/devtools/i386/SUNWspro/SS12u1/bin/CC
configure: Resolving CXX (as /java/devtools/i386/SUNWspro/SS12u1/bin/CC)
with 'which' failed, using /java/devtools/i386/SUNWspro/SS12u1/bin/CC
directly.
checking resolved symbolic links for CXX...
/java/devtools/i386/SUNWspro/SS12u1/prod/bin/CC
checking if CXX is disguised ccache... no, keeping CXX
configure: Using Sun Studio C++ compiler version 5.10 (located at
/java/devtools/i386/SUNWspro/SS12u1/prod/bin/CC)
checking whether we are using the GNU C++ compiler... no
(note the problem using 'which' again)
But then it fails because it thinks I'm on a mac ;-)
checking whether we are using the GNU Objective C compiler... no
checking whether gcc accepts -g... no
configure: The path of OBJC, which resolves as "gcc", is not found.
configure: error: Cannot locate the the path of OBJC
configure exiting with result code 1
Pretty sure I don't need objective-C on Solaris :-)
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
Generating generated-configure.sh
/java/embedded/users/dh198349/build-infra/builds/../common/autoconf/autogen.sh:
line 51: autoconf: command not found
Generating custom generated-configure.sh
/java/embedded/users/dh198349/build-infra/builds/../common/autoconf/autogen.sh:
line 59: autoconf: command not found
David
-----
> /Magnus
More information about the build-infra-dev
mailing list