Prev: Calling DLL subroutine from C++
Next: Can command characters actions be disabled in modern compilers ?
From: Tobias Burnus on 30 Mar 2010 03:05
chengiz wrote:
> On Mar 29, 7:19 pm, nos...(a)see.signature (Richard Maine) wrote:
>> chengiz <chen...(a)my-deja.com> wrote:
>>>> There must be more F2003 stuff than just the read statement. POS= is
>>>> for files connected for stream access and stream is a F2003 new feature.
>>>> Check the open statements for the f and see what is going on there.
[...]
> The compiler version (f95 --version)
> GNU Fortran (GCC) 4.1.2 20071124 (Red Hat 4.1.2-42)

gfortran has stream access since 4.2.0, which was released 2007-05-13,
cf. http://gcc.gnu.org/gcc-4.2/changes.html

Possibly, Red Hat's GCC contains some patches from the experimental
version, which give some half-complete stream access.

Note that GCC 4.1 and 4.2 are no longer supported; currently supported
are: 4.3 (previous stable), 4.4 (stable) and 4.5 (should be released
rather soon, presumably within the next two weeks).

If you have the choice, I would use 4.4 (or 4.5) as 4.3 will be out of
maintenance after 4.5 is released. Besides, at least for Fortran, 4.4
and 4.5 contain many fixes and should thus be stabler. (Assuming, no
nasty, unreported, unfixed bug creped in after 4.3.)

See also http://gcc.gnu.org/wiki/GFortranBinaries

Tobias
From: chengiz on 30 Mar 2010 10:54

>
> gfortran has stream access since 4.2.0, which was released 2007-05-13,
> cf.http://gcc.gnu.org/gcc-4.2/changes.html
>
> Possibly, Red Hat's GCC contains some patches from the experimental
> version, which give some half-complete stream access.
>
> Note that GCC 4.1 and 4.2 are no longer supported; currently supported
> are: 4.3 (previous stable), 4.4 (stable) and 4.5 (should be released
> rather soon, presumably within the next two weeks).
>
> If you have the choice, I would use 4.4 (or 4.5) as 4.3 will be out of
> maintenance after 4.5 is released. Besides, at least for Fortran, 4.4
> and 4.5 contain many fixes and should thus be stabler. (Assuming, no
> nasty, unreported, unfixed bug creped in after 4.3.)
>
> See alsohttp://gcc.gnu.org/wiki/GFortranBinaries
>
> Tobias

Tobias,
You are probably right about the half-complete stream access, because
the configuration for the software set the HAVE_STREAM macro. One'd
think that line would have this macro around it but it didnt. I
disabled that macro, put it around that line, but the code has some
weird compiler errors elsewhere that seem to be gcc's fault and they
seem to have fixed it in a newer release, so I dont have any option
but to upgrade the compilers.

Also, yes I put in foo and var as aliases for the actual names. I'd
have thought it'd be obvious, but I was wrong and I apologize.

chengiz

From: chengiz on 30 Mar 2010 12:45
On Mar 30, 3:05 am, Tobias Burnus <bur...(a)net-b.de> wrote:
> chengiz wrote:
> > On Mar 29, 7:19 pm, nos...(a)see.signature (Richard Maine) wrote:
> >> chengiz <chen...(a)my-deja.com> wrote:
> >>>> There must be more F2003 stuff than just the read statement. POS= is
> >>>> for files connected for stream access and stream is a F2003 new feature.
> >>>> Check the open statements for the f and see what is going on there.
> [...]
> > The compiler version (f95 --version)
> > GNU Fortran (GCC) 4.1.2 20071124 (Red Hat 4.1.2-42)
>
> gfortran has stream access since 4.2.0, which was released 2007-05-13,
> cf.http://gcc.gnu.org/gcc-4.2/changes.html
>
> Possibly, Red Hat's GCC contains some patches from the experimental
> version, which give some half-complete stream access.
>
> Note that GCC 4.1 and 4.2 are no longer supported; currently supported
> are: 4.3 (previous stable), 4.4 (stable) and 4.5 (should be released
> rather soon, presumably within the next two weeks).
>
> If you have the choice, I would use 4.4 (or 4.5) as 4.3 will be out of
> maintenance after 4.5 is released. Besides, at least for Fortran, 4.4
> and 4.5 contain many fixes and should thus be stabler. (Assuming, no
> nasty, unreported, unfixed bug creped in after 4.3.)
>
> See alsohttp://gcc.gnu.org/wiki/GFortranBinaries
>
> Tobias


Tried installing those binaries. They depend on glibc_2.11 but the
page doesnt mention that. It appears the path to /lib64/libc.so.6 is
hardcoded in the binaries and I definitely cant change anything in /.
Do I need to build from source then?
chengiz
From: Craig Powers on 30 Mar 2010 14:40
chengiz wrote:
> On Mar 30, 3:05 am, Tobias Burnus <bur...(a)net-b.de> wrote:
>> chengiz wrote:
>>> On Mar 29, 7:19 pm, nos...(a)see.signature (Richard Maine) wrote:
>>>> chengiz <chen...(a)my-deja.com> wrote:
>>>>>> There must be more F2003 stuff than just the read statement. POS= is
>>>>>> for files connected for stream access and stream is a F2003 new feature.
>>>>>> Check the open statements for the f and see what is going on there.
>> [...]
>>> The compiler version (f95 --version)
>>> GNU Fortran (GCC) 4.1.2 20071124 (Red Hat 4.1.2-42)
>> gfortran has stream access since 4.2.0, which was released 2007-05-13,
>> cf.http://gcc.gnu.org/gcc-4.2/changes.html
>>
>> Possibly, Red Hat's GCC contains some patches from the experimental
>> version, which give some half-complete stream access.
>>
>> Note that GCC 4.1 and 4.2 are no longer supported; currently supported
>> are: 4.3 (previous stable), 4.4 (stable) and 4.5 (should be released
>> rather soon, presumably within the next two weeks).
>>
>> If you have the choice, I would use 4.4 (or 4.5) as 4.3 will be out of
>> maintenance after 4.5 is released. Besides, at least for Fortran, 4.4
>> and 4.5 contain many fixes and should thus be stabler. (Assuming, no
>> nasty, unreported, unfixed bug creped in after 4.3.)
>>
>> See alsohttp://gcc.gnu.org/wiki/GFortranBinaries
>>
>> Tobias
>
>
> Tried installing those binaries. They depend on glibc_2.11 but the
> page doesnt mention that. It appears the path to /lib64/libc.so.6 is
> hardcoded in the binaries and I definitely cant change anything in /.

glibc is too integrated into the system to fool around with it. If you
try, you're liable to break something seriously (as in, so badly that
you have to reinstall the OS).

> Do I need to build from source then?

Yes. Unfortunately, the pre-built linux binaries require a fairly
recent glibc, which disqualifies them from use on RHEL4 (and maybe even
RHEL5 at this point).
First  |  Prev  | 
Pages: 1 2
Prev: Calling DLL subroutine from C++
Next: Can command characters actions be disabled in modern compilers ?