Hey
i downloaded gcc , propably the latest version on my 'Fedora 7.
I am trying to compile a simple program.
If i save the program as <name>.f i get this message:
PROGRAM ela
1
Error: Non-numeric character in statement label at (1)
In file ela.f:1

PROGRAM ela
1
Error: Unclassifiable statement at (1)
In file ela.f:2

PRINT * ,'satanas'
1
Error: Non-numeric character in statement label at (1)
In file ela.f:2

PRINT * ,'satanas'
1
Error: Unclassifiable statement at (1)
In file ela.f:3

END
1
Error: Non-numeric character in statement label at (1)
In file ela.f:3

END
1
Error: Unclassifiable statement at (1)


Then if i save it as <name>.f95 and compile it again i get no errors. But the executable file does not work.
Any suggestions?
Is it possible to put also the f77 compiler to on my system?

Try sudo yum install compat-gcc-34-g77 compat-libf2c-34

But I'd suggest you first look at info gfortran for suggestions about getting the f95 program to run.

thanks for the help But,...
Ok i checked the manual , i also checked the official site and it seems that everything should have been working .
With the something.f files it never works .
But with the something.f95 everything is fine.
I compile it , i get an executable file, and then the file does Nothing...!
I don want do download the g77 ,since the manual says that its ok compiling older fortran formats, and i dont wan to mix up things by downloading stuff.

I am a newbie so i know nothing about the sourcecodes , or about the libraries maybe is somethin to do with these things.

Do you have libgfortran installed? gcc-gfortran?

compat-lib2c-34 might also be useful.

Can you show us your F95 code? (If you paste the code into a message, put it between "code" tags. I.e., a [ code ] and [ /code ] with no spaces within the brackets, or, if you're using the "reply" form instead of the default "quick reply" one, just highlight the code an click the "#" button at the top of the input form.)

I suspect that you're missing a library, but I'm surprised that you got an executable file if the library isn't available.

i have everything!
But it doesnt work. I dont realy know why.
is there a way of uninstalling them so i can pu them back again?

Does it really do nothing or does it give some errors? What is it expected to do? Can you post the code or the relevant parts of the code, as PTrenholme suggested?

the code is really sipmle i just did it to check if the compiler works
[program test print*,'pls work..' end]

Then i saved the fil as .test.f95
and this is what happens in the terminal when i compile and try to execute:

[vassos@localhost fortr]$ f95 test.f95 -o test
[vassos@localhost fortr]$ test
[vassos@localhost fortr]$ dir
test test.f95
[vassos@localhost fortr]$

Try using the standard executable output:For some reason, using the -o option doesn't seem to work.
<edit> Ah, yes. (See below) It did work, there's just a "test" commandin my (and your) path. (Actually, "test" is a bash built-in command. I'd forgotten that since I almost always use the "[" test command alias.)

Another suggestion: Try naming your executables using upper-case letters. Almost all Linux command use mixed case.
</edit>

(I don't know if the "stop" is really needed, but it doesn't hurt to flush the buffers.)

You might want to look at the kdevelop package if you're using KDE -- it supports standard project development for any of the gcc-supported languages.

Here is the problem: you are executing the linux test command, not really the program you have just compiled. To be sure to execute the command which is in your current directory, you should launch it with its relative path:
as in the example of PTrenholme for launching the a.out executable. Just a little of experience, then you will type ./ automatically!

YEEEEES! thanks a lot.
It worked finally. Just by using the ./ before calling the program.
And the -o command works to.

I have a question though what is the difference of using ./ ??
Some times when i am installing something while usinh configure, or make install , i have to use ./ and some times not
why is that???

When you launch a command on Linux/Unix the system looks for that command on some directories. These are the directories listed in your environment variable called PATH. Try
to inspect your own PATH. When an executable that matches the name you've typed on the command line, is encountered along the PATH, it is executed.
But you can also launch a command specifying its absolute or relative path: for example, if you have an executable called test in /home/vassos/fortr you can launch it with its absolute path, despite the directory you're currently into:
or with its relative path... relative to the directory you're currently into:
or
This is the reason why typing simply test and not ./test, the system has executed the shell command test: it has encountered an executable called test along the PATH and has executed it. Simply. You can verify where the test command is located by:
Cheers.