All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Samuelson <peter@cadcamlab.org>
To: Peter Bergner <bergner@borg.umn.edu>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>, bergner@us.ibm.com
Subject: Re: Different CFLAGS for arch and non-arch files.
Date: Tue, 20 Feb 2001 22:48:30 -0600	[thread overview]
Message-ID: <20010220224830.B28652@cadcamlab.org> (raw)
In-Reply-To: <20010220210802.A451159@brule.borg>
In-Reply-To: <20010220210802.A451159@brule.borg>; from bergner@borg.umn.edu on Tue, Feb 20, 2001 at 09:08:02PM -0600


[Peter Bergner]
> Hopefully someone can point me in the right direction here.
> I need to use different CFLAGS options depending on whether
> I'm compiling arch dependent code or arch independent code.

Use the per-directory $(EXTRA_CFLAGS), and/or the per-file
$(CFLAGS_foo.o).  See also $(EXTRA_AFLAGS), $(EXTRA_LDFLAGS) and
$(AFLAGS_foo.o).  I suppose there ought to be a $(LDFLAGS_foo.o) for
completeness, but nobody has needed it yet.

Peter

      reply	other threads:[~2001-02-21  4:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-21  3:08 Different CFLAGS for arch and non-arch files Peter Bergner
2001-02-21  4:48 ` Peter Samuelson [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=20010220224830.B28652@cadcamlab.org \
    --to=peter@cadcamlab.org \
    --cc=bergner@borg.umn.edu \
    --cc=bergner@us.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.