On 21/11/2007, Bhaskar Jayaraman <[EMAIL PROTECTED]> wrote:
> Hi thanks for your posts so far. Since what I had assumed was a 32 bit kernel 
> which I compiled didn't work, I religiously set out on compiling a 64 bit 
> version as my system is currently booted in 64 bit mode.
> I installed SUNStudio12 on the system and set the SPRO_VROOT to point towards 
> it and when I do a make all in usr/src directory, I get the following error 
> when make cwds and runs in the i86pc/unix direcotry: -
>

If you would, please limit this type of posting to opensolaris-code
*or* opensolaris-discuss in the future.

However, to further assist you:

1) Compiling with SS12 is not yet supported, see the developer's
reference or documentation. Studio 11 is supported.

2) You must be on a relatively new Solaris Express install to perform
compilation in many cases.

3) In my experience, I have been unable to build parts of the source
tree without running nightly at least once, after that I was always
able to build individual parts the way you are doing.

4) Generally the right way to compile or work with the ON tree is to:

1) change to the top level source directory (one level above usr)

2) cp usr/src/tools/env/opensolaris.sh .

3) Open opensolaris.sh in a text editor

4) Change GATE and CODEMGR_WS to match the location of your workspace

5) Change MAILTO and STAFFER to suit you

6) Save the changes and exit the text editor

7) Run /opt/onbld/bin/bldenv -d opensolaris.sh

I would also suggest using a version of SUNWonbld from here as
appropriate for your architecture:

http://dlc.sun.com/osol/scm/SUNWonbld/SUNWonbld-latest.i386.tar.bz2
http://dlc.sun.com/osol/scm/SUNWonbld/SUNWonbld-latest.sparc.tar.bz2

-- 
Shawn Walker, Software and Systems Analyst
http://binarycrusader.blogspot.com/

"We don't have enough parallel universes to allow all uses of all
junction types--in the absence of quantum computing the combinatorics
are not in our favor..." --Larry Wall
_______________________________________________
opensolaris-help mailing list
[email protected]

Reply via email to