- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
History: I used a free, non-commercial version of the Intel Fortran Compiler for Linux 8.1, I think, in Fedora-Core-3 (FC3) Linux. The attractive features were the free Compiler, that it supported Cray-style pointers, and that it was able to work with my Advanced-MicroDevices (AMD) Duron central processing unit (cpu). Mr. Steve Lionel and perhaps another person kindly posted some advice in an Internet newsgroup or forum at that time. My hard-disk drive failed and was replaced. Then FC3 was no longer supported. I installed OpenSuSE-11.1 and am currently using it with the Linux kernel 2.6.27.25-0.1-pae, glibc-2.9-2.11.1, gcc-4.3-34.168, and binutils-2.19-9.3. My non-commercial license for version 8.0 or 8.1 of the Compiler at the time recently allowed me to proceed ahead with installing version 9.0.033 of the Compiler.--But that installation was reported as unsuccessful by running the corresponding script file install.sh. Also after typing the commands "source /opt/intel/fc/9.0/bin/ifortvars.sh" and "source /opt/intel/idb/9.0/bin/idbvars.sh," when trying to compile a simple sample file of Fortran source code named Test3.f using the command "ifort -c Test3.f" in the directory /opt/intel/fc/9.0/bin, the response from my computer was "-bash: ifort: command not found," even though both Test3.f and ifort were actually located in that directory. One of the problems might be that my glibc version is too new for the versions of glibc that will work with version 9.0.033 of the Compiler.
The only non-commercial version of the Compiler for Linux I could currently find on the Internet to download is the Intel Fortran Compiler for Linux Professional Edition 11.1, build 046, which requires 1 gigabyte of Random Access Memory (RAM), too much for my computer with only 256 MegaBytes (MB) of RAM installed in it. The ideal solution would be to find a non-commercial version of the Intel Fortran Compiler for Linux that I can still download and use in OpenSuSE-11.1 Linux with glibc-2.9-2.11.1, version 2.6.27.25-0.1-pae of the Linux kernel, 256 MB of RAM, etc. Is that possible? If so, which non-commercial version of the Compiler would be recommended and where on the Internet would I obtain it?
Another option I could imagine might be to search for a still-supported earlier version of OpenSuSE Linux or else of glibc that will work in OpenSuSE-11.1 Linux and perhaps other Linux software that will also work with version 9.0.033 of the Compiler, which at least my Intel license will still allow me to install. I assume that 256 MB of RAM will be sufficient to use version 9.0.033 of the Compiler. But I haven't checked any of the possibilities in this paragraph lately.
If glibc-2.9-2.11.1 being too high a version number is really my problem with trying to install version 9.0.033 of the Compiler in OpenSuSE-11.1 Linux, I recommend that in the future installation script files named install.sh be written to accommodate higher version numbers of glibc, etc., than exist at the time of attempted installation of the Compiler. Thanks in advance for anyone taking time to post helpful comments in this thread.
Pat
The only non-commercial version of the Compiler for Linux I could currently find on the Internet to download is the Intel Fortran Compiler for Linux Professional Edition 11.1, build 046, which requires 1 gigabyte of Random Access Memory (RAM), too much for my computer with only 256 MegaBytes (MB) of RAM installed in it. The ideal solution would be to find a non-commercial version of the Intel Fortran Compiler for Linux that I can still download and use in OpenSuSE-11.1 Linux with glibc-2.9-2.11.1, version 2.6.27.25-0.1-pae of the Linux kernel, 256 MB of RAM, etc. Is that possible? If so, which non-commercial version of the Compiler would be recommended and where on the Internet would I obtain it?
Another option I could imagine might be to search for a still-supported earlier version of OpenSuSE Linux or else of glibc that will work in OpenSuSE-11.1 Linux and perhaps other Linux software that will also work with version 9.0.033 of the Compiler, which at least my Intel license will still allow me to install. I assume that 256 MB of RAM will be sufficient to use version 9.0.033 of the Compiler. But I haven't checked any of the possibilities in this paragraph lately.
If glibc-2.9-2.11.1 being too high a version number is really my problem with trying to install version 9.0.033 of the Compiler in OpenSuSE-11.1 Linux, I recommend that in the future installation script files named install.sh be written to accommodate higher version numbers of glibc, etc., than exist at the time of attempted installation of the Compiler. Thanks in advance for anyone taking time to post helpful comments in this thread.
Pat
Link Copied
8 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Pat,
Yes, OpenSUSE 11.1 is probably too new for that older compiler.
Your system RAM is the bottleneck. Although you don't have the recommended ram for the Fortran v11.1, you might try it anyway. I suspect it may take longer to compile, but if your code is not too complex it should work. The memory usage tends to be for complex codes with nested interdependent USE statements, or large BLOCK DATA sections, or if you use -ipo or -fast (-fast has -ipo). So try Fortran v11.1 and avoid using -ipo
And please read the OpenSUSE installation guide: http://software.intel.com/en-us/articles/installing-intel-compilers-on-opensuse/
Note that even Intel Fortran v11.1 does not support OpenSUSE 11.1 at this point in time. Software vendors start a development cycle about 18months before the product release. So at that point in time you find the current distributions and versions and you design support for these existing distros/versions. It's impossible to make a product work for a future release of linux - too many variables and unknowns - things like where they'll put libraries, changes in glibc, etc. too many chances of major changes that will break your product.
So our philosophy is to have a matrix of supported distros/versions. These are tested and we know they work. Newer versions of supported distros OR strange fringe distros may work and probably will work. But it's impossible for any installer to keep up with all the distros and versions.
ron
Yes, OpenSUSE 11.1 is probably too new for that older compiler.
Your system RAM is the bottleneck. Although you don't have the recommended ram for the Fortran v11.1, you might try it anyway. I suspect it may take longer to compile, but if your code is not too complex it should work. The memory usage tends to be for complex codes with nested interdependent USE statements, or large BLOCK DATA sections, or if you use -ipo or -fast (-fast has -ipo). So try Fortran v11.1 and avoid using -ipo
And please read the OpenSUSE installation guide: http://software.intel.com/en-us/articles/installing-intel-compilers-on-opensuse/
Note that even Intel Fortran v11.1 does not support OpenSUSE 11.1 at this point in time. Software vendors start a development cycle about 18months before the product release. So at that point in time you find the current distributions and versions and you design support for these existing distros/versions. It's impossible to make a product work for a future release of linux - too many variables and unknowns - things like where they'll put libraries, changes in glibc, etc. too many chances of major changes that will break your product.
So our philosophy is to have a matrix of supported distros/versions. These are tested and we know they work. Newer versions of supported distros OR strange fringe distros may work and probably will work. But it's impossible for any installer to keep up with all the distros and versions.
ron
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks, Mr. Ronald Green, for kindly posting a knowledgeable reply, including a hyperlink to your detailed writing at http://software.Intel.com/en-us/articles/installing-intel-compilers-on-opensuse/ on the Internet. With Tim18's comments there and your writing at both Web sites, I have hope for possible success using the non-commercial version of the Intel Fortran Compiler for Linux Professional Edition 11.1 (IFCLPE) in my OpenSuSE-11.1 Linux installation. Although I did not design the IFCLPE or know in detail how it works and exactly what it does using Random Access Memory (RAM), it seems quite reasonable to me that one should be able to use little RAM in the IFCLPE when compiling a simple and relatively short Fortran program and in this way stay within my computer's 256-MegaByte (MB) RAM limitation. If so, I would like that! For the simple Fortran codes I might want to write, I should be able to avoid nested "USE" statements, since I don't know anything about them, and long "BLOCK DATA" statements. Also I don't know the purpose of the -ipo option in the IFCLPE, but hope I can avoid using that extensive-RAM-using feature of the IFCLPE.
Sorry, I neglected to mention the very-important fact that I use a 32-bit computer; the ia32 version of the IFCLPE is what I would want to try. But perhaps you could already guess that about a computer old enough to contain only 256 MB of RAM.--It was a display model in a store and purchased in the latter half of February of the year 2002.
Once again I have gcc-4.3-34.168 installed in my OpenSuSE-11.1 Linux installation. You wrote to use gcc-3.3, if I understand the numbering system properly, in both 32-bit OpenSuSE-11.1 Linux and in the 64-bit version of it, I think when compiling applications for use on 32-bit computers. Tim18 wrote that he had success using gcc-4.3 and libstdc++.so.5 in apparently a 64-bit computer using the 64-bit version of the IFCLPE, I suppose when compiling applications for use on 64-bit computers. He also wrote that "The SuSE-11.1 glibc is in fact newer than what has been tested with ifort"; "but it appears to work," again keeping in mind that Tim18 used a 64-bit computer and IFCLPE, whereas I use a 32-bit computer and would want to use the 32-bit IFCLPE. He installed gcc-4.3 and libstdc++.so.5 from the SuSE (I suppose probably OpenSuSE) Installation Software Graphical User Interface. However, based on your writing, Tim18 thought it was necessary to use the 32-bit gcc-3.3 for the 32-bit ifort command in 64-bit SuSE, of course on a 64-bit computer.
Question 1a: So I guess that gcc-3.3 and lisbstdc++-3.3 will be essential to use the 32-bit ifort command in the 32-bit version of OpenSuSE-11.1 on my 32-bit computer. Do you agree?
Question 1b: Would your commands I quote in question 1d below include uninstalling or replacing gcc-4.3 and perhaps libstdc++-4.3 with version 3.3 of them?
Question 1c: Or would I first have to uninstall the higher-numbered versions of gcc and libstdc before executing your commands to install version 3.3 of them?
Question 1d, one might say considering the "other side" of the same question 1a: Or instead of your commands
zypper install gcc33-32bit
zypper install libstdc++33-32bit
rm /usr/bin/gcc
ln -s /usr/bin/gcc-33 /usr/bin/gcc ,
in my 32-bit computer with the 32-bit IFCLPE should I also do what Tim18 did on his 64-bit computer probably when compiling 64-bit applications, namely to use gcc-4.3 and libstdc++.so.5, if necessary installing the missing one of them from the SuSE Graphical User Interface menu? Generally using a newer version of a software package is preferred, unless there is some essential reason for using the older version. But perhaps for the historical reason that the IFCLPE may have been developed for use with gcc-3.3 is why there is this essential reason to install gcc-3.3 and libstdc++-3.3 for use with the 32-bit ifort command in both 32- and 64-bit installations. If version 3.3 of both gcc and libstdc++ is essential for me, I suppose when making updates in YaST2 (Yet another Software Tool 2) to OpenSuSE-11.1 Linux I will have to be diligent to refuse updating gcc and libstdc++ beyond version 3.3 of them when given such opportunties.
As I recall gcc stands for GNU Compiler Collection. From http://directory.fsf.org/project/gpp on the Internet I learned that g++ is the GNU version of a compiler for the computer language C++. In my OpenSuSE-11.1 installation after I typed "rpm -qa | grep gcc", my computer "replied" to me with text including gcc-4.3-34.168. So I suppose that I have version 4.3-34.168 of g++ installed on my computer. Also from the Internet I learned that libstdc++ is a standard library for the computer language C++. Given that the C++ compiler installed on my computer's hard-disk drive is of the GNU variety, I suppose the libstdc++ would then be a standard library for g++. So it appears to me that your command "zypper install gcc33-32bit" would install version 3.3 of the g++; and your command "zypper install libstdc++33-32bit" would install version 3.3 of the standard library for version 3.3 of the g++. Furthermore from the above reasoning I make a guess: Since I probably have g++ 4.3-34.168 installed on my computer, I guess I may also have libstdc++ 4.3-34.168 installed on it. Based on what I found at a couple of places on the Internet, I suppose that via the command "rpm -qa | grep libsdtc" I may be able to check that guess.
Pat
Sorry, I neglected to mention the very-important fact that I use a 32-bit computer; the ia32 version of the IFCLPE is what I would want to try. But perhaps you could already guess that about a computer old enough to contain only 256 MB of RAM.--It was a display model in a store and purchased in the latter half of February of the year 2002.
Once again I have gcc-4.3-34.168 installed in my OpenSuSE-11.1 Linux installation. You wrote to use gcc-3.3, if I understand the numbering system properly, in both 32-bit OpenSuSE-11.1 Linux and in the 64-bit version of it, I think when compiling applications for use on 32-bit computers. Tim18 wrote that he had success using gcc-4.3 and libstdc++.so.5 in apparently a 64-bit computer using the 64-bit version of the IFCLPE, I suppose when compiling applications for use on 64-bit computers. He also wrote that "The SuSE-11.1 glibc is in fact newer than what has been tested with ifort"; "but it appears to work," again keeping in mind that Tim18 used a 64-bit computer and IFCLPE, whereas I use a 32-bit computer and would want to use the 32-bit IFCLPE. He installed gcc-4.3 and libstdc++.so.5 from the SuSE (I suppose probably OpenSuSE) Installation Software Graphical User Interface. However, based on your writing, Tim18 thought it was necessary to use the 32-bit gcc-3.3 for the 32-bit ifort command in 64-bit SuSE, of course on a 64-bit computer.
Question 1a: So I guess that gcc-3.3 and lisbstdc++-3.3 will be essential to use the 32-bit ifort command in the 32-bit version of OpenSuSE-11.1 on my 32-bit computer. Do you agree?
Question 1b: Would your commands I quote in question 1d below include uninstalling or replacing gcc-4.3 and perhaps libstdc++-4.3 with version 3.3 of them?
Question 1c: Or would I first have to uninstall the higher-numbered versions of gcc and libstdc before executing your commands to install version 3.3 of them?
Question 1d, one might say considering the "other side" of the same question 1a: Or instead of your commands
zypper install gcc33-32bit
zypper install libstdc++33-32bit
rm /usr/bin/gcc
ln -s /usr/bin/gcc-33 /usr/bin/gcc ,
in my 32-bit computer with the 32-bit IFCLPE should I also do what Tim18 did on his 64-bit computer probably when compiling 64-bit applications, namely to use gcc-4.3 and libstdc++.so.5, if necessary installing the missing one of them from the SuSE Graphical User Interface menu? Generally using a newer version of a software package is preferred, unless there is some essential reason for using the older version. But perhaps for the historical reason that the IFCLPE may have been developed for use with gcc-3.3 is why there is this essential reason to install gcc-3.3 and libstdc++-3.3 for use with the 32-bit ifort command in both 32- and 64-bit installations. If version 3.3 of both gcc and libstdc++ is essential for me, I suppose when making updates in YaST2 (Yet another Software Tool 2) to OpenSuSE-11.1 Linux I will have to be diligent to refuse updating gcc and libstdc++ beyond version 3.3 of them when given such opportunties.
As I recall gcc stands for GNU Compiler Collection. From http://directory.fsf.org/project/gpp on the Internet I learned that g++ is the GNU version of a compiler for the computer language C++. In my OpenSuSE-11.1 installation after I typed "rpm -qa | grep gcc", my computer "replied" to me with text including gcc-4.3-34.168. So I suppose that I have version 4.3-34.168 of g++ installed on my computer. Also from the Internet I learned that libstdc++ is a standard library for the computer language C++. Given that the C++ compiler installed on my computer's hard-disk drive is of the GNU variety, I suppose the libstdc++ would then be a standard library for g++. So it appears to me that your command "zypper install gcc33-32bit" would install version 3.3 of the g++; and your command "zypper install libstdc++33-32bit" would install version 3.3 of the standard library for version 3.3 of the g++. Furthermore from the above reasoning I make a guess: Since I probably have g++ 4.3-34.168 installed on my computer, I guess I may also have libstdc++ 4.3-34.168 installed on it. Based on what I found at a couple of places on the Internet, I suppose that via the command "rpm -qa | grep libsdtc" I may be able to check that guess.
Pat
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The article was written for installing the compiler on a 64bit version of OpenSUSE. Your 32bit installation might be quite a bit different.
So let us try to install using the gcc you have on the system by default.
First, check that g++ is installed. Surprisingly, many times the gcc package does NOT include g++. Try this:
g++ --version
just to see if it is installed. If not, find it and install it at the SAME VERSION as your gcc.
The installer will also look for libstdc++.so.5. Some systems only come with libstdc++.so.6. If this is the case, do this as root:
ln -s /usr/lib/libstdc++.so.6 /usr/lib/libstdc++.so.5
(assumes you find libstdc++.so.6 in /usr/lib. If not use the correct path)
Next, try to install IFCPEL 11.1. You only need the 32bit version so l_cprof_p_11.1.046_ia32.tgz is the package you need. The installer will complain that it is missing prerequisites - IGNORE the message and continue with the installation.
Once installed:
source /opt/intel/Compiler/11.1/046/bin/ifortvarsh.sh ia32
ifort -V
and then try to compile some simple helloworld.f90 or other very very simple fortran program.
ropn
So let us try to install using the gcc you have on the system by default.
First, check that g++ is installed. Surprisingly, many times the gcc package does NOT include g++. Try this:
g++ --version
just to see if it is installed. If not, find it and install it at the SAME VERSION as your gcc.
The installer will also look for libstdc++.so.5. Some systems only come with libstdc++.so.6. If this is the case, do this as root:
ln -s /usr/lib/libstdc++.so.6 /usr/lib/libstdc++.so.5
(assumes you find libstdc++.so.6 in /usr/lib. If not use the correct path)
Next, try to install IFCPEL 11.1. You only need the 32bit version so l_cprof_p_11.1.046_ia32.tgz is the package you need. The installer will complain that it is missing prerequisites - IGNORE the message and continue with the installation.
Once installed:
source /opt/intel/Compiler/11.1/046/bin/ifortvarsh.sh ia32
ifort -V
and then try to compile some simple helloworld.f90 or other very very simple fortran program.
ropn
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Quoting - Ronald W. Green (Intel)
The article was written for installing the compiler on a 64bit version of OpenSUSE. Your 32bit installation might be quite a bit different.
So let us try to install using the gcc you have on the system by default.
First, check that g++ is installed.
The installer will also look for libstdc++.so.5. Some systems only come with libstdc++.so.6.
So let us try to install using the gcc you have on the system by default.
First, check that g++ is installed.
The installer will also look for libstdc++.so.5. Some systems only come with libstdc++.so.6.
As Ron and I found difficulties using the 32-bit g++-4 with ifort ia32, you may find it better to install the gcc3-c++, as you already mentioned, if that appears as an option on Software Installation menu when you connect to a SUSE mirror.
In the OpenSUSE 11.1 Software Installation menu, you should also find the option to install libstdc++.so.5 (from a mirror server, it's not on my 32-bit installation DVD) alongside the default libstdc++.so.6.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
OK, I've installed OpenSUSE 11.1 32-bit on a Pentium D. More difficult than I expected.
I went through the hassle of rejecting online upgrade during installation, then configuring LAN card and letting Online Update run, which took longer than the original installation.
When I opened up the GUI Install Software menu, and searched for libstdc++, it presented a default set of choices which included both the libstdc++-33 which ifort needs and the newer ones which gcc needs, and it installed them OK.
The GUI menu didn't work for installing gcc and g++. I used
sudo zypper install gcc
sudo zypper install gcc-c++
This installed the SUSE 4.3 i586 builds.
Intel registration/download center didn't allow me to log in using the Firefox provided by SUSE. Bummer. Unexpectedly, Konqueror is OK. The download choice still switches back to 11.0 the first time, so must select 11.1 again.
After all this, the ifort "unsupported" installation proceeded with no unexpected hitches. I've been complaining for months about the message which says we need binutils 2.13 or newer, without even checking what binutils is there (once it decides you have an unsupported installation).
So Ron was right, the hitch about ifort not liking the default 32-bit g++ didn't come up on the pure 32-bit installation.
I went through the hassle of rejecting online upgrade during installation, then configuring LAN card and letting Online Update run, which took longer than the original installation.
When I opened up the GUI Install Software menu, and searched for libstdc++, it presented a default set of choices which included both the libstdc++-33 which ifort needs and the newer ones which gcc needs, and it installed them OK.
The GUI menu didn't work for installing gcc and g++. I used
sudo zypper install gcc
sudo zypper install gcc-c++
This installed the SUSE 4.3 i586 builds.
Intel registration/download center didn't allow me to log in using the Firefox provided by SUSE. Bummer. Unexpectedly, Konqueror is OK. The download choice still switches back to 11.0 the first time, so must select 11.1 again.
After all this, the ifort "unsupported" installation proceeded with no unexpected hitches. I've been complaining for months about the message which says we need binutils 2.13 or newer, without even checking what binutils is there (once it decides you have an unsupported installation).
So Ron was right, the hitch about ifort not liking the default 32-bit g++ didn't come up on the pure 32-bit installation.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello again, Mr. Ron Green. Thanks for your knowledgeable, kind, and prompt help and advice! Following your advice, in the terminal program, superuser mode I typed "yast." Then an interactive visual display appeared for YaST2 that I don't recall previously having seen. Apparently that was what you called the interactive mode (for YaST2). In it there were a couple of important details for me to discover: 1) Use the tab and arrow keys to maneuver among the various regions of that display. 2) After making a selection of a group of software packages, for example, "Base Development," to install, select Actions; List All Packages; Install All... Finally I had to select Accept and then often give an "OK" on making one or more dependencies compatible with the packages I wanted to install or vice versa. In the course of installing the "Base Development" or "C/C++ Development" group of software packages I noticed that a Fortran compiler was already installed or would be installed, probably as part of the gcc (GNU Compiler Collection), something I should have realized earlier. I will later return to this finding. I wanted to install both the Intel Fortran and C Compilers for Linux. But I was running out of hard-disk-drive space in my "/" (also called root?) partition when trying to install the "Integrated Development Environments" group of packages you wrote that would be needed for the C Compiler. And after putting the installation files for the C and Fortran Compilers in a sub-subdirectory of my OpenSuSE-11.1 home directory, even my "/home"-containing partition of my hard-disk drive was filling up, too. At one point in time I could not even get into the K Desktop Environment 3 (KDE3) of my OpenSuSE-11.1 Linux installation, I suppose because the "/" partition, which probably contains the OpenSuSE-11.1 Linux operating system, was nearly full.
To obtain more space on two partitions of my hard-disk drive I used a few steps. Among them I booted my computer from a GParted Live Compact Disc and gave myself more space on the "/home"- and "/"-containing partitions of my hard-disk drive. Your mention of the file libstdc++.so.6 instead of libstdc++.so.5 being installed in some installations fit my OpenSuSE-11.1 installation. So the link command you mentioned was appropriate to I suppose force the file libstdc++.so.6 to be used when the Intel Fortran Compiler Professional Edition for Linux (IFCPEL) 11.1 would be calling for libstdc++.so.5 in a working installation of IFCPEL 11.1. And the directory immediately containing libstdc++.so.6 was exactly /usr/lib, just as you wrote it could be. At some point in time, following your kindly written advice, I typed "g++ --version" and subsequently found that version 4.3.2, "[gcc-4_3-branch revision 141229]" of g++ was installed in my OpenSuSE-11.1 installation, I suppose, based on the quote I just made, as part of the gcc.
I unpacked the downloaded file l_prof_p_11.1.046_ia32.tgz using the command "tar -zxvf l_prof_p_11.1.046_ia32.tgz" in the terminal program in superuser mode. Among the messages displayed during that unpacking I saw the path /l_cprof_p_11.1.046/pset/32e/gcc-3.2/libstdc++.so.5 displayed minus the leading "/". So apparently the IFCPEL 11.1 was written for at least i) gcc 3.2 and glibc 3.2, assuming the version numbers for gcc and glibc are supposed to be the same, and ii) libstdc++.so.5. In the newly formed directory ../l_prof_p_11.1.046_ia32 I typed "./install.sh"; and that shell began to run. With my IFCPEL-11.1's serial number I was able to register the IFCPEL online using a different computer and then return from the registration Web site with an unlock code to install the IFCPEL 11.1.046 in my OpenSuSE-11.1-loaded computer. After inputting that unlock code there and choosing a typical installation, eventually I saw the message "-- Host machine does not support Intel Streaming SIMD 2 Extensions."--That would be Streaming Single Instruction Multiple Data 2 Extensions, or SSE2. So apparently my Hewlett-Packard Pavilion notebook computer's one-GigaHertz (GHz), Advanced-MicroDevices (AMD), Duron, central processing unit (cpu) does not support SSE2. From what I read on the Internet, AMD began supporting SSE2 with its Athlon 64 and Opteron cpus, which I guess may have first appeared on the open market after my Duron cpu did. So unfortunately the IFCPEL 11.1 will not work at all on my computer, due to this critically important program-hardware mismatch. Of course it was my fault not to consider this mismatch very seriously at an earlier time.
I considered the possibility of using an earlier version of OpenSuSE Linux, which might contain a version of glibc which would work with the Intel Fortran Compiler 9.0.033 for Linux, for which I have an installation file I am still licensed to use. I found that OpenSuSE 10.3 is still downloadable on August 21, 2009 from within http://download.opensuse.org/distribution/10.3/ on the Internet; however, from http://www.linuxforums.org/forum/suse-linux-help/124287-need-help-installing-gcc.html on the Internet, it appears that OpenSuSE 10.3 may contain gcc 4.2-24, which I just guess might still be too high a version number of I suspect both gcc and glibc for the Intel Fortran Compiler 9.0.033 for Linux to use.
Now I return to the finding that GNU Fortran, or gfortran, was probably already installed on my computer, I suppose as part of gcc in OpenSuSE-11.1 Linux. I doubt if that compiler supports Cray-style pointers.--About three or so years ago the Intel Fortran Compiler for Linux was the only free (for non-commercial use) Fortran compiler I knew, with an installation file available for downloading from the Internet, which would support Cray-style pointers. But when I don't need to use such pointers, I suppose the use of gfortran may be okay for me.
I tried to use gfortran to compile the following simple Fortran program I called Test3.f (The actual comment line is different from the one below.):
C A COMMENT LINE OF SOME SORT
X=3.0
Y=X**2
PRINT *, Y
STOP
END
.
Eventually I found some conditions in which I could compile, link, and run such a Fortran program:
1) gfortran -c Test3.f (This produced the object code Test3.o.)
gfortran -o Test3 Test3.o (This produced the executable file Test3 from the object-code-containing file Test3.o.)
./Test3
2) Taking out the intial comment line in Test3.f and calling the resulting source code Test4.f90:
gfortran -c Test4.f90
gfortran -o Test4 Test4.o
./Test4
I first tried typing just "Test3" to run the Test3 program; but instead from the Internet I found that I had to type "./Test3" to run or execute the program. Permission to execute the the executable file Test3 had apparently already been given by gfortran as a result of my command "gfortran -o Test3 Test3.o". Eventually I learned from the Internet that Test3.f could be converted to a Fortran-90-capable, Fortran-source-code file of the form Test3.f90 by replacing the "C," in Fortran in the 1960s and 1970s a commonly used "signal" for a comment line placed in column one of a Fortran line, with a "!" and changing the file extension from ".f" to ".f90".
I suppose that the gcc in OpenSuSE-11.1 Linux might also contain a GNU C and/or C++ compiler. But if so, I haven't experimented by trying to compile any test source code with it.
Again thanks, Mr. Ron Green, for kindly providing expert help so promptly for me in an Internet forum! A knowledge of details is important to get things done. You kindly took the time to provide some good details for me. I really appreciate a man like you!!
Pat
To obtain more space on two partitions of my hard-disk drive I used a few steps. Among them I booted my computer from a GParted Live Compact Disc and gave myself more space on the "/home"- and "/"-containing partitions of my hard-disk drive. Your mention of the file libstdc++.so.6 instead of libstdc++.so.5 being installed in some installations fit my OpenSuSE-11.1 installation. So the link command you mentioned was appropriate to I suppose force the file libstdc++.so.6 to be used when the Intel Fortran Compiler Professional Edition for Linux (IFCPEL) 11.1 would be calling for libstdc++.so.5 in a working installation of IFCPEL 11.1. And the directory immediately containing libstdc++.so.6 was exactly /usr/lib, just as you wrote it could be. At some point in time, following your kindly written advice, I typed "g++ --version" and subsequently found that version 4.3.2, "[gcc-4_3-branch revision 141229]" of g++ was installed in my OpenSuSE-11.1 installation, I suppose, based on the quote I just made, as part of the gcc.
I unpacked the downloaded file l_prof_p_11.1.046_ia32.tgz using the command "tar -zxvf l_prof_p_11.1.046_ia32.tgz" in the terminal program in superuser mode. Among the messages displayed during that unpacking I saw the path /l_cprof_p_11.1.046/pset/32e/gcc-3.2/libstdc++.so.5 displayed minus the leading "/". So apparently the IFCPEL 11.1 was written for at least i) gcc 3.2 and glibc 3.2, assuming the version numbers for gcc and glibc are supposed to be the same, and ii) libstdc++.so.5. In the newly formed directory ../l_prof_p_11.1.046_ia32 I typed "./install.sh"; and that shell began to run. With my IFCPEL-11.1's serial number I was able to register the IFCPEL online using a different computer and then return from the registration Web site with an unlock code to install the IFCPEL 11.1.046 in my OpenSuSE-11.1-loaded computer. After inputting that unlock code there and choosing a typical installation, eventually I saw the message "-- Host machine does not support Intel Streaming SIMD 2 Extensions."--That would be Streaming Single Instruction Multiple Data 2 Extensions, or SSE2. So apparently my Hewlett-Packard Pavilion notebook computer's one-GigaHertz (GHz), Advanced-MicroDevices (AMD), Duron, central processing unit (cpu) does not support SSE2. From what I read on the Internet, AMD began supporting SSE2 with its Athlon 64 and Opteron cpus, which I guess may have first appeared on the open market after my Duron cpu did. So unfortunately the IFCPEL 11.1 will not work at all on my computer, due to this critically important program-hardware mismatch. Of course it was my fault not to consider this mismatch very seriously at an earlier time.
I considered the possibility of using an earlier version of OpenSuSE Linux, which might contain a version of glibc which would work with the Intel Fortran Compiler 9.0.033 for Linux, for which I have an installation file I am still licensed to use. I found that OpenSuSE 10.3 is still downloadable on August 21, 2009 from within http://download.opensuse.org/distribution/10.3/ on the Internet; however, from http://www.linuxforums.org/forum/suse-linux-help/124287-need-help-installing-gcc.html on the Internet, it appears that OpenSuSE 10.3 may contain gcc 4.2-24, which I just guess might still be too high a version number of I suspect both gcc and glibc for the Intel Fortran Compiler 9.0.033 for Linux to use.
Now I return to the finding that GNU Fortran, or gfortran, was probably already installed on my computer, I suppose as part of gcc in OpenSuSE-11.1 Linux. I doubt if that compiler supports Cray-style pointers.--About three or so years ago the Intel Fortran Compiler for Linux was the only free (for non-commercial use) Fortran compiler I knew, with an installation file available for downloading from the Internet, which would support Cray-style pointers. But when I don't need to use such pointers, I suppose the use of gfortran may be okay for me.
I tried to use gfortran to compile the following simple Fortran program I called Test3.f (The actual comment line is different from the one below.):
C A COMMENT LINE OF SOME SORT
X=3.0
Y=X**2
PRINT *, Y
STOP
END
.
Eventually I found some conditions in which I could compile, link, and run such a Fortran program:
1) gfortran -c Test3.f (This produced the object
gfortran -o Test3 Test3.o (This produced the executable file Test3 from the object-code-containing file Test3.o.)
./Test3
2) Taking out the intial comment line in Test3.f and calling the resulting source code Test4.f90:
gfortran -c Test4.f90
gfortran -o Test4 Test4.o
./Test4
I first tried typing just "Test3" to run the Test3 program; but instead from the Internet I found that I had to type "./Test3" to run or execute the program. Permission to execute the the executable file Test3 had apparently already been given by gfortran as a result of my command "gfortran -o Test3 Test3.o". Eventually I learned from the Internet that Test3.f could be converted to a Fortran-90-capable, Fortran-source-code file of the form Test3.f90 by replacing the "C," in Fortran in the 1960s and 1970s a commonly used "signal" for a comment line placed in column one of a Fortran line, with a "!" and changing the file extension from ".f" to ".f90".
I suppose that the gcc in OpenSuSE-11.1 Linux might also contain a GNU C and/or C++ compiler. But if so, I haven't experimented by trying to compile any test source code with it.
Again thanks, Mr. Ron Green, for kindly providing expert help so promptly for me in an Internet forum! A knowledge of details is important to get things done. You kindly took the time to provide some good details for me. I really appreciate a man like you!!
Pat
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Quoting - lpatricksom
Your mention of the file libstdc++.so.6 instead of libstdc++.so.5 being installed in some installations fit my OpenSuSE-11.1 installation. So the link command you mentioned was appropriate to I suppose force the file libstdc++.so.6 to be used when the Intel Fortran Compiler Professional Edition for Linux (IFCPEL) 11.1 would be calling for libstdc++.so.5 in a working installation of IFCPEL 11.1.
...
Among the messages displayed during that unpacking I saw the path /l_cprof_p_11.1.046/pset/32e/gcc-3.2/libstdc++.so.5 displayed minus the leading "/". So apparently the IFCPEL 11.1 was written for at least i) gcc 3.2 and glibc 3.2, assuming the version numbers for gcc and glibc are supposed to be the same, and ii) libstdc++.so.5.
"-- Host machine does not support Intel Streaming SIMD 2 Extensions."--That would be Streaming Single Instruction Multiple Data 2 Extensions, or SSE2.
...
Among the messages displayed during that unpacking I saw the path /l_cprof_p_11.1.046/pset/32e/gcc-3.2/libstdc++.so.5 displayed minus the leading "/". So apparently the IFCPEL 11.1 was written for at least i) gcc 3.2 and glibc 3.2, assuming the version numbers for gcc and glibc are supposed to be the same, and ii) libstdc++.so.5.
"-- Host machine does not support Intel Streaming SIMD 2 Extensions."--That would be Streaming Single Instruction Multiple Data 2 Extensions, or SSE2.
I don't believe the gcc-3.2 supplied with ifort plays any role on a system like yours which has a more up to date version of gcc. There is no such thing as glibc-3.2. The glibc-2.9 provided by SuSE is more up to date than any which were tested during ifort 11.1 development.
Sorry Ron and I missed the point about how ifort 11.0 and newer are intended to run only on SSE2 CPUs, even though there is the option to generate non-SSE 32-bit code. You may have to download and install ifort 10.1 or 9.1 to avoid this problem, if your CPU is older than Athlon-64 or Turion X2. Then you may have to install the older g++-3.x which you could get from YOU mirror and make it active when using ifort.
I ran OpenSuSE 10.3 on my laptop until my employer locked it down to Windows only; that version also may be a useful option for you. There aren't known compatibilities between older versions of ifort and current versions of glibc; it's only that there was no possibility of testing the combinations.
Check the gfortran documentation; there is a switch -fcray-pointer. Besides, current gfortran and ifort support iso_c_interop which provides a portable replacement for Cray pointers.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks, Tim18, especially for mentioning the -fcray-pointer option in gfortran. Given that, even though I haven't tried to use Cray pointers in a Fortran program compiled with gfortran, gfortran becomes the second Fortran compiler of which I am aware can be downloaded free from the Internet which can handle Cray-style pointers. This assumes that the current version of the Intel Fortran Compiler Professional Edition for Linux 11.1 can handle Cray-style pointers, as the Intel Fortran Compiler 8.1 (or so) for Linux could.
Pat
Pat
Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page