Home > Archive > Fortran > June 2005 > Tiger OS X 10.4 Big Fortran Problem
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Tiger OS X 10.4 Big Fortran Problem
|
|
|
| Until yesterday I have OS X 10.2 with fortran g77. After the
installation of Tiger and the new dev. kit, g77 doesn't work yet.
Does anyone can help me?
I've tried to reinstall g77 and after also g95 but without success. When
I type G77 or GFORTRAN in terminal: 'command not found' is the answer.
| |
| Madhusudan Singh 2005-05-04, 8:58 pm |
| David wrote:
> Until yesterday I have OS X 10.2 with fortran g77. After the
> installation of Tiger and the new dev. kit, g77 doesn't work yet.
> Does anyone can help me?
>
> I've tried to reinstall g77 and after also g95 but without success. When
> I type G77 or GFORTRAN in terminal: 'command not found' is the answer.
Assuming that Mac OS shell behaves like BSD, what do you get with :
locate g77
and export | grep "PATH"
?
| |
| Richard E Maine 2005-05-04, 8:58 pm |
| In article <4279273f$0$79458$14726298@news.sunsite.dk>,
Madhusudan Singh <spammers-go-here@spam.invalid> wrote:
> David wrote:
>
> Assuming that Mac OS shell behaves like BSD, what do you get with :
>
> locate g77
>
> and export | grep "PATH"
In addition to questions like those, clearly aimed at checking for an
appropriate PATH, I feel obligated to ask whether the OP actually meant
what he said. The reply above seems to "interpret" the OP's question.
Now maybe the interpretation is right; I often find myself answering
what I think was the intended question instead of the one asked. But
just on the off chance that the OP did in fact mean exactly what he
typed...
Try typing g77 and g95 instead of G77 and GFORTRAN. Note two
differences, both important.
1. Case matters. The commands *MUST* be in lower case. If you type them
in upper case, then they won't work (unless you have gone to special
trouble to make that work, but if the OP knew how to do that, he
probably wouldn't be needing to ask questions like this).
2. G95 and gfortran are different compilers - related, but different. If
you really installed g95, then the command gfortran isn't likely to do
anything, even in lower case.
--
Richard Maine | Good judgment comes from experience;
email: my first.last at org.domain | experience comes from bad judgment.
org: nasa, domain: gov | -- Mark Twain
| |
| Dave Seaman 2005-05-05, 3:59 pm |
| On Wed, 04 May 2005 13:11:01 -0700, Richard E Maine wrote:
> In article <4279273f$0$79458$14726298@news.sunsite.dk>,
> Madhusudan Singh <spammers-go-here@spam.invalid> wrote:
[color=darkred]
[color=darkred]
> In addition to questions like those, clearly aimed at checking for an
> appropriate PATH, I feel obligated to ask whether the OP actually meant
> what he said. The reply above seems to "interpret" the OP's question.
> Now maybe the interpretation is right; I often find myself answering
> what I think was the intended question instead of the one asked. But
> just on the off chance that the OP did in fact mean exactly what he
> typed...
> Try typing g77 and g95 instead of G77 and GFORTRAN. Note two
> differences, both important.
> 1. Case matters. The commands *MUST* be in lower case. If you type them
> in upper case, then they won't work (unless you have gone to special
> trouble to make that work, but if the OP knew how to do that, he
> probably wouldn't be needing to ask questions like this).
That's true on most Unix systems, but the OP is asking about Mac
OS X Tiger, which has a case-insensitive file system.
i[gemini:hello] $ ls -l /sw/bin/*77
lrwxr-xr-x 1 root admin 11 May 4 09:24 /sw/bin/f77 -> /sw/bin/g77
-rwxr-xr-x 1 root admin 303672 May 4 09:23 /sw/bin/g77
[gemini:hello] $ which g77
/sw/bin/g77
[gemini:hello] $ which G77
/sw/bin/G77
[gemini:hello] $ G77 hello.f
[gemini:hello] $ a.out
Hello, world!
> 2. G95 and gfortran are different compilers - related, but different. If
> you really installed g95, then the command gfortran isn't likely to do
> anything, even in lower case.
Yes, they are different compilers. I have both.
[gemini:hello] $ which gfortran
/sw/bin/gfortran
[gemini:hello] $ rm a.out
[gemini:hello] $ GFORTRAN hello.f
[gemini:hello] $ a.out
Hello, world!
--
Dave Seaman
Judge Yohn's mistakes revealed in Mumia Abu-Jamal ruling.
<http://www.commoncouragepress.com/i...book&bookid=228>
| |
| Richard E Maine 2005-05-05, 3:59 pm |
| In article <d5d5ml$5ff$1@mailhub227.itcs.purdue.edu>,
Dave Seaman <dseaman@no.such.host> wrote:
> On Wed, 04 May 2005 13:11:01 -0700, Richard E Maine wrote:
[color=darkred]
>
[color=darkred]
> That's true on most Unix systems, but the OP is asking about Mac
> OS X Tiger, which has a case-insensitive file system.
Oops. I'd forgotten about that. I think the Mac way is an improvement
here, by the way. I've also worked on other systems with a similar
scheme - case is preserved when making a file, so you can use mixed-case
names where it helps clarity, but case doesn't have to match when
opening an existing file.
--
Richard Maine | Good judgment comes from experience;
email: my first.last at org.domain | experience comes from bad judgment.
org: nasa, domain: gov | -- Mark Twain
| |
| Ron Shepard 2005-05-05, 3:59 pm |
| In article <d5d5ml$5ff$1@mailhub227.itcs.purdue.edu>,
Dave Seaman <dseaman@no.such.host> wrote:
> That's true on most Unix systems, but the OP is asking about Mac
> OS X Tiger, which has a case-insensitive file system.
Just to be clear, this is not a feature of the operating system, it
is a feature of the HFS+ file system. If you are using a different
filesystem, e.g. ufs or an nfs-mounted remote filesystem, then OS X
behaves the same as any other unix/posix machine. I remember
reading rumors a few months ago that HFS+ was going to have an
option to be case sensitive under 10.4, but I haven't heard anything
about that in the past few days since the release, so I guess it
didn't happen. I've also heard rumors that support for some of the
popular linux filesystems, such as ext3, was going to appear in
10.4, presumably to allow hard drives to be used without
reformatting on several machines or in duel boot situations; if and
when this occurs, then OS X will probably act the same as any other
unix OS on these filesystems.
This feature of OS X has always been a little confusing to me. It
does not act the way that VAX/VMS worked -- with a VAX, which also
had a case-insensitive file system, the files always "appeared" to
be in upper case. You could access them with lower or mixed case,
but you always "knew" that they were sitting there on the disk with
their folded uppercase names. OS X and HFS+ doesn't do it the same
way. For example, if you have a fortran file file.f in one
directory, and a file.F in another directory, then the latter will
be compiled with the preprocessor and the first one will not; that
is, the compiler can tell the difference in the file names and act
accordingly. In this sense, upper and lower case are not treated
the same with OS X. The limitation is that you cannot have both
file.f and file.F in the same directory, and if you try to move or
copy the second file into a directory with the first, it will
overwrite the first file.
$.02 -Ron Shepard
| |
| Alex Gibson 2005-05-05, 3:59 pm |
|
"David" <redboy_xxx@yahoo.it> wrote in message
news:d5b3h9$4n8$1@newsreader.mailgate.org...
> Until yesterday I have OS X 10.2 with fortran g77. After the installation
> of Tiger and the new dev. kit, g77 doesn't work yet.
> Does anyone can help me?
>
> I've tried to reinstall g77 and after also g95 but without success. When I
> type G77 or GFORTRAN in terminal: 'command not found' is the answer.
Apple doesn't have g77 or g95 in its compiler packages.
You will need to reinstall them yourself either manually or using fink
| |
| Gordon Sande 2005-05-05, 3:59 pm |
|
Ron Shepard wrote:
> In article <d5d5ml$5ff$1@mailhub227.itcs.purdue.edu>,
> Dave Seaman <dseaman@no.such.host> wrote:
>
>
>
>
> Just to be clear, this is not a feature of the operating system, it
> is a feature of the HFS+ file system. If you are using a different
> filesystem, e.g. ufs or an nfs-mounted remote filesystem, then OS X
> behaves the same as any other unix/posix machine. I remember
> reading rumors a few months ago that HFS+ was going to have an
> option to be case sensitive under 10.4, but I haven't heard anything
> about that in the past few days since the release, so I guess it
> didn't happen. I've also heard rumors that support for some of the
> popular linux filesystems, such as ext3, was going to appear in
> 10.4, presumably to allow hard drives to be used without
> reformatting on several machines or in duel boot situations; if and
> when this occurs, then OS X will probably act the same as any other
> unix OS on these filesystems.
>
> This feature of OS X has always been a little confusing to me. It
> does not act the way that VAX/VMS worked -- with a VAX, which also
> had a case-insensitive file system, the files always "appeared" to
> be in upper case. You could access them with lower or mixed case,
> but you always "knew" that they were sitting there on the disk with
> their folded uppercase names. OS X and HFS+ doesn't do it the same
> way. For example, if you have a fortran file file.f in one
> directory, and a file.F in another directory, then the latter will
> be compiled with the preprocessor and the first one will not; that
> is, the compiler can tell the difference in the file names and act
> accordingly. In this sense, upper and lower case are not treated
> the same with OS X. The limitation is that you cannot have both
> file.f and file.F in the same directory, and if you try to move or
> copy the second file into a directory with the first, it will
> overwrite the first file.
>
The buzzwords are that Mac HFS+ is case retentive but case insensitive.
So you get it back the way you spelt it but all other variations
on case will match the same name. I have been seeing somethings about
the case sensitive extension to HFS+ which can be used for data volumes
but not the boot volume. I did not pay close attention as it seems
to be directed at the server version, or some other variant which
does not apply to me.
Being case retentive but case insensitive strikes me as a sensible
mode as it leaves the names visually distinctive without the bother of
having Test, test and TEST all be distinct. This confusion is what I
have learned to call "Failing the telephone test" as it makes life
difficult to discuss names over the telephone. F90 passes the
telephone test.
Being case retentive but case insensitive also shows up in some of
the Unix emulators for Windows. MKS being the first example to come
to mind.
> $.02 -Ron Shepard
| |
| Dave Seaman 2005-05-05, 8:58 pm |
| On Fri, 6 May 2005 01:56:24 +1000, Alex Gibson wrote:
> "David" <redboy_xxx@yahoo.it> wrote in message
> news:d5b3h9$4n8$1@newsreader.mailgate.org...
[color=darkred]
> Apple doesn't have g77 or g95 in its compiler packages.
> You will need to reinstall them yourself either manually or using fink
If the OP is already using fink, the thing to do is go to the fink page and
read what it says about upgrading to Tiger.
I updated my g77 and it seems to be fine.
--
Dave Seaman
Judge Yohn's mistakes revealed in Mumia Abu-Jamal ruling.
<http://www.commoncouragepress.com/i...book&bookid=228>
| |
|
| Thanks you all!
I've tried to start g77 in the directory where it was installed and it
worked.
So the simple task is that while upgrading the OS from 10.2.8 to 10.4 my
environment variables were erased.
I re-added /usr/local/bin to .login in /etc and it works.
I have another question.
I have installed (with the new OS X) the new Development Kit (with GCC
4.0) and then reinstalled the OLD g77. After the optimization "g77 -O"
my programs run about 30% faster than the same with the previous OS, do
anyone knows why?
David wrote:
> Until yesterday I have OS X 10.2 with fortran g77. After the
> installation of Tiger and the new dev. kit, g77 doesn't work yet.
> Does anyone can help me?
>
> I've tried to reinstall g77 and after also g95 but without success. When
> I type G77 or GFORTRAN in terminal: 'command not found' is the answer.
| |
| c. konig 2005-06-02, 3:59 am |
| Hi everybody
Might be a little off-thread-topic but I did not want to start a new
one.
I am also running into problems using g77 after I installed Mac OS X.4
(Tiger). The error message I get is:
g77: installation problem, cannot exec `as': No such file or directory
I updated g77 using fink. It should be up to date.
I looked around for 'as' (assembler?) and found one in my archived
system (10.3.x) but none in the current system.
Do I need to install more Developer Tools? Which ones? I thought I had
the most important ones but might have skipped some (HD filling up...).
Or what else?
Thanks for any help.
Chris
| |
| Richard E Maine 2005-06-02, 3:58 pm |
| In article <1117678902.945463.70220@g14g2000cwa.googlegroups.com>,
"c. konig" <chris.konig@gmail.com> wrote:
> I am also running into problems using g77 after I installed Mac OS X.4
> (Tiger). The error message I get is:
>
> g77: installation problem, cannot exec `as': No such file or directory
....
> Do I need to install more Developer Tools?
I haven't yet installed Tiger, but this doesn't off-hand sound horribly
Tiger specific.
Yes, you need to install the developer's tools. I'm not sure about your
"more" wording, though. That doesn't quite fit, which makes me
suspicious that you haven't actually found the developer's tools. Note
that the developer's tools aren't in fink; if you are looking for
developer tools in fink, that's not the right place. (There are plenty
of tools in fink that are useful for developers, but they aren't the
Apple "Developer's Tools"). Actually, Apple has changed their
terminology (at least once), which tends to confuse things.
What used to be known as the developer's tools now seems to be called
XCode, though it might also still be called developer's tools. It is
probably somewhere on your Tiger DVD, though I don't know exactly where.
--
Richard Maine | Good judgment comes from experience;
email: my first.last at org.domain | experience comes from bad judgment.
org: nasa, domain: gov | -- Mark Twain
| |
| Andy Vaught 2005-06-02, 8:58 pm |
| On 1 Jun 2005, c. konig wrote:
> Hi everybody
>
> Might be a little off-thread-topic but I did not want to start a new
> one.
>
> I am also running into problems using g77 after I installed Mac OS X.4
> (Tiger). The error message I get is:
>
> g77: installation problem, cannot exec `as': No such file or directory
>
> I updated g77 using fink. It should be up to date.
>
> I looked around for 'as' (assembler?) and found one in my archived
> system (10.3.x) but none in the current system.
>
> Do I need to install more Developer Tools? Which ones? I thought I had
> the most important ones but might have skipped some (HD filling up...).
The assembler can be found in the cctools package at:
ftp://gcc.gnu.org/pub/gcc/infrastru...tools-528.5.dmg
Andy
|
|
|
|
|