Packages made with slackbuilds
My question is about building a package with a slackbuild script on one
computer and then installing it on another computer:
I'm not familiar with what goes on during the compile process. Will there
be problems with this?
Your question is very generic. You must specify what the OS of those computers you are reffering to are using.
If they have eg. up to date Slackware 12.2 the packages should work fine on both.
I do it all the time.
Qt4 is the only one that I had trouble with that I can remember. For some reason, every time I transfer qt4 with a flash card I get corrupted files errors.
It is how the packages in Slackware are built... one computers of the Slackware team, and then downloaded by countless (I hope) people on the Internet.
A "binary" package is compiled to run on a certain architecture (i386, x86_64, ARM, S/390, Power - you can not run a porpgram that was compiled for i386 on a computer with an ARM CPU) and the binaries expect to find the set of "dynamic libraries" on the destination computer that were present when the code was compiled and which it needs to function at all. That is why a package destined for Slackware 12.2 may (or may not) work on Slackware 10.0.
Sorry for the confusion.
I'm want to build packages using slackbuilds from www.slackbuilds.org
I'm using a live cd: slax 6.1.1 that I have sbopkg on.
I don't have an internet connection at the moment, so I thought I
would download and build some packages with sbopkg and then install
them on my computer at home.
I couldn't find a way to just download the packages without building
them with sbopkg. If it is a problem building them on another computer
I can download the sources and build them at home.
My friends computer is a dell Optiplex GX260.
My computer is a Compaq evo d500.
I am using Slackware 12.2
As i said before, and Alien Bob explained more thoroughly, if you compile the packages on the same version of the same OS, they will work.
|All times are GMT -5. The time now is 03:41 PM.|