Solaris compiler setup ?

[Erik Joelsson]

Yes, I've noticed this too since this is how I always configure, but was 
already busy with too many parallel threads of development to fix it 
right away. Workaround is to touch spec.gmk and then run configure. I 
will go fix it now.

/Erik

On 2012-11-01 05:23, David Holmes wrote:
> On 30/10/2012 5:39 AM, Magnus Ihse Bursie wrote:
>> On 2012-10-26 16:36, Magnus Ihse Bursie wrote:
>>>> 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.
>>
>> I forgot to push that fix. Done now.
>>
>> How far do you get this time? :-)
>
> Not too far :(
>
> checking for mozilla headers in /java... /java/devtools/share/plugin
> checking for devtools path in /java... /java/devtools/i386/bin
> checking for GCC compiler path in /java... /java/devtools/i386/gnucc/bin
> configure: Current directory is 
> /java/embedded/users/dh198349/build-infra/builds/b01/se-solaris-i586-ea.
> configure: Since this is not the source root, configure will output 
> the configuration here
> configure: (as opposed to creating a configuration in 
> <src_root>/build/<conf-name>).
> configure: However, this directory is not empty. This is not allowed, 
> since it could
> configure: seriously mess up just about everything.
> configure: Try 'cd /java/embedded/users/dh198349/build-infra' and 
> restart configure
> configure: (or create a new empty directory and cd to it).
> configure: error: Will not continue creating configuration in 
> /java/embedded/users/dh198349/build-infra/builds/b01/se-solaris-i586-ea
> configure exiting with result code 1
>
> ---
>
> > ls -l b01/se-solaris-i586-ea
> total 40
> -rw-r--r--   1 daholme  staff      19688 Nov  1 00:18 config.log
>
>
> Is it tripping over its own output file ??? My script creates the 
> output directory then cd's to it and invokes configure.
>
> David
> -----
>
>>
>> /Magnus