This web mail archive is frozen.
This page is part of a frozen web archive of this mailing list.
You can still navigate around this archive, but know that no new mails
have been added to it since July of 2016.
Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.
On Feb 28, 2013, at 12:04 PM, Pavel Mezentsev <pavel.mezentsev_at_[hidden]> wrote:
> Do you mean the logs from failed attempts? They are enclosed. If you need the successful logs I'll need to make them again since the files from successful builds are deleted.
You guessed right; I need the logs from the failed builds.
It looks like your openf95 compiler is generating borked executables:
configure:31019: checking KIND value of Fortran C_SIGNED_CHAR
configure:31046: openf95 -o conftest conftest.f90 >&5
configure:31046: $? = 0
./configure: line 4343: 1234 Illegal instruction (core dumped) ./conftest$ac_exeext
configure:31046: $? = 132
configure: program exited with status 132
configure: failed program was:
| program main
| use, intrinsic :: ISO_C_BINDING
| open(unit = 7, file = "conftest.out")
| write(7, *) C_SIGNED_CHAR
There's no reason the above Fortran program should fail with "illegal instruction".
> I am not using MXM. The results with the option you suggested are the same as before:
We're investigating the latency issue.
For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/