LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices



Reply
 
Search this Thread
Old 05-25-2009, 05:56 AM   #16
H_TeXMeX_H
Guru
 
Registered: Oct 2005
Location: $RANDOM
Distribution: slackware64
Posts: 12,928
Blog Entries: 2

Rep: Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269

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.
 
Old 05-25-2009, 10:02 AM   #17
ponce
Senior Member
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 2,504

Rep: Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912
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.

Last edited by ponce; 07-26-2009 at 05:57 AM.
 
Old 05-25-2009, 11:05 AM   #18
disturbed1
Senior Member
 
Registered: Mar 2005
Location: USA
Distribution: Slackware
Posts: 1,133
Blog Entries: 6

Original Poster
Rep: Reputation: 223Reputation: 223Reputation: 223
Quote:
Originally Posted by poncez View Post
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
 
Old 05-25-2009, 11:10 AM   #19
H_TeXMeX_H
Guru
 
Registered: Oct 2005
Location: $RANDOM
Distribution: slackware64
Posts: 12,928
Blog Entries: 2

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

Code:
./configure --prefix=/usr --libdir=/usr/lib64
and ffmpeg needs something special:

Code:
./configure --prefix=/usr --libdir=/usr/lib64 --shlibdir=/usr/lib64
otherwise the .so shared libs will be installed in /usr/lib.
 
Old 05-25-2009, 11:14 AM   #20
ponce
Senior Member
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 2,504

Rep: Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912
Quote:
Originally Posted by disturbed1 View Post
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
yeah, tnx for fixing

Quote:
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
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.

Last edited by ponce; 05-25-2009 at 12:01 PM.
 
Old 05-25-2009, 11:45 AM   #21
disturbed1
Senior Member
 
Registered: Mar 2005
Location: USA
Distribution: Slackware
Posts: 1,133
Blog Entries: 6

Original Poster
Rep: Reputation: 223Reputation: 223Reputation: 223
Quote:
Originally Posted by H_TeXMeX_H View Post
and ffmpeg needs something special:

Code:
./configure --prefix=/usr --libdir=/usr/lib64 --shlibdir=/usr/lib64
otherwise the .so shared libs will be installed in /usr/lib.
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
 
Old 05-25-2009, 03:14 PM   #22
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 5,393

Rep: Reputation: Disabled
Quote:
Originally Posted by disturbed1 View Post
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
 
Old 05-25-2009, 04:26 PM   #23
gnashley
Amigo developer
 
Registered: Dec 2003
Location: Germany
Distribution: Slackware
Posts: 4,776

Rep: Reputation: 481Reputation: 481Reputation: 481Reputation: 481Reputation: 481
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.
 
Old 05-25-2009, 05:39 PM   #24
ponce
Senior Member
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 2,504

Rep: Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912
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

Last edited by ponce; 05-25-2009 at 05:41 PM.
 
Old 05-25-2009, 09:48 PM   #25
disturbed1
Senior Member
 
Registered: Mar 2005
Location: USA
Distribution: Slackware
Posts: 1,133
Blog Entries: 6

Original Poster
Rep: Reputation: 223Reputation: 223Reputation: 223
Quote:
Originally Posted by Alien Bob View Post
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
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 Images
File Type: png snapshot1.png (139.8 KB, 8 views)
File Type: png snapshot2.png (132.4 KB, 9 views)

Last edited by disturbed1; 05-25-2009 at 09:52 PM.
 
Old 05-26-2009, 03:55 AM   #26
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 5,393

Rep: Reputation: Disabled
Quote:
Originally Posted by disturbed1 View Post
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
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
 
Old 05-26-2009, 08:02 AM   #27
disturbed1
Senior Member
 
Registered: Mar 2005
Location: USA
Distribution: Slackware
Posts: 1,133
Blog Entries: 6

Original Poster
Rep: Reputation: 223Reputation: 223Reputation: 223
Quote:
Originally Posted by Alien Bob View Post
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!
 
Old 05-26-2009, 08:55 AM   #28
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 5,393

Rep: Reputation: Disabled
Quote:
Originally Posted by disturbed1 View Post
Thanking me
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 ;-)
Quote:
No, thank you for all your work on Slackware, and this 64 port!
You're welcome.

Eric
 
Old 05-26-2009, 10:21 AM   #29
ponce
Senior Member
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 2,504

Rep: Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912
Quote:
Originally Posted by disturbed1 View Post
No, thank you for all your work on Slackware, and this 64 port!
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

Last edited by ponce; 05-26-2009 at 10:29 AM.
 
Old 02-14-2010, 09:05 AM   #30
H_TeXMeX_H
Guru
 
Registered: Oct 2005
Location: $RANDOM
Distribution: slackware64
Posts: 12,928
Blog Entries: 2

Rep: Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269
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.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
/usr/bin/ld: skipping incompatible /usr/lib/libXpm.so when searching for -lXpm sqn Linux - Server 2 05-12-2009 04:53 AM
oops, I stripped /usr/lib and /usr/X11R6/lib ! H_TeXMeX_H Slackware 2 02-08-2007 10:27 PM
Relocat /usr/lib and /usr/lib64 to a different path schokshi Fedora 3 08-30-2005 10:14 PM
Compromised? Files "/usr/lib.hwm", "/usr/lib.pwd", "/usr/lib.pwi" Klaus Pforte Linux - Security 4 09-29-2004 12:33 AM
Installing software, /usr/lib directory and /usr/local millertime Linux - Software 2 07-10-2004 10:21 AM


All times are GMT -5. The time now is 03:23 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration