Sponsored Content
Top Forums Programming Problem with Compiling C on Tiger Post 302172825 by Octal on Tuesday 4th of March 2008 07:01:05 PM
Old 03-04-2008
To explain this better:
You write the program into a file called "cprog.c".
Then after you execute "gcc cprog.c -o cprog", use the command "ls" to list the current files in the directory ("man ls" for more info).
You should see a file called "cprog". This file cprog was created when you did the "gcc cprog.c -o cprog", and this command means that you use the program gcc (gnu c compiler) on the c source file "cprog.c". Then the "-o" means to output the binary file to "cprog". If you hadn't used "-o", gcc would have generated a file called "a.out". ("man gcc" for more info)
Lastly, you can execute the file "cprog" by typing "./cprog" into the terminal. This means to check the directory "./" (which means the current directory that you are in) for the file "cprog". If you didn't specify that "cprog" was in "./", then the operating system would have assumed "cprog" was in "/usr/bin" or another directory (if you want to know type "$PATH" into your terminal).

Does that explain things clearly?
 

10 More Discussions You Might Find Interesting

1. Programming

Problem compiling metamail

Hi Guys. I have downloaded metamail from internet e Iīm trying to compile it at a SCO 5.0.5. In this server itīs working fine (letīs name it as mission1) iīm using the developer package in this server (mission1) and when I use mailto, i got the e-mail fine. Itīs forwarding to a exchange server... (2 Replies)
Discussion started by: ahnishimi
2 Replies

2. Solaris

Compiling problem

I'm trying to install the jed text editor on a SunOS 5.10 box. It depends on the s-lang library, which I installed to ~/lib. I'm trying to install jed to ~/jed (it's a box @ my university, so I don't have rights to install globally), but when I run make I get this error: It looks like it... (1 Reply)
Discussion started by: iandunn
1 Replies

3. Solaris

Problem in PowerDNS compiling

PowerDNS is true Power of Internet Name Management. http://www.powerdns.com Now, I compile it on my SunOS system (SunOS 5.8 Generic_117350-05 sun4u sparc SUNW,Ultra-5_10). ./configure -- no error make --> it has error: <i> make: Fatal error: Command failed for target... (0 Replies)
Discussion started by: secret4all
0 Replies

4. Programming

Problem compiling program

hi i am having a problem that when ever i use cc program_name.c to compile a program. an error occurs, showing cc not found. please help. (28 Replies)
Discussion started by: rochitsharma
28 Replies

5. Solaris

Problem's compiling Glib

Hello, I am trying to install glib on my development box - with little/no luck. Below are some details of the box: SunOS 5.8 Generic_117350-38 sun4u sparc SUNW,Ultra-Enterprise gcc version 2.95.2 19991024 (release) GNU Make version 3.78.1, by Richard Stallman and Roland McGrath. Glib version:... (2 Replies)
Discussion started by: tetley
2 Replies

6. Programming

help on compiling a C program on Tiger

here is the very simple bob.c: main() { printf("hello"); } i use tiger and i use the command: gcc bob.c and the end result: bob.c: In function ‘main': bob.c:3: warning: incompatible implicit declaration of built-in function /‘printf' any help appreciated, i'm just starting... (4 Replies)
Discussion started by: cleansing_flame
4 Replies

7. HP-UX

Problem in HP-UX compiling

Hi When im trying to do make --version and make --help in HP-UX it throws error Make: Unknown flag argument -. Stop. a soft link is present in this directory /usr/bin/make and hard link is in /usr/ccs/bin/make what could be the reason can any1 ..please tell me how to solve this... (1 Reply)
Discussion started by: vasanthan
1 Replies

8. UNIX for Dummies Questions & Answers

Compiling samba problem

People i download the lastest version of samba i`am tryng to compile it in a solaris 9 i'm reading the how to of samba, i am in the first step making the autogen.sh but show me this when i do ./autogen.sh ./autogen.sh: running script/mkversion.sh ./script/mkversion.sh: 'include/version.h'... (0 Replies)
Discussion started by: enkei17
0 Replies

9. Programming

Library problem - not compiling in c

Ok I was trying to test if I installed correctly gsl, I followed the INSTALL file and still I don't know what is wrong. Here is a sample code to test gel,I got it from Random Number Generator Examples - GNU Scientific Library -- Reference Manual (note: made a few changes in the code) #include... (2 Replies)
Discussion started by: joseamck
2 Replies

10. AIX

Compiling problem - AIX 7.2

Hi We meet errors while running configuration scripts to prepare compiling source code on AIX 7.2. This error does not happen on AIX5.3 and AIX6.1 With the “/usr/bin/sh” from AIX7.2, sometimes , the script runs sucessfully, sometimes not. It’s unstable, and I don’t know why. When... (10 Replies)
Discussion started by: bobochacha29
10 Replies
gnats(7)                                                 Problem Report Management System                                                 gnats(7)

NAME
gnats - Problem Report Management System DESCRIPTION
GNATS is a bug-tracking tool designed for use at a central support site. Software users who experience problems use tools provided with GNATS to submit Problem Reports to the the maintainers of that software; GNATS partially automates the tracking of these problems by: o organizing problem reports into a database and notifying responsible parties of suspected bugs; o allowing support personnel and their managers to edit, query and report on accumulated bugs; and o providing a reliable archive of problems with a given program and a history of the life of the program by preserving its reported problems and their subsequent solutions. GNATS offers many of the same features offered by more generic databases. You can query and edit existing problem reports (PRs) as well as obtain reports on groups of PRs. The database itself is simply an ordered repository for problem reports; each PR receives a unique, incremental PR number which identifies it throughout its lifetime. Many of the primary functions available with GNATS are accessible from within GNU Emacs. PROBLEM REPORT STATES
PRs go through several states in their lifetimes. The set of states is site-specific. The default set of states are: open the initial state of every PR; this means the PR has been filed and the person or group responsible for it has been notified of the suspected problem analyzed the problem has been examined and work toward a solution has begun feedback a solution has been found and tested at the support site, and sent to the party who reported the problem; that party is testing the solution closed the solution has been confirmed by the party which reported it In some cases, it may be necessary to suspend work on a bug; in this case, its state changes to suspended rather than closed. STRUCTURE
Incoming PRs are assigned an incremental serial number and filed according to category. An index is kept concurrently to accelerate searches of the database. All GNATS administration and database files are located in subdirectories of a directory associated with each database. Databases are named, and the association between database names and directories is described by the databases file, which is found on this system in /usr/etc/gnats/databases. Problem Reports are segregated into subdirectories within the database directory by category. For example, problems submitted with a cate- gory of gcc will be filed in the database subdirectory gcc. GNATS administration files are kept in the database subdirectory gnats-adm: addresses contains mappings between submitter IDs and corresponding e-mail addresses categories table of valid categories and parties responsible for them classes table of valid classes of Problem Reports current keeps track of incremental PR numbers assigned dbconfig describes the structure of the database, and various database-specific options gnatsd.user_access lists host names and access levels of hosts authorized to access the database gnatsd.user_access lists user names, passwords and access levels of users authorized to access the database index database index locks directory containing lock files responsible table of responsible parties and their email addresses states table of valid states of Problem Reports submitters database of sites which submit PRs Administrative programs and programs internal to GNATS are kept in the directory /usr/libexec/gnats while those meant for public use are installed in /usr/bin. /usr/libexec/gnats contains the programs: mkdb used by the GNATS administrator to create a new database mkcat used by the GNATS administrator to create new categories [obsolete] rmcat used by the GNATS administrator to remove outdated categories [obsolete] gen-index used by the GNATS administrator to generate a new version of the index queue-pr mail control program which accepts incoming messages and periodically submits them to the database via cron by feeding them through the program file-pr(8) pr-edit program which is mainly responsible for editing existing PRs and filing new ones; it is used by edit-pr and file-pr file-pr script which uses pr-edit to file new PRs at-pr automatically notifies responsible parties if a PR is not analyzed within a requisite period defined in the submitters file delete-pr used to delete closed PRs /usr/bin contains the programs query-pr used to query the database edit-pr used to edit individual PRs send-pr used to submit problems to GNATS Documentation exists for all programs associated with GNATS. SEE ALSO
Keeping Track: Managing Messages With GNATS (also installed as the GNU Info file gnats.info) databases(5), dbconfig(5), delete-pr(8), edit-pr(1) file-pr(8), gen-index(8), gnats(7), gnatsd(8), mkcat(8), mkdb(8), pr-edit(8), query- pr(1), queue-pr(8), send-pr(1). HISTORY
GNATS was greatly inspired by the BSD sendbug(1) and bugfiler(8) programs. It was originally written in C++, Elisp, shell script, and awk. It presently consists of utilities written in C, shell script, and Elisp. AUTHORS
GNATS was originally written by Heinz G. Seidl (Cygnus Support). Subsequent iterations were developed by Brendan Kehoe (Cygnus Support) and Jason Merrill (Cygnus Support), with help from Tim Wicinski. Documentation was initially developed by Jeffrey Osier (Cygnus Support) and Brendan Kehoe (Cygnus Support). Version 4.x was a substantial rewrite done by Bob Manson (Juniper Networks), Milan Zamazal and Yngve Svendsen (Clustra Systems / Sun Microsystems) COPYING
Copyright (c) 1992, 1993, 1999, 2000, 2003, Free Software Foundation Permission is granted to make and distribute verbatim copies of this manual provided the copyright notice and this permission notice are preserved on all copies. Permission is granted to copy and distribute modified versions of this manual under the conditions for verbatim copying, provided that the entire resulting derived work is distributed under the terms of a permission notice identical to this one. Permission is granted to copy and distribute translations of this manual into another language, under the above conditions for modified versions, except that this permission notice may be included in translations approved by the Free Software Foundation instead of in the original English. GNATS August 2003 gnats(7)
All times are GMT -4. The time now is 03:58 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy