All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] Allow override of CFLAGS/LDFLAGS
Date: Tue, 02 Dec 2003 00:42:40 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-107033884717932@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-106971527707016@msgid-missing>

On Mon, Nov 24, 2003 at 04:59:19PM -0600, Chris Larson wrote:
> Greetings,
> 
> As it is generally a good idea to allow the user to override CFLAGS and
> LDFLAGS (automake based systems manage this with AM_CFLAGS vs CFLAGS),
> here's a patch that does so.  The key is to keep options that are
> required to build, along with include and link paths relative to the
> source dir seperate from those that should be overridable (warning
> flags, debug flags, optimizations, include/lib paths outside the source
> tree).  Rather than adding another couple variables, I made use of the
> GNU make 'override' directive.

Hm, this patch breaks the binary when building with klibc.  Can you try
to fix it up?

thanks,

greg k-h


-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

  reply	other threads:[~2003-12-02  0:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-24 22:59 [PATCH] Allow override of CFLAGS/LDFLAGS Chris Larson
2003-12-02  0:42 ` Greg KH [this message]
2003-12-02  1:33 ` Chris Larson

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-hotplug-107033884717932@msgid-missing \
    --to=greg@kroah.com \
    --cc=linux-hotplug@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.