Compiling and running in terminal at the same time

[pakito15191]

Hello to everyone
This is my first post here, I'm new in Fedora and I came some weeks ago from Ubuntu (since Fedora 15 beta was available)
I like to program sometimes, and in Ubuntu I just used gedit and a little script I did that worked pretty well with my C files, as I didn't like too much the compilers and I love the gedit syntax

I wrote this (at the beginning of the C source code):

/*
#!/bin/bash
gcc program.c -o program -lm
./program
*/

And I just had to double click the source file (ofc I gave it "Execution permission" ages ago), select "Run in terminal" and it did all itself, giving me the program from just that, from the source code

Here, if I follow the normal steps to compile the program manually, it works perfectly, but if I try this script, it gives me the following error:
/home/user/Program/program.c: line 1: /bin: Is a directory

I know it's shouldn't be right at all to execute a bash script from a .c code that then compiled itself, but it used to work, so I was wondering where is the difference

I have gcc installed and "which bash" gives me the "/bin/bash", so I think that's right
Also, I'm using the stable version of Fedora 15, and I post this question because I didn't find the answer anywhere
Thank you so much!

[Dies]

I thought the "shebang" had to be on the first line. I definitely wouldn't have expected it to work sandwiched between C-style comments...

I guess you're right though it *sort* of works on Ubuntu.

~$ ./test.sh 
./test.sh: line 1: /bin: is a directory
This shouldn't work!
./test.sh: line 4: Desktop/: is a directory

For whatever reason it still ran my "echo" line.

[stevea]

DIes is right - the pound-bang "#!" as the VERY FIRST characters of a file are interpreted in the kernel exec.
Putting that in on the second line is meaningless.

Since the file is executable and not a recognized binary format it is still exec'ed in the shell.
The first line "/*" is interpretted as a bash shell command. On my root file system "/* expands to ...
/bin /boot /cgroup /common /dev /etc /home /lib /lib64 /lost+found /media /mnt /null /opt /opt2 /proc /root /sbin /selinux /
and when the shell attempts to execute this - then it complains that /bin is a directory - not a command or executable.

My advise is to NOT overload the intended meaning of files. Learn to create a makefile like:

[stevea@hypoxylon tmp]$ cat Makefile
LDLIBS="-lm"

p: p.c

Then the command 'make' does the right thing.