[indiana-discuss] Indiana impressions after 1 week

[Kristin Amundsen]

Ok, I have been playing with Indiana developer 2 preview for a week now 
both at home and work.

The install was super easy.  It seems to run great as a desktop. 

Sadly, I have had no end of frustration with trying to compile 
something... anything really.  I do not see this so much as an Indiana 
problem as a documentation problem.

I decided to approach this as a "newbie" (which I really am since I did 
not really played with Indiana much during the previous release) and use 
only externally available information. 

So, I saw there was no compiler.  I thought that was funny since this is 
a "developer" preview... but no problem.  I know that has been discussed 
before but I do think the name will cause Joe-New-To-OpenSolaris a lot 
of confusion.  I downloaded Sun Studio 11 and got that installed just 
fine.  I tested it quick by running cc -### foo.c just to make sure 
something worked.  I need to do UNIX work so I checked c89, it was ok.  
Then I checked c99.  Not working.  Grumble. 

I moved on to compile hello_world.c and cc cannot find stdio.h.  Yes, 
/usr/include is there but none of the headers I expected to see (like 
stdio.h) are there.  Hmm... ok.  So I started looking all around the 
Indiana pages on opensolaris.org looking for any information about how 
to get the headers.  After not finding it there, I just started looking 
at download center on opensolaris.org to try to find them.  I also did a 
search of the Indiana discussion alias for information.  I never found 
what I wanted through the download center but I did see this in an email 
discussion:

 > Are you trying to compile this on the Indiana prototype? If so, be
 > sure that you've adding SUNWhea
 >
 > # pkg install SUNWhea
 >
 > And if you haven't already installed SUNWsprot, you'll probably want
 > that package as well installed.

Ok... so I tried that and I see:

-bash-3.2# pkg install SUNWhea
Creating PlanTraceback (most recent call last):
  File "/usr/bin/pkg", line 856, in ?
    ret = main_func()
  File "/usr/bin/pkg", line 824, in main_func
    return install(img, pargs)
  File "/usr/bin/pkg", line 367, in install
    verbose = verbose, noexecute = noexecute)
  File "/usr/lib/python2.4/vendor-packages/pkg/client/image.py", line 
923, in list_install
    ip.evaluate()
  File "/usr/lib/python2.4/vendor-packages/pkg/client/imageplan.py", 
line 285, in evaluate
    self.evaluate_fmri(f)
  File "/usr/lib/python2.4/vendor-packages/pkg/client/imageplan.py", 
line 148, in evaluate_fmri
    retrieve.get_manifest(self.image, pfmri)
  File "/usr/lib/python2.4/vendor-packages/pkg/client/retrieve.py", line 
59, in get_manifest
    raise NameError, "could not retrieve manifest '%s' from '%s'" % \
NameError: could not retrieve manifest 
'SUNWhea at 0.5.11%2C5.11-0.79%3A20080205T181206Z' from 
'http://pkg.opensolaris.org:80'

Yick.  Thank you Sun firewall.  Ok... more searching email archives to 
find...

 > The default port is 80 for this very reason.
 >
 > Did you try setting http_proxy environment variable?

Ok, haven't heard of that one before... but I set it and SUNWhea 
installed, yay!

And finally... I can compile something.  I still can't get c99 to be 
happy but cc and c89 work.

The steps to get things working were really easy... but... finding the 
information I needed to do something as simple as compile hello_world.c 
was way too hard.  Why is this information not super easy to find on the 
Indiana web page?  I would think after running end-user apps the next 
most common task for joe-user would be to try compiling something.  It 
seems like the steps to make that possible should be someplace painfully 
obvious.

Now to see if I can actually build and run what I need to.

-Kristin
_______________________________________________
indiana-discuss mailing list
indiana-discuss at opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss

--
This message posted from opensolaris.org