On Wed, Jun 24, 2015 at 10:43:11PM -0400, Nathan Scott wrote:
> Hi all,
>
> Just setting up some build machines here, decided to have a crack
> at Solaris again since my old OpenIndiana VM image went to the big
> bit-bucket in the sky recently.
>
> I went for a fully native build - Solaris and toolchain (compilers)
> from Oracle so that the PCP scripting language modules will function
> correctly with the default perl and python binaries.
>
> Local setup uses x86_64 KVM virtualisation. Download the Solaris OS
> SolarisStudio toolchain from Oracle (requires an Oracle account), and
> follow the installation instructions - no issues here for me.
>
> Once a guest is fully installed and running you'll need to get a few
> extras like git, bison, and flex from the opencsw.org packaging site;
> again all straight forward.
>
> Next, clone a pcp git repo. Setup your environment to point to these
> tools:
> CC=/opt/solarisstudio12.3/bin/cc
> CXX=/opt/solarisstudio12.3/bin/CC
> YACC=/opt/csw/bin/bison
> LEX=/opt/csw/bin/flex
>
> Run "./Makepkgs --without-infiniband --without-manager" (these make
> use of compiler/language features not supported by the native tools -
> the infiniband one looks fairly easy to fix, pmmgr needs configure.ac
> checks to auto-disable it I guess).
>
> With latest git fixes (will all be in pcp-3.10.6), successful package
> generation results. Light sanity testing performed - pmcd & pmlogger
> start up, and make data available (locally and remotely).
I'm running a build on my laptop (OpenIndiana Hipster) right now.
FWIW, Solaris and Illumos-based distros (like OpenIndiana) have diverged in
some ways so making the assumption that Illumos == Solaris is dangerous.
Unfortunately, Illumos identifies rather confusingly:
$ uname -s
SunOS
$ uname -r
5.11
$ uname -o
Solaris
Jeff.
--
UNIX is user-friendly ... it's just selective about who its friends are
|