From: Elena Zannoni <ezannoni@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] fix -Werrors from new readline
Date: Sun, 08 Dec 2002 20:42:00 -0000 [thread overview]
Message-ID: <15860.7482.156282.685877@localhost.redhat.com> (raw)
In-Reply-To: <20021209013830.GA27320@nevyn.them.org>
Daniel Jacobowitz writes:
> On Sun, Dec 08, 2002 at 08:23:40PM -0500, Elena Zannoni wrote:
> >
> >
> > And the makefile.
> >
> > 2002-12-08 Elena Zannoni <ezannoni@redhat.com>
> >
> > * Makefile.in (readline_h): Define.
> > (completer.o): Depend on readline_h.
> > (corelow.o): Ditto.
> > (event-top.o): Ditto.
> > (exec.o): Ditto.
> > (solib.o): Ditto.
> > (source.o): Ditto.
> > (symfile.o): Ditto.
> > (symmisc.o): Ditto.
> > (top.o): Ditto.
> > (tracepoint.o): Ditto.
> > (utils.o): Ditto.
> > (cli-dump.o): Ditto.
> > (tui-hooks.o): Ditto.
> > (tuiWin.o): Ditto.
>
> > +readline_h = $(READLINE_SRC)/readline.h
>
> Erk, is this necessary? It comes from the combined source tree, but
> it's basically a 'system' header. I compile using the system readline
> instead of the included one; this is just another thing which would get
> in the way of doing that.
>
Hmm, but what happens if the system readline and gdb's readline get
out of sync again? BTW, there was a readline_h already used in some
tui files, but it wasn't defined.
Rereading your sentence... you are trying to get rid of src/readline?
> (The patches to do this are getting smaller; I'll finish and post them,
> really I will!)
>
> --
> Daniel Jacobowitz
> MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-12-09 4:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-08 17:25 Elena Zannoni
2002-12-08 17:36 ` Elena Zannoni
2002-12-08 18:44 ` Daniel Jacobowitz
2002-12-08 20:42 ` Elena Zannoni [this message]
2002-12-08 22:07 ` Daniel Jacobowitz
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=15860.7482.156282.685877@localhost.redhat.com \
--to=ezannoni@redhat.com \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.redhat.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