We have installed Open64 220.127.116.11 and 4.5.1 on an HP X9000 system, with a 64-bit filesystem (64-bit inodes), and have found that it does not work in either of the following cases:
1) Open64 is installed on the 64-bit file system. Attempts to compile source code (located on local disk, w/32-bit inodes) fail with error message:
gcc: error trying to exec 'cc1': execvp: No such file or directory
If the file tree is copied to local disk (with 32-bit inodes) compilations succed.
2) The source code is located on the 64-bit file system. With a local copy of Open64 and the source code on 64-bit filesystem compilation fails with error message:
cc1: error: test.c: Value too large for defined data type
Copying the source code to local disk (32 bit fs) the same compilation succeeds.
We suspect this is a bug caused by use of 32-bit system calls, or something similar. Since it's dependent on the location of the source code, it makes use of Open64 too cumbersome for our users.
I couldn't find anything about this in the forums or the knowledge base. Is this a known issue, and is there any workaround? If not, may we hope it might get fixed in an upcoming release?