Technically the way I posted sometimes doesn't work either ... I know, I wish the cmake options were more standardized and worked every time, kinda like standard automake system, I don't remember the last time that failed me.

I compiled some stuff for my own use, if you need something (patch, edited slackbuilds or precompiled binaries for x86_64), just have a look here.
nothing original, mostly stuff taken from slackbuilds.org with a few additions, but hope it can be useful.

Your devede package puts what should be in /usr/lib64/devede/* to /usr/lib. Devede needs --libdir=/usr/lib64 --pkglibdir=/usr/lib64 passed to the ./install.sh

I looked at a couple of your other SlackBuilds. Quite a few have errors. glibmm.SlackBuild is missing the ARCH=${ARCH:-x86_64} field (no arch at all is defined), there are also no CLAGS defined for x86_64, so even if you pass ARCH=x86_64 to the script, you'd miss at least -fPIC. x264 is the same, as is cairomm. I didn't look at all of them.

I'd do a little more editing on them. Nice collection so far

In case anyone want to know I always use this to compile any libraries for my 64-bit system:

and ffmpeg needs something special:

otherwise the .so shared libs will be installed in /usr/lib.

yeah, tnx for fixing

the missing flags are intentional: individual slackbuilds are to be called from the main one, that got the list of stuff to compile and environment variables, just like in kde build (I actually copied it ).

if you need to compile a subset best way is to copy the Addons.SlackBuild to Foo.SlackBuild, edit it with the stuff you want to compile and then execute it.

Found that out earlier as well

Someone should make a list of the special cases, like ffmpeg, aften, and some of the other oddities.

@poncez OIC

Funny, since my ffmpeg.SlackBuild does not have a "--libdir=/usr/lib64 --shlibdir=/usr/lib64" at all :-)

It builds a nice 64 bit package if you set ARCH to x86_64.

Eric

I'm interested in checking any weird cases -I have src2pkg adding lib64 options automatically when appropriate and will be writing a 'lint' routine to check for 64-bit 'mistakes' in finished packages, as well as trying to integrate bette checking and correction of cmake files and hard-coded Makefiles -fun stuff! srcspk will also add the LDFLAGS="-L/lib64 -L/usr/lib64" for you if you want/need them. I'm trying to work everything out so these arch-specific options are independent of the build script, so you don't need to maintain separate build scripts or do anything special with the environment to build 32 or 64-bit packages using the same script.

surely better than my approach: slackbuild everything on a virtual machine and then see what has gone in /usr/lib
Aristotle should be proud of me

Not this one - http://www.slackware.com/~alien/slac...eg/pkg64/12.2/

And, the package you linked to - a nice 64 bit package does indeed have --libdir= and --shlib in it

Attached Thumbnails

   

Thanks for taking the time to check these packages and their SlackBuilds disturbed1 ... I have screwed up the SlackBuild by overwriting it with an older version. Will set things right ASAP.

Cheers, Eric

Thanking me
No, thank you for all your work on Slackware, and this 64 port!

Sure. It allows me to set something straight. And btw... I fixed the content of the "build" as well as the "pkg64" directories at http://www.slackware.com/~alien/slackbuilds/ffmpeg/ so all is well again ;-)
You're welcome.

Eric

exactly my feeling, tnx a lot bob.

I'm saying this also as a long time user of your scripts/packages, you eased my slackware experience a lot

What about ogre3d, any way to make this beast install itself in /usr/lib64, I can seem to find anything on the net about this, nothing mentioned so far works.