Mailing Lists: Apple Mailing Lists
Image of Mac OS face in stamp
 
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Extra bytes in OSX vs classic binaries

On Jun 25, 2004, at 5:47 PM, Joe Koski wrote:

Please excuse me for piggy-backing, but I have a similar issue for which
list members may know the answer.

I have a Fortran 77 code that I compile with g77-3.5. The program can write
binary output files for reading by a post-processor (GMV). The
post-processor is C code, probably compiled with gcc. Apparently the g77
binary file format differs from the gcc binary file format as described in
this thread. As a result the C language post-processor can't read the g77
binary output, and I'm forced to use ASCII instead. As far as I know, the
post-processor won't read .hdf files, either.

My question: are there compiler switches for g77 that will allow the g77
binary output files to be compatible with gcc, similar to the -N3 Absoft
option described below? Any tricks? How about running the particular g77
output routine through f2c and then compiling it with gcc?

One option is to write the data to a fortran direct access file, with a record length of 1. This is basically the same as writing in C. No extra record information will appear in the file, only the data you write.

Drew

---------------------------------------------------------
Drew McCormack

www.maniacalextent.com
_______________________________________________
fortran-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/fortran-dev
Do not post admin requests to the list. They will be ignored.

References: 
 >Re: Extra bytes in OSX vs classic binaries (From: Joe Koski <email@hidden>)



Visit the Apple Store online or at retail locations.
1-800-MY-APPLE

Contact Apple | Terms of Use | Privacy Policy

Copyright © 2007 Apple Inc. All rights reserved.