Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@oss.sgi.com>
To: Steven Liu <stevenliu@psdc.com>
Cc: Keith M Wesolowski <wesolows@foobazco.org>, linux-mips@oss.sgi.com
Subject: Re: mips-tfile
Date: Sat, 19 May 2001 00:23:05 -0300	[thread overview]
Message-ID: <20010519002305.B1209@bacchus.dhis.org> (raw)
In-Reply-To: <000801c0dff4$3870ba60$dde0490a@pcs.psdc.com>; from stevenliu@psdc.com on Fri, May 18, 2001 at 04:42:37PM -0700

On Fri, May 18, 2001 at 04:42:37PM -0700, Steven Liu wrote:

> I have a question regarding MIPS Makefile.
> 
> In the Makefile of the Linux build directory, there are two Macros of C
> compiler flags: HOSTCFLAGS and CFLAGS.
> 
> What are their purpose and difference? In another words, what is host gcc?
> Why do we use host gcc in building the target kernel?

During the build process of the kernel some tools like scripts/mkdep and
others are built which are running on the compile machine, not the target
machine.  The variable HOSTCFLAGS takes some extra compiler options to be
passed for such compilations.

  Ralf

  parent reply	other threads:[~2001-05-19  3:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-05 12:49 mips-tfile Steven Liu
2001-03-05 12:49 ` mips-tfile Steven Liu
2001-03-06  4:55 ` mips-tfile Keith M Wesolowski
2001-03-09 16:58   ` mips-tfile Ralf Baechle
2001-05-18  1:09   ` mips-tfile Steven Liu
2001-05-18  1:09     ` mips-tfile Steven Liu
2001-05-18  1:31     ` mips-tfile Ralf Baechle
2001-05-18 23:42       ` mips-tfile Steven Liu
2001-05-18 23:42         ` mips-tfile Steven Liu
2001-05-18 23:50         ` mips-tfile Justin Carlson
2001-05-19  3:23         ` Ralf Baechle [this message]
2001-03-09 17:15 ` Scrabled headers, was: mips-tfile Ralf Baechle
2001-03-09 17:15   ` Ralf Baechle

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=20010519002305.B1209@bacchus.dhis.org \
    --to=ralf@oss.sgi.com \
    --cc=linux-mips@oss.sgi.com \
    --cc=stevenliu@psdc.com \
    --cc=wesolows@foobazco.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