🚀 go-pugleaf

In article <lpaF02tvI.5Aw@netcom.com> lpa@netcom.com (Pierre Asselin) writes:
>metzler@oddjob.uchicago.edu (Chris Metzler) writes:
>
>>Anyway, I can use any help I can get.  I'm on a Red Hat Linux machine.
>>It doesn't have full g77 installed -- f77 or g77 invokes an f2c
>>preprocessor, followed by gcc.  Fortran programs compiled this way
>>don't seem to be able to read Fortran unformatted binary files.
>
>Hem, I don't know that Fortran unformatted files were ever meant to be
>portable across different platforms.

I don't know whether they were meant to or not; but I've had no
problems with portability for 14 years, which was why I was surprised
here.

>  It doesn't help that you don't
>tell us what your "other machine" is.

Sorry; brain fart on my part.  i686.

Anyway, your explanation made perfect sense.

I fetched a converter from a Linux software archive, and my problem
went away.  I was hoping, though, that some sort of compiler option
could *force* the file reads/writes to be done in the opposite way.
The Fortran program I'm really porting over here writes hundreds of
14 MB files every time it runs (and I run it constantly); and I
use a large number of different platforms at the same time, basically
wherever I can get CPU cycles.  It would be nice if external conversion
wasn't necessary.  But if it is, it is.

Anyway, thanks for cluing me in re: unformatted file strucutre.

-c


-- 
Chris Metzler                   Work Address:   Theoretical Astrophysics
630-840-3662 (office)                           Fermi National Accelerator Lab
metzler@oddjob.uchicago.edu (play)              P.O. Box 500, MS-209
cmetzler@spam-me-not.fnal.gov (work)            Batavia, IL  60510 USA

"As a child I understood how to give; I have forgotten this grace since I
have become civilized." - Chief Luther Standing Bear