From: "H . J . Lu" <hjl@lucon.org>
To: gdb-patches@sourceware.cygnus.com
Subject: Re: Patch for readline
Date: Sun, 15 Jul 2001 17:28:00 -0000 [thread overview]
Message-ID: <20010715172814.A15278@lucon.org> (raw)
In-Reply-To: <20010715152744.A21829@nevyn.them.org>
On Sun, Jul 15, 2001 at 03:27:44PM -0700, Daniel Jacobowitz wrote:
> >
> > CCFLAGS = $(DEFS) $(LOCAL_DEFS) $(CPPFLAGS) $(INCLUDES) $(LOCAL_CFLAGS) $(CFLAGS)
>
> Is -I$(includedir) ever actually right? I've always considered it to
> be where include files should be installed, not referenced from.
That was my thinking too. Certainly Linux doesn't need it. But I cannot
speak for all other platforms.
H.J.
prev parent reply other threads:[~2001-07-15 17:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-15 12:10 H . J . Lu
2001-07-15 15:27 ` Daniel Jacobowitz
2001-07-15 17:28 ` H . J . Lu [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=20010715172814.A15278@lucon.org \
--to=hjl@lucon.org \
--cc=gdb-patches@sourceware.cygnus.com \
/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