Fortran compiler suitable for Apple AND Windows?
Terence
quality DOS and Windows--running computers and presented me with a
MacPro Professional, with Windows 2000 loaded under simulation.
After facing the grief of an entirely new user interface to learn,
what do Forum members recommend for me, to aquire a trustable Fortran
compiler, with which I can continue to compile my (F77) code and have
it run on Apple AND Windows systems (even if two versions are
needed)?
I note that the Apple MAC is really based on an Intel chip and nVidia
graphics and happily runs my DOS code under the VMware Fusion
application.
( Here I inteject to note that I had to eliminate some Fx key
shortcuts and write new ASM software to get real Funtion keys, and ALT-
arrow simulations of the "missing" Home, End, Page up, Page down and
control-arrow keys. Unfortunately there is no Delete function as "we"
know it, but a "Delete"-labelled backspace erasing key that starts in
the "wrong" place, and there is no insert key; that makes running
good old software a little difficult. But the kludge works).
So: Fortran compilers to run on Apple MAC (or Windows simulation) with
target systems of native Apple MAC and Windows 2000 or V7?
(Not really happy with XP; and Vista is Dodo-bound).
Richard Maine
> My kids draggged me screaming away from my roomful of faithful museum-
> quality DOS and Windows--running computers and presented me with a
> MacPro Professional, with Windows 2000 loaded under simulation.
Fancy gift. Makes me feel cheap because I only bought my (80-year-old)
Mom a 20" iMac (and a reconditioned one at that). I looked at the 24"
ones, but my son commented that my mother wouldn't be doing anything
that would make good use of the extra size. One of my brothers had
"tasked" me with getting mom a new computer after dad died. I'm sure he
expected me to come back with a cheap Windows box (but not as cheap as
the old eMachines one dad had been clinging to). I got her the iMac
instead, which has pleased her, except that she thinks I spent way to
much on it for her; I think I have yet a long way to go before we are
"even."
> After facing the grief of an entirely new user interface to learn,
> what do Forum members recommend for me, to aquire a trustable Fortran
> compiler, with which I can continue to compile my (F77) code and have
> it run on Apple AND Windows systems (even if two versions are
> needed)?
> I note that the Apple MAC is really based on an Intel chip and nVidia
> graphics and happily runs my DOS code under the VMware Fusion
> application.
Yes. For a start, any compiler that you could otherwise run on Windows
2000 or Windows 7, you ought to still be able to run on them under
VMWare. I can't comment constructively on compatibility between the
different Windows versions, but I can tell you that you don't need
anything special for Windows under VMWare than for the same version of
Windows on any other Windows box. Heck, though I haven't tried it, I
think it is supposed to be possible to run DOS under VMWare if you
really want. One nice thing about the Mac with VMWare is that you have a
lot of choices that don't have to exclude each other.
> So: Fortran compilers to run on Apple MAC (or Windows simulation) with
> target systems of native Apple MAC and Windows 2000 or V7?
> (Not really happy with XP; and Vista is Dodo-bound).
For the Windows side, see above for general comments. I'll defer more
specific recommendations to others.
For the native Mac side, there are also quite a few choices. G95 and
GFortran are free (in both senses) and have versions for both Mac and
Windows. Intel Fortran isn't free, but it also has Mac and Windows
versions. Likewise for Nag, Absoft, and PGI.
--
Richard Maine | Good judgment comes from experience;
email: last name at domain . net | experience comes from bad judgment.
domain: summertriangle | -- Mark Twain
Gordon Sande
> My kids draggged me screaming away from my roomful of faithful museum-
> quality DOS and Windows--running computers and presented me with a
> MacPro Professional, with Windows 2000 loaded under simulation.
Must be a new model as it does not match the factory descriptions.
Apple claims to sell a model called the Mac Pro in either Quad-Core
or 8-Core variants.
> After facing the grief of an entirely new user interface to learn,
> what do Forum members recommend for me, to aquire a trustable Fortran
> compiler, with which I can continue to compile my (F77) code and have
> it run on Apple AND Windows systems (even if two versions are
> needed)?
>
> I note that the Apple MAC is really based on an Intel chip and nVidia
> graphics and happily runs my DOS code under the VMware Fusion
> application.
> ( Here I inteject to note that I had to eliminate some Fx key
> shortcuts and write new ASM software to get real Funtion keys, and ALT-
> arrow simulations of the "missing" Home, End, Page up, Page down and
> control-arrow keys. Unfortunately there is no Delete function as "we"
> know it, but a "Delete"-labelled backspace erasing key that starts in
> the "wrong" place, and there is no insert key; that makes running
> good old software a little difficult. But the kludge works).
You could have used the Apple supplied device drivers under BootCamp to
run Windows natively without the layer of MacOsX so you could preserve
more of your museum look and feel. Without all the extra software layers
the keyboard might work as intended. But that takes away the adventure
aspects.
> So: Fortran compilers to run on Apple MAC (or Windows simulation) with
> target systems of native Apple MAC and Windows 2000 or V7?
> (Not really happy with XP; and Vista is Dodo-bound).
Any of Absoft, NAG or Intel offer separate versions of their compilers for
MacOsX and Windows. There are also the GNU siblings of G95 and Gfortran
which come in both variants. For a total of five potential vendors. Depends
of which attributes float your boat. If you are up to your ears in extensions
there may be no vendor that meets your needs.
A sensible scheme is to have two compilers of different charactistics. One
for good debugging and one for good optimizations. One to be strict as possible
and one to tolerate no end of foolishness (which the first will make go away!).
NAG is both very strict and very good at debugging. The others list extensions
all over the place and have differing quality of optimizations.
Tim Prince
>
> You could have used the Apple supplied device drivers under BootCamp to
> run Windows natively without the layer of MacOsX so you could preserve
> more of your museum look and feel. Without all the extra software layers
> the keyboard might work as intended. But that takes away the adventure
> aspects.
>
>
A (possibly minor) drawback of bootcamp is the lack of driver support
for many Windows versions. So, your favorite Windows version (if not
specifically called out as having driver support) likely will not find
network connections. It should still run the Windows compilers. For
some of us, ability to test Windows x64 .exe and still have network
connections might be important.
--
Tim Prince
Richard Maine
Are there Windows versions that are supported with bootcamp, but don't
have working network connections? My experience lacks breadth in that
regard, but my XP (32-bit) bootcamp system sees the network just fine on
this 4-month-old 27" iMac. It also worked find on the 3-year-old one
that this displaced.
BootCamp doesn't support a whole lot of Windows versions, though.
Quickly checking Apple's support pages, I see that it doesn't support
64-bit XP at all. So if you are talking x64 .exes, I guess that must be
either Vista or Windows 7, neither of which I have even token experience
with - never so much as touched a keyboard or mouse on a system running
them. Bootcamp supports those only on pretty recent systems. Are you
saying that one of those doesn't have working network drivers in
bootCamp?
I'd think a bigger factor would be that bootCamp might not support your
favorite Windows version at all. In particular, if you are looking for
x64 support and don't have one of the machines listed as supporting
that, then you'd have a problem. I suppose that perhaps lack of the
needed drivers might be exactly why Apple doesn't support some
combinations.
P.S. Another possibility for keyboard unhappiness is to use a 3rd party
keyboard. I haven't done so, but most/all? USB keyboards ought to work.
I do use 3rd party mice (well, trackballs).
George White
> My kids draggged me screaming away from my roomful of faithful museum-
> quality DOS and Windows--running computers and presented me with a
> MacPro Professional, with Windows 2000 loaded under simulation.
>
> After facing the grief of an entirely new user interface to learn,
> what do Forum members recommend for me, to aquire a trustable Fortran
> compiler, with which I can continue to compile my (F77) code and have
> it run on Apple AND Windows systems (even if two versions are
> needed)?
Don't be afraid to use a Fortran 9x or 200x compiler unless you rely
heavily on some vendor-specific extensions to f77 or specific layout of
common blocks in memory the changes should be minor. For legacy f77
code I see current compiler standards as just cleaning up gratuitous
vendor-specific differences.
Gfortran is pretty solid and the price is right. At work we use a large
NASA application that has required commercial compilers for the past 13
years but is now working with gfortran-4.5. Some things are faster with
the commercial compilers, but overall gfortran is only slightly slower.
Installing free fortran on Windows has been a bit of a headache as it
relies on tools that you don't normally find on Windows. These days I
just install Octave, which includes a fortran compiler.
For Apple, there have been way too many buggy builds of gfortran, but
the R-project's Apple people provide a reliable build of gfortran-4.2.
Windows 2000 is about to reach "end of life" and already new versions
of some apps have dropped Win2K support, so you may find your options
limited.
> I note that the Apple MAC is really based on an Intel chip and nVidia
> graphics and happily runs my DOS code under the VMware Fusion
> application.
> ( Here I inteject to note that I had to eliminate some Fx key
> shortcuts and write new ASM software to get real Funtion keys, and ALT-
> arrow simulations of the "missing" Home, End, Page up, Page down and
> control-arrow keys. Unfortunately there is no Delete function as "we"
> know it, but a "Delete"-labelled backspace erasing key that starts in
> the "wrong" place, and there is no insert key; that makes running
> good old software a little difficult. But the kludge works).
>
> So: Fortran compilers to run on Apple MAC (or Windows simulation) with
> target systems of native Apple MAC and Windows 2000 or V7?
> (Not really happy with XP; and Vista is Dodo-bound).
--
George White <aa...@chebucto.ns.ca> <gn...@acm.org>
189 Parklea Dr., Head of St. Margarets Bay, Nova Scotia B3Z 2G6
Tim Prince
>
> BootCamp doesn't support a whole lot of Windows versions, though.
> Quickly checking Apple's support pages, I see that it doesn't support
> 64-bit XP at all. So if you are talking x64 .exes, I guess that must be
> either Vista or Windows 7, neither of which I have even token experience
> with - never so much as touched a keyboard or mouse on a system running
> them. Bootcamp supports those only on pretty recent systems. Are you
> saying that one of those doesn't have working network drivers in
> bootCamp?
>
> I'd think a bigger factor would be that bootCamp might not support your
> favorite Windows version at all. In particular, if you are looking for
> x64 support and don't have one of the machines listed as supporting
> that, then you'd have a problem. I suppose that perhaps lack of the
> needed drivers might be exactly why Apple doesn't support some
> combinations.
>
> P.S. Another possibility for keyboard unhappiness is to use a 3rd party
> keyboard. I haven't done so, but most/all? USB keyboards ought to work.
> I do use 3rd party mice (well, trackballs).
>
We installed Windows 7 X64 with reasonable success under bootcamp on a
new Mac 2 months ago. As you say, Apple made no mention of supporting
it. Win-7 home premium doesn't support LAN connection, while bootcamp
didn't provide wireless support for win-x64. We looked every which way.
Win-7 Pro and above support a LAN connection, and that did work in
bootcamp.
I don't spend enough time running an IPod to be proficient on the Mac
mouse pad or whatever it's called.
--
Tim Prince
Terence
I tried my old F77 compiler and it runs OK.
I tried several ancient DOS programs an all worked except when page up
or down were needed (not on MAC), and the alternative ctl-up and ctl-
down arrows gave no response at all!
I tried using a keyboard test program that was compiled with MS F77
V3.31, that itself call a standard dos service call to read an
extended keyboard as two byte scancodes.
The result is strange.
All keystrokes that would be expected to produce a character code plus
a key number do so.
But the Function keys is all shift combinations yield results with a
half-second pause.
The unshifted arrow keys give a normal response.
But the ctl and alt key combinations of the arrow keys return codes
after a 5 second pause!
I tried a Fotran program that used both Int 16h with 16H in AH, and a
read string (Int 10 with #0902 in AH), as two different input
keystroke methods.
Same result.
I then tried the MS EDIT program and used arrow keys to navigate.
Response speed was normal, but this uses no extended keyboard keys.
I gather there must be a problem with getting the extended keyboard
codes and somewhere a time-out is built in, in the emulator.
And I was trying to move on...
Gordon Sande
> My Mac is a MacBook Pro, it says here).
> I tried my old F77 compiler and it runs OK.
> I tried several ancient DOS programs an all worked except when page up
> or down were needed (not on MAC), and the alternative ctl-up and ctl-
> down arrows gave no response at all!
The absence of page-up and page-down is more associated with it being
a laptop than its being a Mac. The mini keyboards on laptops all look a
lot alike so PC laptops would have similar problems. Full size Mac
keyboards look a lot like other full size keyboards back to the days of
VT100s with both a numerical pad and cursor and function cluster. Many
laptops support using a full sized leyboard through an i/o port. These
external keyboards are both Mac abd PC comapatible. Most laptops even
support an auxilary monitor to become replacements for a desktop.
Macs normally run MacOsX and not DOS. So you must be using an PC emulator
as you tell us at the end. There are three of them! You forgot to say which
one. In any case they all have their own sources of support for a problem
which is not a Fortran problem. You will almost certainly have better luck
asking is a place concerned with whichever emulator you are using. They
may even know the their way of emulating the keys missing from a full size
key board. Common ways are a multi finger salute or a sequence of keys. For
all I know they may even offer choices of which method or combination of keys.
The other way would be to ask the support folks who handle MS F77.
user1
>
> And I was trying to move on...
Still using a 16bit DOS based compiler and old fashioned DOS interrupts.
Time to move on indeed.
Richard Maine
> On 2010-03-11 06:32:13 -0400, Terence <tbwr...@cantv.net> said:
>
> > My Mac is a MacBook Pro, it says here).
...
> The absence of page-up and page-down is more associated with it being
> a laptop than its being a Mac.
Yeah. In my prior post, I misguessed the system he was talking about.
The Mac system names can be confusing, as I well know. (Not that Apple
is at all unique in that regard). In particular, a Mac Pro is a *VERY*
different system from a MacBook Pro. That "book" part of the name is
more important than it might look. (A MacBook Pro is also a nice system
- just not what I had been thinking was meant.)
So my prior comments about 3rd party keyboards are less relevant. Do
note though that you can attach a USB keyboard to a Mac laptop. I used
to do so all the time at NASA when I was using a (much older) Mac laptop
as my desktop. It does mean that when you take the laptop on a trip, you
are suddenly having to deal with the keyboard differences if you were
used to using an external keyboard when the laptop was an your desk.