From rshepard at appl-ecosys.com Sat Mar 14 19:02:23 2015 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sat, 14 Mar 2015 12:02:23 -0700 (PDT) Subject: [sbopkg-users] Sbopkg Not Working Properly Here Message-ID: This is my second attempt to use sbopkg without success. Someone here can probably tell me where my errors are to be found. One package I'm trying to upgrade is pgadmin3. Sbopkg fails with this error message: ../pgadmin/include/ctl/ctlSQLBox.h:17:24: fatal error: wx/stc/stc.h: No such file or directory #include ^ compilation terminated. make[3]: *** [pgAdmin3.o] Error 1 make[3]: Leaving directory /tmp/SBo/pgadmin3-1.20.0/pgadmin' make[2]: *** [all] Error 2 make[2]: Leaving directory /tmp/SBo/pgadmin3-1.20.0/pgadmin' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory /tmp/SBo/pgadmin3-1.20.0' make: *** [all] Error 2 Here, that header file is located in: /usr/include/wx-3.0/wx/stc/stc.h Were I building this slackbuild package manually I'd change the configuration file to show the path as above; it's apparently not aware of the wx-3.0/ subdirectory in the path. How should I provide the correct path for sbopkg? TIA, Rich From michiel.van.wessem at gmail.com Sun Mar 15 01:43:56 2015 From: michiel.van.wessem at gmail.com (Michiel van Wessem) Date: Sun, 15 Mar 2015 01:43:56 +0000 Subject: [sbopkg-users] Sbopkg Not Working Properly Here In-Reply-To: References: Message-ID: <20150315014356.78515370@hades.olympus.lan> On Sat, 14 Mar 2015 12:02:23 -0700 (PDT) Rich Shepard wrote: > Here, that header file is located in: > /usr/include/wx-3.0/wx/stc/stc.h > It's not sbopkg that fails here .. I think the failure if any is nothing else then you making the assumption that sbopkg will do magic(tm) and are acting surprised when that is not the case. you seem to be using a different version of wxPython (since the version of slackbuilds.org uses /usr/include/wx-2.8/wx/stc/stc.h), then is supplied on slackbuilds.org. Sbopkg is just a tool that makes things a little bit easier for the user. No Magic, just some clever scripting. SBopkg does give you the ability to edit the slackbuilds and as such you could do the same thing as you have always done, edit the slackbuild so it will find the correct libraries of any newer versions. It should use your modified slackbuild then over the `stock one'. The manpage and documentation should be able to help you out on this. -M. -- Michiel van Wessem (http://michielvwessem.wordpress.com) I figured out what's wrong with life: it's other people.