Compile-time packages

New features which should be implemented in Porteus; suggestions are welcome. All questions or problems with testing releases (alpha, beta, or rc) should go in their relevant thread here, rather than the Bug Reports section.
Post Reply
User avatar
Ahau
King of Docs
King of Docs
Posts: 1331
Joined: 28 Dec 2010, 15:18
Distribution: LXDE & Xfce 32/64-bit
Location: USA

Compile-time packages

Post#1 by Ahau » 23 Nov 2011, 15:51

Hello all,

While going through the exercise of compiling several packages from source (for XFCE), I ran into trouble. As I worked through the issues, I sorted out that there are some development packages that are included with standard Slackware (which have been removed from Porteus) that are necessary to get things working smoothly. They were a little tricky because of my inexperience with the standard Slackware and with compiling in general. At fanthom's request, I'm starting this thread to list these packages, with the idea that some of them may need to be included in the development module. If any of you have run across similar issues and have suggestions (or would like help finding answers), please feel free to add your comments.

Here's what I found:

linuxdoc-tools
This one was especially tricky to sort out because it does not show as a dependency during the configure script. Configuration completed as normal and compilation started, only to fail towards the end with xml parser errors (in the case of gnome-disk-utility) or an error regarding the usage of /usr/bin/xsltproc -nonet (in the case of udisks and upower).

cmake
This one was easier to figure out. It was required on my part to compile libproxy, but I'm sure other packages require it as well.

ca-certificates
This package was required in order to compile glib-networking (a dep of libsoup, which is a dep of gnome-disk-utility, which is an optional dep for gvfs). I got around it for a while with the use of the --without-ca-certificates parameter, but for only 100kB in size, I figure it's worth adding to avoid making customizations to the compile scripts (and therefore introducing more chances for me to foul-up). It would not belong in the development module, but keep it in mind if you start seeing certificate errors.
Please take a look at our online documentation, here. Suggestions are welcome!

User avatar
brokenman
Site Admin
Site Admin
Posts: 5439
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Re: Compile-time packages

Post#2 by brokenman » 23 Nov 2011, 18:30

linuxdoc-tools
I also found this while trying to compile a gnome power manager

cmake is fast becoming a standard. I think we need to include this one for sure.
How do i become super user?
Wear your underpants on the outside and put on a cape.

User avatar
wread
Module Guard
Module Guard
Posts: 1062
Joined: 09 Jan 2011, 18:48
Distribution: Porteus v3.2.5-kde5-64 bits
Location: Santo Domingo
Contact:

Re: Compile-time packages

Post#3 by wread » 30 Nov 2011, 16:52

I posted a cmake-2.8.4 module for porteus 32-bits a while ago. I have it in modules as a standard for me. I think all members of the xzm-team have it also included in their systems...

Interesting is to report this: in my mediafire repo cmake was required with 18 downloads, git-1.7.5.4 has been downloaded 22 times and the java-module, jre-1.6.0 has been downloaded 143 times! - a bestseller- :)
(Are there 143 porteus users interested in the jre module?)

Regards

EDIT: automoc4 will be needed for anything that you compile using qt.....could be thought as part of a combo with cmake together. Can be downloaded as xzm-module from
http://www.mediafire.com/?4lva7at687o4bkm
Porteus is proud of the FASTEST KDE ever made.....(take akonadi, nepomuk and soprano out and you will have a decent OS).
The Porteus Community never sleeps!

Post Reply