public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kalin KOZHUHAROV <kalin@thinrope.net>
To: linux-kernel@vger.kernel.org
Subject: Re: Howto set kernel makefile to use particular gcc
Date: Mon, 02 Jan 2006 16:21:53 +0900	[thread overview]
Message-ID: <dpakah$tip$2@sea.gmane.org> (raw)
In-Reply-To: <3AEC1E10243A314391FE9C01CD65429B223AF3@mail.esn.co.in>

Do not top-post!
http://en.wikipedia.org/wiki/Toppost

Mukund JB. wrote:
> Jasper,
> 
> But I was doing it all that I was doing with 2.4 i.e. the follwoing steps to build the kernel.
> I also found these steps are followed in the 2.6.x kernel build howto's too.
> 
> Do you mean, to rebuild the 2.6.x kernel,
> 
> 	make CC=<path of gcc> would be enough?
> 
Yes that will do to compile any 2.6.x kernel.

> I am just thinking whether I am doing something redundent.
Just a bit, usually not a problem (but may be wrong).

Kalin.
-- 
|[ ~~~~~~~~~~~~~~~~~~~~~~ ]|
+-> http://ThinRope.net/ <-+
|[ ______________________ ]|


  reply	other threads:[~2006-01-02  7:30 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-02  5:59 Howto set kernel makefile to use particular gcc Mukund JB.
2006-01-02  7:21 ` Kalin KOZHUHAROV [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-12-30  7:25 Mukund JB.
2005-12-31  0:42 ` Jiri Slaby
2005-12-30  7:04 Mukund JB.
2005-12-30  7:24 ` Chris White
2006-01-01 10:03   ` Kalin KOZHUHAROV
2006-01-01 11:13     ` Marc Giger
2006-01-01 11:18       ` Keith Owens
2006-01-01 11:37         ` Marc Giger
2006-01-01 11:49           ` Kalin KOZHUHAROV
2006-01-01 13:09           ` Keith Owens
2006-01-01 12:00     ` Adrian Bunk
2006-01-02  7:19       ` Kalin KOZHUHAROV
2005-12-30  8:25 ` Jesper Juhl
2005-12-30  5:46 Mukund JB.
2005-12-30  6:58 ` Alessandro Suardi

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='dpakah$tip$2@sea.gmane.org' \
    --to=kalin@thinrope.net \
    --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