X-Spam-Checker-Version: SpamAssassin 3.4.0-r929098 (2010-03-30) on oss.sgi.com X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham version=3.4.0-r929098 Received: from cuda.sgi.com (cuda2.sgi.com [192.48.176.25]) by oss.sgi.com (8.14.3/8.14.3/SuSE Linux 0.8) with ESMTP id p84N2wH4234414 for ; Sun, 4 Sep 2011 18:02:58 -0500 X-ASG-Debug-ID: 1315177376-3260010a0000-S8gJnT X-Barracuda-URL: http://cuda.sgi.com:80/cgi-bin/mark.cgi Received: from ipmail04.adl6.internode.on.net (localhost [127.0.0.1]) by cuda.sgi.com (Spam Firewall) with ESMTP id C21C3133C47 for ; Sun, 4 Sep 2011 16:02:56 -0700 (PDT) Received: from ipmail04.adl6.internode.on.net (ipmail04.adl6.internode.on.net [150.101.137.141]) by cuda.sgi.com with ESMTP id 5FD2WXTEl8sVPsFE for ; Sun, 04 Sep 2011 16:02:56 -0700 (PDT) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ai0CACkBZE520d2u/2dsb2JhbAAMNoRNlGuRbgEBBCRbJwMBAgECAiYCUSGHc6ZakDaBLIQtgREEky6RHw Received: from ppp118-209-221-174.lns20.mel6.internode.on.net (HELO [192.168.1.100]) ([118.209.221.174]) by ipmail04.adl6.internode.on.net with ESMTP; 05 Sep 2011 08:32:55 +0930 X-ASG-Orig-Subj: [Fwd: Re: [pcp] build issues] Subject: [Fwd: Re: [pcp] build issues] From: Ken McDonell To: pcp@oss.sgi.com Content-Type: text/plain; charset="UTF-8" Date: Mon, 05 Sep 2011 09:03:09 +1000 Message-ID: <1315177389.2810.41.camel@bozo.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.32.2 Content-Transfer-Encoding: 7bit X-Barracuda-Connect: ipmail04.adl6.internode.on.net[150.101.137.141] X-Barracuda-Start-Time: 1315177377 X-Barracuda-Bayes: INNOCENT GLOBAL 0.0000 1.0000 -2.0210 X-Barracuda-Virus-Scanned: by cuda.sgi.com at sgi.com X-Barracuda-Spam-Score: -2.02 X-Barracuda-Spam-Status: No, SCORE=-2.02 using per-user scores of TAG_LEVEL=2.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=2.1 tests= X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.2.73661 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- X-Virus-Scanned: ClamAV version 0.94.2, clamav-milter version 0.94.2 on oss.sgi.com X-Virus-Status: Clean Remove the attachment so that oss.sgi.com police won't block the mail ... -------- Forwarded Message -------- From: Ken McDonell To: Josef 'Jeff' Sipek 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 $ sudo /usr/sbin/svcadm enable -s pcp/pcp I just ran my daily-pcp script for my OpenIndiana VM and it works as I expected, including running the -g sanity QA tests (I've attached the log in case this helps). [it all works except for a Perl build problem, which is related to 32-bit vs 64-bit builds, but this is existing, known and not related to your issue ... which causes 1 QA failure, and another QA failure that is a non-deterministic timing issue on VMs] > The package build process we're implementing at OI tries to use the DESTDIR > way of installing the software into a prototype directory. Sadly, the PCP > makefiles don't work that way. Thoughts about how to work around it? (I'd > rather not have to make a patch which changes every makefile to support > DESTDIR or something like it.) 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. If this does not help, we'll need to dig deeper to understand why my builds work and your do not. Cheers, Ken.