Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <dmj+@andrew.cmu.edu>
To: "H . J . Lu" <hjl@lucon.org>
Cc: gdb-patches@sourceware.cygnus.com
Subject: Re: Patch for readline
Date: Sun, 15 Jul 2001 15:27:00 -0000	[thread overview]
Message-ID: <20010715152744.A21829@nevyn.them.org> (raw)
In-Reply-To: <20010715121010.A20272@lucon.org>

On Sun, Jul 15, 2001 at 12:10:10PM -0700, H . J . Lu wrote:
> When you configure gdb with --prefix=/usr, readline will compile with
> -I/usr/include, which is very bad with gcc and cross compile. Here is
> a patch.
> 
> 
> H.J.
> ----
> 2001-07-15  H.J. Lu  (hjl@gnu.org)
> 
> 	*  Makefile.in (INCLUDES): Never add -I/usr/include.
> 
> --- readline/Makefile.in.include	Sun Jul 15 11:38:10 2001
> +++ readline/Makefile.in	Sun Jul 15 11:42:30 2001
> @@ -63,7 +63,10 @@ LOCAL_DEFS = @LOCAL_DEFS@
>  TERMCAP_LIB = @TERMCAP_LIB@
>  
>  # For libraries which include headers from other libraries.
> -INCLUDES = -I. -I$(srcdir) -I$(includedir)
> +INCLUDES = -I. -I$(srcdir) \
> +  `if test "$(includedir)" != "/usr/include"; then \
> +     echo -I$(includedir); \
> +   else true; fi`
>  
>  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.

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2001-07-15 15:27 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 [this message]
2001-07-15 17:28   ` H . J . Lu

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=20010715152744.A21829@nevyn.them.org \
    --to=dmj+@andrew.cmu.edu \
    --cc=gdb-patches@sourceware.cygnus.com \
    --cc=hjl@lucon.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