10 Steps to Caiman Development on Indiana

In one of our meetings the other day I was pointing out to the team that I could tell most of them weren't using Indiana as their primary development platform, because I was finding bugs in the Caiman source release when attempting to build it using Indiana.  Usually we're pretty good at eating our own dog food, but that hasn't really happened much yet with Indiana, in part because we've had a couple of other things to do at the same time.  Some of the team suggested that one of the issues holding them back is that there's a bunch of additional stuff you need to add to the base Indiana install to make it suitable for development use, and they didn't feel they had the time to figure it out.  Well, fortunately, I already have, at least for Caiman development, since I put Indiana on my laptop right after we released it 2.5 months ago, and my desktop a few weeks later (my desktop at home is still running SXCE for a bunch of mostly lame reasons).  So, without further ado, here's my brief cheat-sheet on how to get an Indiana system into shape for OpenSolaris development:
  1. Follow the instructions for downloading the live CD, burning it, booting it, installing from it
  2. Once you've booted from the disk, make sure you update the system (which is mentioned in the above instructions, but bears repeating since it will fix some critical problems, such as the broken SVR4 packaging software on the preview media).
  3. Install the header files: pkg install SUNWhea
  4. Install Mercurial: pkg install SUNWmercurial
  5. Install make: pkg install SUNWsprot
  6. Install Java: pkg install SUNWj6rt
  7. Follow the instructions to download and install the compilers and build tools, though you'll want the tools from the SCM Migration project so that they work with Mercurial.
  8. In order to build the Caiman sources, download and pkgadd SUNWwbint, SUNWzoneint, and SUNWldskint (SUNWldskint isn't up there yet, we're working on getting that corrected).
  9. If you have an NVIDIA graphics controller, then you probably want to install NVDAgraphics and NVDAgraphicsr from the Nevada media or NVIDIA's web site.
  10. A few other things you might find yourself wanting; first two are on the Nevada media.
    • SUNWflash-player-plugin
    • SUNWrealplayer
    • OpenOffice 2.3
I haven't tried building the OS/Net sources on Indiana since I haven't had a need lately, but I don't know of any reason why it wouldn't work.


Is there a reason why there is no OpenOffice IPS package yet ?


Posted by EdwardOCallaghan on January 11, 2008 at 04:03 PM EST #

"I haven't tried building the OS/Net sources on Indiana since I haven't had a need lately, but I don't know of any reason why it wouldn't work."

It doesn't work. the version of SUNWsprot that pkg pulls in doesn't include the assembler. The assembler is non-redistributable, and the ON sources rely on a lot of it's functionality that GAS doesn't provide.

Posted by JohnS on January 11, 2008 at 06:55 PM EST #

Why is Java runtime (SUNWj6rt) needed to do OpenSolaris development?

How's come Nvidia has such beautiful Sun/Solaris compliant System V packages? Did they get a little help from Sun? One doesn't see a vendor churn out such slick packages for Solaris these days (most are broken in one way or another). So, how did Nvidia do it?

Posted by UX-admin on January 11, 2008 at 08:10 PM EST #

Is anyone able to get the image-update step to work? I've been trying off and on for weeks, and every time I do, pkg.opensolaris.org just times out or fails to retrieve anything. I finally dug into the pkg script that is failing this time and extracted a URL.

% curl -O http://pkg.opensolaris.org/filelist/0
curl: (52) Empty reply from server

And indeed, if I do the HTTP request manually I don't get any headers back, it just closes the connection.

Posted by Nicholas Riley on January 12, 2008 at 05:31 AM EST #

John, thanks for the note about the assembler. I'll have to find out when we'll have that resolved.

Edward, the OpenOffice packages are in the works, I don't know exactly what the issues were with them but they're a high priority to add to the repository.

Nicholas, I'd suggest posting your issues to pkg-discuss@opensolaris.org or indiana-discuss; many of us have successfully updated so I'm unaware of a problem with it.

UX-admin: You'll need the Java runtime to build some things on ON; you don't actually need it at this point for Caiman. We have worked very closely with Nvidia on the port of the drivers since we've been bundling them with Solaris, so I'm sure that has something to do with the condition of the packages.

Posted by Dave Miner on January 12, 2008 at 07:34 AM EST #

I found out that showrev was missing after installation (svn_79). I have to installed SUNWadmlib-sysid SUNWadmc SUNWadmfw from Nevada installation CD.



Posted by Jan Hlodan on March 08, 2008 at 06:35 AM EST #

Right. showrev is being replaced with a simpler implementation which should have fewer dependencies. See http://blogs.sun.com/clayb/entry/removing_admintool_and_replacing_what

Posted by Dave Miner on March 10, 2008 at 07:20 AM EDT #

Post a Comment:
Comments are closed for this entry.

I'm the architect for Solaris deployment and system management, with a lot of background in networking on the side. I spend a lot of my time currently operating Solaris Engineering's OpenStack cloud. I am co-author of the OpenSolaris Bible (Wiley, 2009). I also play a lot of golf.


« June 2016

No bookmarks in folder


No bookmarks in folder