Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
How come I can run './configure --prefix=/usr --libdir=/usr/lib64' and it will work 99% of the time, while for cmake the following often do not work, or sometimes work and sometimes don't:
Please, if there is any way to be 100% sure that libraries will be installed to /usr/lib64, post it so we can all benefit. I would be very grateful. Otherwise, it seems I will have to steer clear of cmake, because it just doesn't want to listen to anything I tell it. It's just not worth the time and headache.
Your question, however seems to have been answered by your homework in the negative. So this post is more of a safety valve for hot steam :-P.
There _is_ no way to make cmake 64bit friendly. You have proved that. Sadly, guys who write good C and C++ can't necessarily script :-/.
Have you tried setting & exporting $LIBDIR?
There is also the following non-FHS non-kosher bodge: Close all 32 bit stuff
mv /usr/lib /usr/lib32
ln -s /usr/lib64 /usr/lib
./configure etc :-D.
fix lib paths.
Or you can let it scatter files to whatever lib directories it likes, and then cobble a little script to run file -b on them, grep for 32/64 and move them accordingly.
Yes, I was thinking of symlinking it like that. But, this should not be necessary. What if I will need multilib some day, it'll screw everything up. It's really a bad thing to symlink like that, I've done it before and I know.
This problem is most troublesome with OGRE, so I'll just stay away from anything that links to it. I tried those solutions and they don't work.
I wasn't intending the symlink to be a permanent thing. Just for the duration of the make.
FYI, I have a laxer attitude here. On my 64-bit multilib box, my /usr/lib is _predominantly_ 32 bit, but not exclusively so. All the automagic stuff sorts it out just fine, and I get no errors. The only hassle is if I install a 32 bit version of a 64 bit lib that I already have in /usr/lib, and something gets koshed.
You can also simply make packages as you're in slackware. Then you only have a few libs. Mind you, I avoid cmake when I can.
I just noticed that OGRE is installed wrong on my computer. I used the 'DOGRE_LIB_DIRECTORY=/usr/lib64' from the site documentation, and that did install the libs there, but the includes were written to /usr/local. What an absolute mess. I'll just never have anything to do with this OGRE, I guess I know now why it's called that.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.