From: Viral Mehta <viral.mehta@einfochips.com>
To: lkml <linux-kernel@vger.kernel.org>
Subject: Re: gcc compilation
Date: Mon, 18 May 2009 18:20:02 +0530 [thread overview]
Message-ID: <4A11597A.5010904@einfochips.com> (raw)
In-Reply-To: <4A115480.60003@einfochips.com>
Ohh sorry asking w/o g00gling...
I just found
GCC manual : "the default configuration is to perform a 3-stage
bootstrap of the compiler when ‘make’ is invoked. This will build the
entire GCC system and ensure that it compiles itself correctly."
Viral Mehta wrote:
> Hello,
>
> I was compiling 2.6.29.7 kernel but it stopped as my system had gcc
> version 4.1.1.
> There was some bug with respect to __weak attribute in gcc 4.1.[01].
> So, I started installing newer gcc 4.3.0.
>
> That was a history part. Now, I have a query.
>
> If I am installing gcc 4.3.0. It will be compiled using gcc 4.1.0 as I
> have that installed on my PC. Now, gcc 4.1.0 has several BUGS and so
> compilation of gcc 4.3.0 will not happen correctly. How this situation
> is handled normally ??
--
Thanks, Viral Mehta, Embedded Software Engineer, www.einfochips.com
prev parent reply other threads:[~2009-05-18 12:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-18 12:28 gcc compilation Viral Mehta
2009-05-18 12:50 ` Viral Mehta [this message]
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=4A11597A.5010904@einfochips.com \
--to=viral.mehta@einfochips.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox