public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] arch/ia64/Makefile tweak
Date: Tue, 02 Apr 2002 19:17:41 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590701905364@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590701905357@msgid-missing>

Applied, thanks.

In the future, please send properly formatted patches, so that they
can be applied with "patch -p1".  This avoids creating extra work when
applying the patch in the bitkeepr tree.

Thanks,

	--david

>>>>> On Mon, 1 Apr 2002 17:36:12 -0800, Gary Hade <garyhade@us.ibm.com> said:

  Gary> If the gcc in your PATH is version 2.X and you are not using
  Gary> cross tools (the CROSS_COMPILE make macro is null) `make
  Gary> CC=<path to a 3.X gcc>` fails due to the lack of --param
  Gary> max-inline-insns 00 on the compile lines.

  Gary> This happens because GCC_VERSION in arch/ia64/Makefile is
  Gary> determined using $(CROSS_COMPILE)$(HOSTCC) which expands "gcc"
  Gary> picking up gcc 2.X.  With GCC_VERSION defined as 2 the
  Gary> additional CFLAGS options within the ifneq ($(GCC_VERSION),2)
  Gary> are not being added.

  Gary> You can work around the problem by also setting HOSTCC on the
  Gary> make command line e.g. `make CC=<path to a 3.X gcc>
  Gary> HOSTCC=<path to a 3.X gcc>` but I believe the correct solution
  Gary> is to use $(CC) instead of $(CROSS_COMPILE)$(HOSTCC) to
  Gary> determine GCC_VERSION.

  Gary> Gary


      reply	other threads:[~2002-04-02 19:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-02  1:36 [Linux-ia64] arch/ia64/Makefile tweak Gary Hade
2002-04-02 19:17 ` David Mosberger [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=marc-linux-ia64-105590701905364@msgid-missing \
    --to=davidm@napali.hpl.hp.com \
    --cc=linux-ia64@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