[SOLVED] Unable to build SuiteSparse (from SBo) in multilib 64-current.
SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Unable to build SuiteSparse (from SBo) in multilib 64-current.
Exactly what it says on the tin.
Trying to build SuiteSparse from SBo and failling to link because of incompatibility of /usr/lib64/gcc/x86_64-slackware-linux/4.7.1/libgfortranbegin.a.
I think it's right, and that the file is a 64 bit.
I have slackware-13.37 multilib, and in /usr/ I have i486-slackware-linux/ for 32 bit, and x86_64-slackware-linux for 64bit. I think it grabbed a 64 bit file.
I think it's right, and that the file is a 64 bit.
I have slackware-13.37 multilib, and in /usr/ I have i486-slackware-linux/ for 32 bit, and x86_64-slackware-linux for 64bit. I think it grabbed a 64 bit file.
I don't have i486-slackware-linux anywhere. Both /usr/lib/gcc and /usr/lib64/gcc have only an x86_64-slackware-linux directory. What I'm thinking is that -currents multilib is broken at the moment.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.