Sponsored Content
Top Forums Programming How to compile a c program by using gcc Post 302070867 by Rakesh Ranjan on Sunday 9th of April 2006 06:16:00 AM
Old 04-09-2006
Quote:
Originally Posted by sanju23jan
Just use

gcc -o file file.c

it will create an file.exe

and then run it as

./file.exe
Sorry Sanju but u have mixed up Unix file format ( aout , coff , elf and as86 ) with that of Windows. Compiling the file as u said (gcc -o file file.c) wont create file.exe but rather create an output file with the name 'file' only. And u can run that like ./file
U may even skip '-o ' option in gcc and that will produce an output file named a.out that can be run as ./a.out (Though the native format of Linux is ELF in this case it produces output file of aout format)
And as for Bell plz. follow jim's advise.
 

10 More Discussions You Might Find Interesting

1. Programming

How to compile using gcc...

I need to know how to make a binary with gcc. I know how to create an obj file, but I'm not quite sure what to do about the linking part. I've gotten this far "gcc -c somefile.c somefile.o" then I'm left with an object file, but I don't see any linking command line options. Does anyone know how... (4 Replies)
Discussion started by: lilprogrammer
4 Replies

2. Programming

Error in compile C by gcc

Hi all, I compile my c program and get following result hrnpfc01.c:1387: stray '\' in program hrnpfc01.c:1387: parse error before `,' hrnpfc01.c:1388: stray '\' in program hrnpfc01.c:1388: parse error before `,' hrnpfc01.c:1396: stray '\' in program hrnpfc01.c:1396: parse error before... (4 Replies)
Discussion started by: zico
4 Replies

3. AIX

RS/6000 gcc compile large file error

hi, everybody£º i have a question, pls help me¡£ OS : RS/6000 AIX 4.3.3 cPU : Powerpc,POWER3 compiler : gcc 3.2.3 source file £º 8M OS kernel : 32 bit (selecting at installing operating system, the hardware support 64 bit) when i compiling the large source file (8 M), i... (3 Replies)
Discussion started by: q30
3 Replies

4. Programming

New to C/gcc compiler - compile error.

I am new to comiling c/c++ programs with gcc compilier unix - AIX version 5.3 gcc compiler version - 4.0.0 My makefile. # makefile 1.0 08/20/98 #CC = cc CC = gcc ESQL = esql CFLAGS = -Wall DBSLIB= DBSLIB=-L${INFORMIXDIR}/lib/esql -L${INFORMIXDIR}/lib `esql -libs` ALL = hds_near... (9 Replies)
Discussion started by: anish
9 Replies

5. AIX

Compile gcc on AIX 5.2

I'm trying to compile gcc 3.4.6 on AIX 5.2 but I get this error: bison -t --name-prefix=java_ -o java/parse.c java/parse.y M4sugar requires GNU M4. Install it before installing M4sugar or set the M4 environment variable to its path name.make: *** Broken pipe gcc -c -g -O2 -DIN_GCC -W... (7 Replies)
Discussion started by: untamed
7 Replies

6. Programming

compile a c program

I am trying to compile a c program on AIX 5.3L 64-bit unix. I have used this program in the past and it works. Does anybody know what this error means? /usr/local/bin> gcc get_epoch_secs.c get_epoch_secs gcc: get_epoch_secs: No such file or directory get_epoch_secs.c: In function... (8 Replies)
Discussion started by: djehresmann
8 Replies

7. SuSE

Can't compile or install GCC

Hi all! I have posted in the Shell Programming Scripting Forum for a problem with the use of shc and so on... You can read it complete here: shell-programming-scripting/148510-problems-using-shc.html I think the problem is: that there aren't compiler installed on the SuSe 10.2 server,... (4 Replies)
Discussion started by: Magius
4 Replies

8. UNIX for Dummies Questions & Answers

Compiling gcc to compile make to compile yaboot

I have just installed OpenBSD on a 333MHz PPC iMac G3. It has a 6GB HDD that has been partitioned as 1GB MacOS 8.5.1, 3GB MacOS X 10.3.9, 2GB OpenBSD 4.8. I now need to install a bootloader so that my computer can recognize the OpenBSD partition at startup. I have been trying to install... (0 Replies)
Discussion started by: t04st3r
0 Replies

9. Red Hat

How to compile httpd using gcc in RHEL?

Hi All, I am trying to compile httpd2.2.19 in RHEL5.5 using gcc version 4.1.2. This is first time I am trying to compile httpd in RHEL. I ran configure with below option ./configure --prefix=/usr/local/apache --enable-rewrite --enable-ssl=shared... (0 Replies)
Discussion started by: kalpeer
0 Replies

10. Programming

I can't compile (gcc) in Solaris 11.3 non global zone

I can't compile anything, the final make error says "Command failed for target `install-recursive'", but I am not able to identify the root cause of that error, I tried with cc, gcc 4.5, also gcc 5.2, using make, using gmake 3.82, ld 5.11, gld 2.31... and I am totally stuck yet... please help, to... (4 Replies)
Discussion started by: sugar222
4 Replies
WINDRES(1)						       GNU Development Tools							WINDRES(1)

NAME
windres - manipulate Windows resources. SYNOPSIS
windres [options] [input-file] [output-file] DESCRIPTION
windres reads resources from an input file and copies them into an output file. Either file may be in one of three formats: "rc" A text format read by the Resource Compiler. "res" A binary format generated by the Resource Compiler. "coff" A COFF object or executable. The exact description of these different formats is available in documentation from Microsoft. When windres converts from the "rc" format to the "res" format, it is acting like the Windows Resource Compiler. When windres converts from the "res" format to the "coff" format, it is acting like the Windows "CVTRES" program. When windres generates an "rc" file, the output is similar but not identical to the format expected for the input. When an input "rc" file refers to an external filename, an output "rc" file will instead include the file contents. If the input or output format is not specified, windres will guess based on the file name, or, for the input file, the file contents. A file with an extension of .rc will be treated as an "rc" file, a file with an extension of .res will be treated as a "res" file, and a file with an extension of .o or .exe will be treated as a "coff" file. If no output file is specified, windres will print the resources in "rc" format to standard output. The normal use is for you to write an "rc" file, use windres to convert it to a COFF object file, and then link the COFF file into your application. This will make the resources described in the "rc" file available to Windows. OPTIONS
-i filename --input filename The name of the input file. If this option is not used, then windres will use the first non-option argument as the input file name. If there are no non-option arguments, then windres will read from standard input. windres can not read a COFF file from standard input. -o filename --output filename The name of the output file. If this option is not used, then windres will use the first non-option argument, after any used for the input file name, as the output file name. If there is no non-option argument, then windres will write to standard output. windres can not write a COFF file to standard output. Note, for compatibility with rc the option -fo is also accepted, but its use is not recommended. -J format --input-format format The input format to read. format may be res, rc, or coff. If no input format is specified, windres will guess, as described above. -O format --output-format format The output format to generate. format may be res, rc, or coff. If no output format is specified, windres will guess, as described above. -F target --target target Specify the BFD format to use for a COFF file as input or output. This is a BFD target name; you can use the --help option to see a list of supported targets. Normally windres will use the default format, which is the first one listed by the --help option. --preprocessor program When windres reads an "rc" file, it runs it through the C preprocessor first. This option may be used to specify the preprocessor to use, including any leading arguments. The default preprocessor argument is "gcc -E -xc-header -DRC_INVOKED". -I directory --include-dir directory Specify an include directory to use when reading an "rc" file. windres will pass this to the preprocessor as an -I option. windres will also search this directory when looking for files named in the "rc" file. If the argument passed to this command matches any of the supported formats (as described in the -J option), it will issue a deprecation warning, and behave just like the -J option. New programs should not use this behaviour. If a directory happens to match a format, simple prefix it with ./ to disable the backward compatibility. -D target --define sym[=val] Specify a -D option to pass to the preprocessor when reading an "rc" file. -U target --undefine sym Specify a -U option to pass to the preprocessor when reading an "rc" file. -r Ignored for compatibility with rc. -v Enable verbose mode. This tells you what the preprocessor is if you didn't specify one. -c val --codepage val Specify the default codepage to use when reading an "rc" file. val should be a hexadecimal prefixed by 0x or decimal codepage code. The valid range is from zero up to 0xffff, but the validity of the codepage is host and configuration dependent. -l val --language val Specify the default language to use when reading an "rc" file. val should be a hexadecimal language code. The low eight bits are the language, and the high eight bits are the sublanguage. --use-temp-file Use a temporary file to instead of using popen to read the output of the preprocessor. Use this option if the popen implementation is buggy on the host (eg., certain non-English language versions of Windows 95 and Windows 98 are known to have buggy popen where the output will instead go the console). --no-use-temp-file Use popen, not a temporary file, to read the output of the preprocessor. This is the default behaviour. -h --help Prints a usage summary. -V --version Prints the version number for windres. --yydebug If windres is compiled with "YYDEBUG" defined as 1, this will turn on parser debugging. @file Read command-line options from file. The options read are inserted in place of the original @file option. If file does not exist, or cannot be read, then the option will be treated literally, and not removed. Options in file are separated by whitespace. A whitespace character may be included in an option by surrounding the entire option in either single or double quotes. Any character (including a backslash) may be included by prefixing the character to be included with a backslash. The file may itself contain additional @file options; any such options will be processed recursively. SEE ALSO
the Info entries for binutils. COPYRIGHT
Copyright (c) 1991, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010 Free Software Foundation, Inc. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, with no Front-Cover Texts, and with no Back-Cover Texts. A copy of the license is included in the section entitled "GNU Free Documentation License". binutils-2.21.1 2011-06-27 WINDRES(1)
All times are GMT -4. The time now is 08:29 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy