On Mon, Dec 14, 2015 at 04:02:01PM +0000, Jonathan Perkin wrote:
> * On 2015-12-14 at 15:47 GMT, Filip Chabik wrote:
> 
> > I'm pretty sure there are other people like me that would see the
> > benefit in bringing Performance Co-Pilot (PCP) to the SmartOS world.
> > 
> > [...]
> >
> > I then realized, that it would actually make more sense to port it to
> > pkgsrc (PCP is open source and you can grab the source to potentially
> > build the packages).
> 
> Perfect ;)
> 
> > I went to https://pkgsrc.joyent.com to learn how to build package from
> > the source and to prepare my environment.
> > 
> > Unfortunately, I hit the wall. Here are the relevant error messages I
> > came across:
> > 
> > ./configure: line 7260: -spec: command not found
> > ./configure: line 7263: test: : integer expression expected
> > ./configure: line 7268: test: : integer expression expected
> > gmake: Makefile: No such file or directory
> > gmake: *** No rule to make target 'Makefile'.  Stop.
> 
> At this point there aren't any generic instructions to follow, it's
> just a matter of digging into the build process for the software you
> are packaging, and try to figure out what it is doing.
> 
> The line preceeding the '-spec: command not found' error is:
> 
>   checking Qt version...

Speaking of Qt...I have this patch locally to make PCP compile on OI.  YMMV.

Jeff.

diff --git a/Makepkgs b/Makepkgs
index 03f58ee..4c362ab 100755
--- a/Makepkgs
+++ b/Makepkgs
@@ -213,7 +213,8 @@ in
        ;;
     sunos|SunOS)
        ARCH=`isainfo -k`
-       [ "$ARCH" = amd64 -o "$ARCH" = sparcv9 ] && configopts="$configopts 
--libdir=/usr/lib/64"
+       configopts="$configopts --disable-ssp"
+       #[ "$ARCH" = amd64 -o "$ARCH" = sparcv9 ] && configopts="$configopts 
--disable-ssp --libdir=/usr/lib/64"
        export YACC=bison
        export LEX=flex
        ;;
diff --git a/src/include/builddefs.in b/src/include/builddefs.in
index 1977f89..d7d2798 100644
--- a/src/include/builddefs.in
+++ b/src/include/builddefs.in
@@ -168,7 +168,7 @@ GIT = @GIT@
 PYTHON = @PYTHON@
 PYTHON3        = @PYTHON3@
 DTRACE  = @DTRACE@
-QMAKE  = @qmake@
+QMAKE  = @qmake@ -spec solaris-g++
 
 INSTALL_SH = $(TOPDIR)/install-sh
 INSTALL        = $(INSTALL_SH) -o $(PCP_USER_INSTALL) -g $(PCP_GROUP_INSTALL)

> 
> So the first step here would be to check the source and documentation
> to see if Qt is a hard requirement.  If it is, then you'll need to
> change the package to pull in the version of Qt required, using
> something like:
> 
> .include "../../x11/qt4-libs/buildlink3.mk"
> 
> Buildlink is the infrastructure used to pull in dependencies, and
> ensure they are linked correctly.  You can find more documentation
> about it in the pkgsrc guide, and you should be able to find plenty of
> examples of other packages using it in the pkgsrc tree ('git grep' is
> a huge help when developing pkgsrc).
> 
> After that it's usually a case of trial-and-error, with multiple
> rebuilds and adding new dependencies via buildlink3 (make sure you
> 'bmake clean' before trying again to ensure the new dependencies are
> correctly pulled in), until you end up with something which can build.
> 
> Ordinarily the ./configure stage should fail if a hard requirement is
> missing, so it might be worth an upstream bug to report the fact that
> ./configure exited ok but didn't produce a Makefile in this case.
> 
> Good luck!  If you need any further help don't hesistate to ask on IRC
> in either #pkgsrc or #smartos on Freenode.
> 
> --
> Jonathan Perkin  -  Joyent, Inc.  -  www.joyent.com
> 

-- 
Ready; T=0.01/0.01 11:06:01


-------------------------------------------
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Reply via email to