SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Quick what does this mean:
Kindertagesstaettenbenutzungsgebuehren
Going on my sketchy German:
School field trip?
German is a kind of funny language. Luckily most words like this have just one meaning, and you wouldn't have to use it often unless you're the one who collects these "kinder garden usage fees". On the other hand, if you look up the 'zu' you'll find over 300 separate ways to use it!
"SIGNIATURE should be SIGNATURE" I still thought you were joking. I had to go look it up before disputing you and now see I'll have to eat crow! I guess I got too used to seeing signi??? from Spanish, although it's still 'signatura' in Spanish whatever it 'signifies'.
So, you win dive, I'll have to correct that. Unfortunately that means you'll have to update your src2pkg.conf file again next time. (Ahh well, Gilbert, perhaps you should take more afternoon naps...)
Scribus 1.3.3.11 built perfectly with src2pkg 1.9.2. It looks like I don't need to build Opera, the download page for the latest version does not offer source files that I could see, but they do have a Slackware package.
EDIT: I'm wrong. The Slackware download for Opera still needs to be made into a package. I'll let you know how it goes.
I'll probably soon be tackling Bluefish and Inkscape.
Some feedback from a Slackware 12 user. I installed the new version and ran the following to test my PHP 5 build:
Code:
src2pkg -A -C -VV -W -a='i686' -e='--with-apxs2=/usr/local/apache2/bin/apxs --with-openssl --with-mysql' php-5.2.5.tar.bz2
I've run it multiple times and each time it hangs on the PHP header files. After the successful build, the output is:
Code:
Build complete.
Don't forget to run 'make test'.
Compiling has been - Successful!
NOTICE - DESTDIR not supported. Falling back to JAIL install
Installing in jail root - Using: 'make install'
Installing PHP SAPI module: apache2handler
/usr/local/apache2/build/instdso.sh SH_LIBTOOL='/usr/local/apache2/build/libtool' libphp5.la /usr/local/apache2/modules
/usr/local/apache2/build/libtool --mode=install cp libphp5.la /usr/local/apache2/modules/
cp .libs/libphp5.so /usr/local/apache2/modules/libphp5.so
cp .libs/libphp5.lai /usr/local/apache2/modules/libphp5.la
libtool: install: warning: remember to run `libtool --finish /tmp/php-5.2.5-src-1/libs'
chmod 755 /usr/local/apache2/modules/libphp5.so
[activating module `php5' in /usr/local/apache2/conf/httpd.conf]
rm: cannot remove `/usr/local/apache2/conf/httpd.conf.new': No such file or directory
Installing PHP CLI binary: /usr/bin/
Installing PHP CLI man page: /usr/man/man1/
Installing build environment: /usr/lib/php/build/
Installing header files: /usr/include/php/
I uninstalled src2pkg-1.9.2-noarch-2.tgz and went back to the old version (src2pkg-1.8-i486-1_K26.tgz) so it's no big deal at this stage.
Maybe the problem is that it's using the jail since it says that DESTDIR is not supported? If anyone has any suggestions (or can point out errors I've made) I'll go back and re-do my packages and post the results.
EDIT: I get the same error with that version of src2pkg as well. It looks like I built the original PHP package with an earlier src2pkg release.
Lufbery: I think you want "./install.sh", not "make install". I don't get how "make install" could even work because I see no Makefile.
gilead: Are you talking about the error rm is spitting out? That error does not look like critical. Please post the rest of the output. BTW, is apache2 a package? If so, it should be in /usr, not /usr/local.
gilead: Are you talking about the error rm is spitting out? That error does not look like critical. Please post the rest of the output. BTW, is apache2 a package? If so, it should be in /usr, not /usr/local.
Sorry, no I didn't mean the rm error. The "Installing header files" line is where it hangs. I've let it sit for over half an hour on one occasion.
Apache 2.0 on my system is compiled and installed from sources manually. It's one of the applications I haven't gotten around to packaging up yet.
As I've already mentioned, quite a few small bugs got introduced in the last two versions with so much code being changed and moved around. I'm going to be away from home for two weeks starting on Wednesday so I've been trying to get rid of whatever problems have come up before I leave.
About building opera, you'll have to do that using -REAL (the old deafult) since the installer tries to install to the real path. Otherwise you'll probably get a package with just docs. And tuxedv is correct that you need 'sh ./install.sh' as the install rule.
src2pkg -VV -C -W -S -i='sh ./install.sh' -n=opera -v=9.25 -REAL opera-9.25-20071214.6-shared-qt.i386-en.tar.gz
Now about php, it seems like it may be installing some files and then carrying out further operations on them or using them to process other files in the sources. Try building using the -REAL option (as root).
Having more than one method to install makes it a little confusing, perhaps. For most of its' life, src2pkg only used what is now called the 'REAL' method and it is still the most dependable. But you must be 'root' to use it and of course it makes it possible to damage your system. But, it still uses the same code as before to backup, and then restore, any files which get overwritten on your system. the other methods using DESTDIR and JAIL root have been introduced to make it possible for normal users to create packages and to reduce the risks from writing directly to your '/' directory. Unfortunately, neither DESTDIR nor JAIL will work every time -there was a very good reason that src2pkg used to 'spam' your '/' directory -running 'make install' directly provides the most dependable way to carry out the installation and provides the best chance of being able to accurately track the creation of files and directories. So, if you are unable to build a correct package using the DESTDIR or JAIL methods, you can always fall back to the old 'REAL' way of doing things.
I also recommend using SlackBuilds when they are available. I also find it quite easy to 'port' them to the src2pkg format(much easier than vice-versa!). I'll mention that I'm considering adding a feature to src2pkg which will search for SlackBuilds and use them when available. I've already gotten a start on some of the code, but this a pretty low-priority item for the moment. Many users get the idea that src2pkg will create a perfect package the first time, or that it tries to. This is not the case, though. There is no substitute for the human element when building packages and many, many packages need special steps or added options to be supplied in order to build correctly. This is especially true for complex programs which provide 'services' or otherwise need to be integrated into the init scripts. And since most of these programs don't come out-of-the-box with support for Slackware-style init script modifications, the package creators must take care of these things. Most of the SlackBuilds on SlackBuilds.org address just this sort of software, and though src2pkg may be able to successfully compile and package the program, the program may not work as expected. Still, src2pkg makes it extermely easy to repeat the build as many times as needed until everything is just right. Sometimes this means *dozens* of rebuilds.
About building opera, you'll have to do that using -REAL (the old deafult) since the installer tries to install to the real path. Otherwise you'll probably get a package with just docs. And tuxedv is correct that you need 'sh ./install.sh' as the install rule.
src2pkg -VV -C -W -S -i='sh ./install.sh' -n=opera -v=9.25 -REAL opera-9.25-20071214.6-shared-qt.i386-en.tar.gz
Ah, I see the mistake I made with "install.sh." So the bug was between my ears.
Still, I built Opera before with src2pkg 1.6 using this command:
There is no substitute for the human element when building packages and many, many packages need special steps or added options to be supplied in order to build correctly. This is especially true for complex programs which provide 'services' or otherwise need to be integrated into the init scripts. And since most of these programs don't come out-of-the-box with support for Slackware-style init script modifications, the package creators must take care of these things.
Before I started diving into this topic, I had no idea how complex it could be to build a good package. Src2pgk is, for me, a great way to learn more about the packages while creating functional software. If I had to script my builds from scratch, I wouldn't be as enthusiastic about the process.
Quote:
Most of the SlackBuilds on SlackBuilds.org address just this sort of software, and though src2pkg may be able to successfully compile and package the program, the program may not work as expected. Still, src2pkg makes it extremely easy to repeat the build as many times as needed until everything is just right. Sometimes this means *dozens* of rebuilds.
Gilbert, your support also greatly aids the process. Thank you.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
