From: Miguel Griffa <mgriffa@technisys.com.ar>
To: fox@sby.centrin.net.id
Cc: linux-c-programming@vger.kernel.org
Subject: Re: start learning gcc ... how to ?
Date: Tue, 9 Apr 2002 10:04:44 -0300 [thread overview]
Message-ID: <20020409130444.GA276@wotan> (raw)
In-Reply-To: <200204091150.g39Bo4825347@jupiter.centrin.net.id>
[-- Attachment #1: Type: text/plain, Size: 1145 bytes --]
Hi,
gcc has lots of options, but theses are (almost) all I've needed:
-Wall (Warnings:ALL)
-g (generate debug info)
-ggdb (idem but with gdb extensions)
-o (output to file)
-c (compile only, don't link for makeing .o)
-ansi (kindda obvious)
Well, I know is little but it might help you to start
I'd strongly recomend you reading a make tutorial
On Tue, Apr 09, 2002 at 06:50:05PM +0700, fox@sby.centrin.net.id wrote:
> Hi...
>
> I'm newbie here...:)(also newbie in Linux)
> I know a little about C/C++ programming (in DOS) and now I want to
> learn about GCC, where I can find some (good) tutorials about it (urls
> please)?
> may be I need some example for compiling (and debugging) with
> gcc...because gcc's option too many and it's not simple I think.
>
> And, also, where I can find some good tutorials about using KDevelop ?
>
> thank you...
>
> --
> Best regards,
> adwin
> -
> To unsubscribe from this list: send the line "unsubscribe linux-c-programming" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2002-04-09 13:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-09 11:50 start learning gcc ... how to ? fox
2002-04-09 13:04 ` Miguel Griffa [this message]
2002-04-09 16:01 ` Re[2]: " adwin
2002-04-09 16:34 ` Elias Athanasopoulos
[not found] ` <1018533665.9524.5.camel@abodh.lan.deeproot.co.in>
2002-04-12 9:22 ` Elias Athanasopoulos
2002-04-09 22:09 ` Re[2]: " Glynn Clements
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020409130444.GA276@wotan \
--to=mgriffa@technisys.com.ar \
--cc=fox@sby.centrin.net.id \
--cc=linux-c-programming@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.