Thanks, between the information you have given me, and that Nathan has given me I think I've got a good chance of getting things to work. I don't know if I'll boot back into Pup 1.0.5 and try it tonight, but if I don't I will tomorrow. After several days of working on it I'm thinking of just surfing tonight. Oh, btw I did try the slackware packages, and they didn't work. The one I tried was GnuPG, and it installed without any problem, but when I tried to run ./gpg it couldn't find a library file it needed.Anonymous wrote:Here's a simple explanation I've found (works for me) for compiling on a Slackware based system:
PACKAGE CREATION
================
1. Create the package creation directory
# mkdir -p /pkgcreate/usr/local
2. Unpack the source distribution, configure it
then compile.
... you should be in /pkgcreate (?)
# tar -zxvf foobar-a.b.c.tar.gz (so you now have directory /pkgcreate/foobar-a.b.c )
# cd foobar-a.b.c
# ./configure --prefix=/usr/local (the ultimate destination)
# make
3. 'Install' the created files in the package
creation directory.
# make install prefix=/pkgcreate/usr/local (where you want the intermediate install to go)
4. Build the tarball package
# cd /pkgcreate
# makepkg foobar-a.b.c-i686-1.tgz
(usually follow the suggestions to create symbolic
links via the script and to NOT change ownership
attributes of the files)
5. Presto you have your tarball package! Stow it
away for safekeeping. (when you "installpkg" it will now go into /usr/local)
Hope this helps a bit.
Rgds
GS
vp&ftgs
The most dangerous man, to any government, is the man who is able to think things out for himself, without regard to the prevailing superstitions and taboos. Almost inevitably he comes to the conclusion that the government he lives under is dishonest, insane and intolerable, and so, if he is romantic, he tries to change it. And even if he is not romantic personally he is very apt to spread discontent among those who are.
H.L. Mencken
' Shoot, after fooling with windoze for several years Linux is a breeze ':lol:'. I'm just trying to get off to a running start. I love to tinker, and working with an OS that is friendly to tinkering, and customization is great. It's also very refreshing to work with an OS that don't crash when you push it just a little, and is not ram starved. I've pushed Puppy way beyond the limits of anything I could do with windoze, and it ain't even wimpered ':P:'. I did kind of crash it one night though, although it really wasn't a crash as such. I had been surfing all night, and had multiple browser windows open, with multiple tabs open in each one. I wasn't paying the least bit of attention to system resources because it wasn't too long after I got Puppy online, and I was still used to the behavior of windoze. Anyway, I opened one window too many, and all of a sudden everything stopped except for the mouse, and it would only move very slowly, and jerked when moving. I managed to get one last thing to open, the view running processes, which I had minimumized (sp?), and it revealed that I had 640Mb out of 640Mb of ram in use. It actually didn't crash, it just did not have any ram left to work with, and quit responding. The thing that impressed me most was the fact that up until it had used the last bit of ram available it had showed absolutly no sign of being under any stress. Had I been using win2k or any other version of windoze, the computer would have crashed a long time before I got anywhere near that point, and would have been complaining loudly about the stress it was under. Puppy is one tough Pup!
Puppy - A computers Best Friend