- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi, I have just intalled ifort into Mac 10.6.8. But there exists one problem.
The home directory of the machine is under NFS.
When I try "ifort -v" on local directoy, it goes well.
However, if try it on NFS directroy, following error appears.
No enough memory when malloc -1 bytes at shared/flexlm/api/flexlm.c:6802Abort trap
Could you please teach me how I can fix it.
Link Copied
14 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
can you tell me please which compiler version you're using: What does
$ ifort -V
print? (provided you're running it on a local working directory)
Thank you & best regards,
Georg Zitzlsberger
can you tell me please which compiler version you're using: What does
$ ifort -V
print? (provided you're running it on a local working directory)
Thank you & best regards,
Georg Zitzlsberger
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello, Georg.
Here is the result
Intel Fortran Intel 64 Compiler XE for applications running on Intel 64, Version 12.1.2.269 Build 20111207Copyright (C) 1985-2011 Intel Corporation. All rights reserved.30 DAY EVALUATION LICENSEifort: NOTE: The evaluation period for this product ends on 16-mar-2012 UTC.
Thank you in advance.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The file paths on the NFS client must match the file paths on the host. Also, the NFS server host, you should have installed the compiler directly to the NFS directory. You cannot copy or move the compiler - it must be installed directly to a directory and should not be moved.
In what directory path (full path from root / ) does the server have the compiler?
In what directory path (full path from root / ) does the client have the compiler?
On the client system, did you copy the license to /Users/Shared/Library/Application Support/Intel/Licenses/*.lic ?
Also, the client has to do command 'source/bin/compilervars.sh intel64'
In what directory path (full path from root / ) does the server have the compiler?
In what directory path (full path from root / ) does the client have the compiler?
On the client system, did you copy the license to /Users/Shared/Library/Application Support/Intel/Licenses/*.lic ?
Also, the client has to do command 'source
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
NFS server is Linux, and client is Mac OS.
Are you suggesting that NFS server must have fortran composer for linux?
But, I also have linux machine of NFS client. I installed ifort into linux client and it goes well.
NFS Server : linux with no compiler
|
|--NFS client : linux with compiler -> OK
|
|--NFS client : Mac with compiler -> NG
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
unfortunately I need one more information from you: Which XCode version are you using?
Our engineers need to know to reproduce the problem.
Edit:
Could you please try a workaround:
$ export INTEL_LICENSE_FILE=.lic
...and try again?
Thank you & best regards,
Georg Zitzlsberger
unfortunately I need one more information from you: Which XCode version are you using?
Our engineers need to know to reproduce the problem.
Edit:
Could you please try a workaround:
$ export INTEL_LICENSE_FILE=
...and try again?
Thank you & best regards,
Georg Zitzlsberger
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
The version of Xcode is 3.2.6.
And,
$ export INTEL_LICENSE_FILE=.lic
did not work.
Thank you in advance.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
you can use a linux NFS server host.
Mount NFS on Mac client #1
Client #1 must have Xcode 3.2.6 installed locally
Install Intel Fortran for Mac OS X to that NFS path from the client. you cannot install in one place and copy to NFS. You cannot move the compiler with cp, tar, etc.
confirm compiler works on client #1 where you did the installation.
Next client: install Xcode 3.2.6. should be 64bit just like client #1
Move license from client #1 to /Users/Shared/Library/Application Support/Intel/Licenses/* to same location on client #2. check permissions so that users can read this full path to .lic file(s).
Mount NFS on same path on client #2 as on client #1
source/bin/compilervars.sh intel64
ifort -V
Mount NFS on Mac client #1
Client #1 must have Xcode 3.2.6 installed locally
Install Intel Fortran for Mac OS X to that NFS path from the client. you cannot install in one place and copy to NFS. You cannot move the compiler with cp, tar, etc.
confirm compiler works on client #1 where you did the installation.
Next client: install Xcode 3.2.6. should be 64bit just like client #1
Move license from client #1 to /Users/Shared/Library/Application Support/Intel/Licenses/* to same location on client #2. check permissions so that users can read this full path to .lic file(s).
Mount NFS on same path on client #2 as on client #1
source
ifort -V
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am sorry, it seems that my explanation is not enought.
I have two nfs clients, Mac and Linux.Linux runs compiler without a problem.
Mac runs compiler only in local directry.
I guess you are mistaking that I have two Mac clients, one runs correctly and the other doesn't.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
If the Mac sees the linux compiler installation on the NFS mount, that compiler won't work under MacOS.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
based on Tim's concern: Do you really have two dedicated installations (Mac OS* X & Linux*) with two different and suitable licenses? Using the Mac OS* X compiler with a Linux* version won't work either.
Best regards,
Georg Zitzlsberger
based on Tim's concern: Do you really have two dedicated installations (Mac OS* X & Linux*) with two different and suitable licenses? Using the Mac OS* X compiler with a Linux* version won't work either.
Best regards,
Georg Zitzlsberger
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Sorry to be late reply.
I figured out something.
I have mounted the NFS to /home/xxx of the Mac.
When I changed the mount point to /tmp, then the error was disappeared.
Do you have any idea why /home/xxx makes the error?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Sorry to be late reply. I figured out something. I have mounted the NFS to /home/xxx of the Mac. When I changed the mount point to /tmp, then the error was disappeared. Do you have any idea why /home/xxx makes the error? |
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
this should be a public update on the problem because sanukisoba and I had a private conversion. It turned out that an old license file was used. Thus, if others are seeing the same symptoms, please check that you've stored a valid and non-expired license file in /Users/Shared/Library/Application Support/Intel/Licenses/.
I admit that the error shown does not help in finding the root cause being an invalid/expired license file. Hence I've submitted a defect ticket to improve this in the future (DPD200275662).
Best regards,
Georg Zitzlsberger
this should be a public update on the problem because sanukisoba and I had a private conversion. It turned out that an old license file was used. Thus, if others are seeing the same symptoms, please check that you've stored a valid and non-expired license file in /Users/Shared/Library/Application Support/Intel/Licenses/.
I admit that the error shown does not help in finding the root cause being an invalid/expired license file. Hence I've submitted a defect ticket to improve this in the future (DPD200275662).
Best regards,
Georg Zitzlsberger
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
the problem with the incorrect allocation and misleading error message (DPD200275662) has been fixed for Intel Composer XE 2011 Update 12 and higher.
Best regards,
Georg Zitzlsberger
the problem with the incorrect allocation and misleading error message (DPD200275662) has been fixed for Intel Composer XE 2011 Update 12 and higher.
Best regards,
Georg Zitzlsberger

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