From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Rohit Rehan <rohitrehan008@gmail.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: C compiler
Date: Sun, 13 Mar 2011 14:47:00 -0000 [thread overview]
Message-ID: <AANLkTinijO0ov+uG5733gyNuw1i8ybrq22f501LeNz6r@mail.gmail.com> (raw)
In-Reply-To: <4D7CD7BE.00000B.01676@L070-PC>
On 13 March 2011 14:42, Rohit Rehan wrote:
> Sir,
> How com the compiler of c is written in C. I mean first we need to compile
> the source to get object but if we don't have a compiler to compile C source
> how can we write a compiler in C. I am totally confused please help me.
Yes, you need a C compiler to build GCC from source:
http://gcc.gnu.org/install/prerequisites.html
This is a common technique, see
http://en.wikipedia.org/wiki/Bootstrapping_(compilers)
Most operating systems either have pre-built versions of GCC available
or provide another C compiler which can be used to compile GC.
next prev parent reply other threads:[~2011-03-13 14:47 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-13 14:43 Rohit Rehan
2011-03-13 14:47 ` Jonathan Wakely [this message]
[not found] <815189974.291369.1523654409630.ref@mail.yahoo.com>
2018-04-13 21:20 ` C++ Compiler Roy Ware via gcc-help
2018-04-13 21:35 ` Martin Sebor
2018-04-13 21:35 ` Andrew Bell
2018-04-13 21:35 ` Marc Glisse
2018-04-13 21:45 ` Roy Ware via gcc-help
-- strict thread matches above, loose matches on Subject: below --
2014-10-19 14:28 C compiler BASAVARAJ L KAGE
2014-10-20 12:42 ` Jonathan Wakely
2013-04-30 2:31 C++ Compiler Scarlbc
2013-04-30 9:06 ` Jonathan Wakely
2007-01-13 19:32 C compiler Berg, Michelle D.
2007-01-15 10:06 ` Hugh Sasse
2005-07-25 17:44 c++ compiler Niels Jende
2005-07-25 17:46 ` corey taylor
2002-08-01 20:50 Dockeen
[not found] <200208012209.AAA06454@mailin.webmailer.de>
2002-08-01 16:00 ` Simon Brügmann
2002-08-01 18:00 ` Oscar Fuentes
2000-07-13 15:52 c compiler Edward Lartey
2000-02-05 23:39 c_compiler Ben Michie
2000-04-01 0:00 ` c_compiler Ben Michie
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=AANLkTinijO0ov+uG5733gyNuw1i8ybrq22f501LeNz6r@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=rohitrehan008@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).