Re: How to compile/link Fortran for 'portable' executable to down-level OVMS?
From: Paddy O'Brien (paddy.o'brien_at_tg.nsw.gov.au)
Date: 06/10/03
- Next message: Bob Ceculski: "Re: Firewall for VMS / TRU64"
- Previous message: Craig A. Berry: "Re: VMS SQL client"
- Maybe in reply to: rlfitch: "How to compile/link Fortran for 'portable' executable to down-level OVMS?"
- Next in thread: jlsue: "Re: How to compile/link Fortran for 'portable' executable to down-level OVMS?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Tue, 10 Jun 2003 09:25:02 +1000
Ronald Milen wrote:
> Hi,
>
> OpenVMS, like most OS, is not backward compatible. There is a chance (I
> haven't tried it) that a program compiled and linked on V7.2 will run on
> V6.2, but most likely it won't. Your best bet would be to adhere to compile
> & link it under V6.2.
>
> Ron Milen
> milenronald@yahoo.com
>
> "rlfitch" <rlfitch@peakpeak.com> wrote in message
> news:000d01c32e09$e6770910$0100a8c0@pj...
>
>>Need help in creating a 'portable' executable where the program
>>development is in Fortran on OVMS 7.2 with F90 compiler and then port
>>(copy) the executable to OVMS 6.2 that has F77 compiler. I believe that
>>the key is in the linking (rather than in the compile) but not sure.
>>
>>Thanks,
>>Ransom Fitch
>>
>
>
O.K., I too am not in a position to try this as all my machines are at
v7.2. However, I would just like to make a few comments.
Firstly, I would think that the version of FORRTL may be more important
than the linker version. I remember when I did try this some while ago
I had an error something like FIXUPERR on the run time library. Have a
look at $ help/message fixuperr for full info which points to problems
with shareable images.
Secondly, I assume that the v6.2 machine is also an Alpha so why don't
you have the F90 compiler there too? What version of Fortran do you
have -- the current is v7.5? Later versions of Fortran do require a
more uptodate version of the OS, and IIRC the past two Fortran versions
required a minimum of VMS 7.1.
What you seem to need is not a portable executable, but portable source
code, since you do have a compiler on the other machine. If you are
stuck with only a F77 compiler (and if the other machine is a VAX, you
will be), then you will have to forego the whizz-bang features of
F90/F95 and write in the compatible subset of F95 which is F77 (but
you've still got a few DEC extensions that became part of the later
standard).
Regards, Paddy
***********************************************************************
"This electronic message and any attachments may contain privileged
and confidential information intended only for the use of the
addressees named above. If you are not the intended recipient of
this email, please delete the message and any attachment and advise
the sender. You are hereby notified that any use, dissemination,
distribution, reproduction of this email is prohibited.
If you have received the email in error, please notify TransGrid
immediately. Any views expressed in this email are those of the
individual sender except where the sender expressly and with
authority states them to be the views of TransGrid. TransGrid uses
virus scanning software but excludes any liability for viruses
contained in any attachment.
Please note the email address for TransGrid personnel is now
firstname.lastname@transgrid.com.au"
***********************************************************************
- Next message: Bob Ceculski: "Re: Firewall for VMS / TRU64"
- Previous message: Craig A. Berry: "Re: VMS SQL client"
- Maybe in reply to: rlfitch: "How to compile/link Fortran for 'portable' executable to down-level OVMS?"
- Next in thread: jlsue: "Re: How to compile/link Fortran for 'portable' executable to down-level OVMS?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
