Salix Forums

I've just installed the 64-bit version of Salix. Wanted to build some packages that I need. So far as I can see, SLKBUILD doesn't support x86_64, or am I missing something? So far, I've used it, then gone and edited ARCH and flags to get what I need.

Any chance of extending it to support x86_64?

Either I can't read or the documentation is a bit out of date. Just tried using x86_64 in the arch field of a SLKBUILD and it works.....

paul.

All you have to do is change the arch line in SLKBUILD to:. If you want a SLKBUILD prototype with this, just edit the SLKBUILD prototype in /etc/slkbuild and rename it something like SLKBUILD.x86. Then when you want to build a new package just issue the following in your build directory: . See "man slkbuild"

Note that the -g function in the current version of slkbuild has a bug which result in getting the stock SLKBUILD file. I believe that gapan is aware of this bug and will be fixing it.
Rich

laprjns wrote:If you want a SLKBUILD prototype with this, just edit the SLKBUILD prototype in /etc/slkbuild and rename it something like SLKBUILD.x86. Then when you want to build a new package just issue the following in your build directory:

Code: Select all

 slkbuild -g x86

. See "man slkbuild"

I think there should be more templates for slkbuild available in the pure standard installation from ISO. So the user and beginning packagers have a clearer way of learning how slkbuild works. Nevertheless, slkbuild is a great tool so far.

laprjns wrote: Note that the -g function in the current version of slkbuild has a bug which result in getting the stock SLKBUILD file. I believe that gapan is aware of this bug and will be fixing it.
Rich

Yes, I hope also that this bug will be fixed soon.

Don't forget to use "--libdir=/usr/lib${LIBDIRSUFFIX}" in the configure options

thenktor wrote:Don't forget to use "--libdir=/usr/lib${LIBDIRSUFFIX}" in the configure options

Additional question: So it should be possible to run applications built for 32 bits under Salix64 if the according libs will be available under /usr/lib/

Yes

damNageHack wrote:Additional question: So it should be possible to run applications built for 32 bits under Salix64 if the according libs will be available under /usr/lib/

That has nothing to do with slkbuild or package building. You can do multilib in slackware, just google for it. But don't expect to use a multilib system for package building.

gapan wrote: That has nothing to do with slkbuild or package building. You can do multilib in slackware, just google for it. But don't expect to use a multilib system for package building.

Therefore I wrote "Additional question" (means nearly offtopic). I don't expect to do multilib, asked just in case I would need a 32 bits app that is not available (yet) for x86_64.

I did not wanted to change the original topic of packaging, sorry.

laprjns wrote:All you have to do is change the arch line in SLKBUILD to:

Code: Select all

arch=x86_64

. If you want a SLKBUILD prototype with this, just edit the SLKBUILD prototype in /etc/slkbuild and rename it something like SLKBUILD.x86. Then when you want to build a new package just issue the following in your build directory:

Code: Select all

 slkbuild -g x86

. See "man slkbuild"

Note that the -g function in the current version of slkbuild has a bug which result in getting the stock SLKBUILD file. I believe that gapan is aware of this bug and will be fixing it.
Rich

Thanks Rich. I managed to get the x86_64 working, so I've managed to build some of the packages I need (mc-4.7.0.1, which finally has Fish fixed, Osmo and associated libraries). I'll go read the packaging rules and submit them sometime in the next few days.

A bit off topic, but maybe someone can answer - is it possible to build for 32-bit systems from the 64-bit? I'd build for both, but I don't currently have the space to install the 32-bit version as well.

paul.

toothandnail wrote: A bit off topic, but maybe someone can answer - is it possible to build for 32-bit systems from the 64-bit? I'd build for both, but I don't currently have the space to install the 32-bit version as well.

Not directly, but you can use a VM.