Compiler using -Wall and -static

[littlevamp]

Hi,

How do we go about compiling the program with -static and -Wall? Why is there a need to use -static when we can compile using: gcc -Wall -o file file.c?

I tried using gcc -Wall -static file file.c but there are quite a number of warnings from this statement.

Can someone please help? Thanks in advance! =)

[Jordan]

You use -static to compile the libraries into the executable. This way the user doesn't have to have any additional libraries installed in order for the program to run. When you compile without -static you are linking dynamically.

What errors do you receive when you compile with -static?

[littlevamp]

Hi Jordan, thanks for your reply =)

gcc -Wall -static fork fork.c results in error: gcc: fork: No such file or directory.

After trying again, I finally used command line: gcc -Wall -g -c -o fork -static fork.c and it compile with no errors. But when I tried to do a strace ./fork, there was an error saying: ERROR: unable to open /dev/log.

I'm not sure what was happening. I'm using SSH (Secure Shell Client) to run my command.

[Cynic]

Originally Posted by littlevamp

Hi Jordan, thanks for your reply =)

gcc -Wall -static fork fork.c results in error: gcc: fork: No such file or directory.

After trying again, I finally used command line: gcc -Wall -g -c -o fork -static fork.c and it compile with no errors. But when I tried to do a strace ./fork, there was an error saying: ERROR: unable to open /dev/log.

It's been a while since I compiled using gcc, but let me see if I can get this right.

-c tells it to compile only, do not create an executable.
-o allows you to name the intermediate object file.

So, you are in effect not making an executable, so there is nothing to trace.