Date: Mon, 5 Sep 2011 11:45:17 -0400
From: "Josef 'Jeff' Sipek" <jeffpc@josefsipek.net>
To: Ken McDonell <kenj@internode.on.net>
Cc: pcp@oss.sgi.com
Subject: Re: [pcp] [Fwd: Re:  build issues]
Message-ID: <20110905154517.GA9504@josefsipek.net>
References: <1315177389.2810.41.camel@bozo.localdomain>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1315177389.2810.41.camel@bozo.localdomain>
User-Agent: Mutt/1.5.21 (2010-09-15)

On Mon, Sep 05, 2011 at 09:03:09AM +1000, Ken McDonell wrote:
> Remove the attachment so that oss.sgi.com police won't block the
> mail ...
> 
> -------- Forwarded Message --------
> From: Ken McDonell <kenj@internode.on.net>
> To: Josef 'Jeff' Sipek <jeffpc@josefsipek.net>
> Cc: pcp@oss.sgi.com
> Subject: Re: [pcp] build issues
> Date: Mon, 05 Sep 2011 07:49:54 +1000
> 
> On Sun, 2011-09-04 at 01:12 -0400, Josef 'Jeff' Sipek wrote:
> > Hello all!
> > 
> > I'm trying to package up PCP for OpenIndiana [1].  I grabbed the 3.5.8
> > tarball and applied the Solaris related commits in git.  It builds fine.
> > The issue is with the install target.
> 
> Jeff,
> 
> This works "out of the box" (tm) for me on OpenIndiana in the QA
> Farm ...
> 
> Here is my recipe snippet
> 
> pull the latest git pieces
> 
> $ make distclean
> $ ./Makepkgs || botch
> : this should work on _all_ platforms, and for OpenIndiana creates
> : solaris packages in build/sun (in addition to a tarball that can be
> : ignored)
> : ... look for errors and warnings in Logs/pcp
> $ cd build/sun
> $ yes Y | sudo /usr/sbin/pkgrm pcp
> $ yes Y | sudo /usr/sbin/pkgadd -d pcp-3.5.9 all || botch

Aha.  That's where we're diverging.  You are using the SVR4 package manager.
OI build (for post-151 release) is switching to IPS (see pkg(1)) and uses a
fork of Oracle's Userland repo (which is much like BSD's ports tree).

The typical package build steps in Userland are (it's all scripted):

1) get the tarball
2) unpack
3) apply all patches
4) build with appropriate prefix, etc.
5) install via DESTDIR to a prototype area
6) generate package manifest using the prototype area & other metadata
   stored along the build script
7) store it in a temp IPS repo

I'm trying to make the build script which will let OI ship PCP packages.

> How are you trying to run the "package build process"?
> 
> DESTDIR is only used for the Perl bits I think, and then I am guessing
> you're trying to to "make install" ... which is not the right recipe.

Yep.  Just doing the usual... make && make install.

Thanks,

Jeff.

P.S. As far as I know, Solaris 11 will be using pkg(1) in favor of
pkg{add,rm} for Oracle provided software.

-- 
The obvious mathematical breakthrough would be development of an easy way to
factor large prime numbers.
		- Bill Gates, The Road Ahead, pg. 265