SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I have benn playing with all possible combinations of Slackware64 13 <stable> <multilib> <current>... Just to see what environment is best suited for my needs.
I do this in an USB HDD of 250 gigs, and an old lappy w an HDD of 120 gigs.
In my lappy I have Slackware64 13, so far I have been able to install all the dependencies from SlackBuilds, and build my own packages from source w src2pkg.
I can build the openCascade infrastructure from source after defining configuration flags, make, and trackinstall , no big deal except the time it takes to build it :-), but it bulds a package allright.
( considering the lappy is more than two years old and has only two Gigs RAM... and the sources for OpenCASCADE are on the hundreds of Megs...)
On the other side, in my USB HDD install, I enabled <current> and <multilb>, mainly for two reasons :
I wanted to get the grasp of working with Kde <current>, and I have to say that it was an awesome job porting it to <current>, and because I want to install some proprietary software that requires 32bit libs...
So, I enabled <multilib>, but my intents were frustrated by two things... :
Trying to install the Intel Compilers still asks for this... :
32-bit libraries not found on this system.
This product release requires the presence of 32-bit compatibility libraries
when running on Intel(R) 64 architecture systems. One or more of these libraries
could not be found:
Without these libraries, the compiler will not function properly. Please refer
to Release Notes for more information.
1. See next issue [default]
2. Back to Pre-requisite summary dialog
b. Back to the previous menu
Please type a selection or press "Enter" to accept default choice :
So my question is :
Do the missing things are present in the system, although in a different prefix ( this would simply ammount to extending LD_LIBRARY_PATH to include its wereabouts... ) ?
Or Do they exist, but simply cannot be "seen" by the installer because they were of the wrong ELF type...? ( installer wants 32, yet it finds 64 )
Or worse, they simply do not exist in the system , and must be created from source, ( using a slackbuild probably ) ?
"libstdc++5" That one, at least, is going to be a problem. Since Slackware64-13.0 is the first release of Slack64, there are no previous versions of libstdc++. You *may* be able to use a symlink to libstdc++6, but I wouldn't bet on it.
It's a bit of a shame that the error states "one or more of these libraries could not be found" as they should all be present if you installed every *-compat32 package from my site.
The libstdc++5 as well as other library files are of course the 32-bit versions that the Intel compiler is looking for, not 64-bit versions. They are present in the a-compat32/cxxlibs-compat32-6.0.10-x86_64-1.txz package.
Is there a log file perhaps that has more detail on what exactly is missing?
I followed your detailed wiki "almost" step by step... I say "almost" because there is something I forgot before trying to Install Intel...
I did no source the environment script /etc/profile.d/32dev.sh...
Maybe this is why the installer was not finding what it was looking for... ?! Dunno... anyway, I will try again after having sourced this at .bashrc level, and I will be back with more news... :-)
One more question, having sourced the env script will forcibly default to a 32 bit compilation in a source project, so does this mean that if I want a 64 bit build all I have to do is "forget" the environment script...? or are there more clever means of control...?
Alex: You can setup a new user account with this environment setting in bashrc script. This account You'll be using for building 32-bit apps only. 64-bit apps You may build then with standard account as usually
In his speech in Australia, after having left Corregidor, he said the officially famous sentence "I came out of Bataan and I shall return"...
After having initially wanted to resign his comission, and fight with the Phillipino Resistance against Dai Nippon Teikoku Kaigun ( The Navy of The Empire of Japan ) and , and having discussed the issue with his Staff, he was demoted to do so, by Presiden Roosevelt, having said "I'll be back"