From: "Kris Warkentin" <kewarken@qnx.com>
To: "Daniel Jacobowitz" <drow@mvista.com>
Cc: <gdb-patches@sources.redhat.com>
Subject: Re: [Patch] correctly configure wcwidth in readline
Date: Wed, 26 Feb 2003 17:44:00 -0000 [thread overview]
Message-ID: <00e901c2ddbe$b23815e0$0202040a@catdog> (raw)
In-Reply-To: <20030226173758.GA14836@nevyn.them.org>
Here's what seems to me to be a more elegant solution. In aclocal.m4, I
just define the obj as wcwidth.o and then the Makefile will either have it
or not.
cheers,
Kris
$ cvs diff Makefile.in aclocal.m4
Index: Makefile.in
===================================================================
RCS file: /cvs/src/src/readline/Makefile.in,v
retrieving revision 1.4
diff -r1.4 Makefile.in
88a89,90
> WCWIDTH_OBJ = @WCWIDTH_OBJ@
>
101c103
< $(srcdir)/mbutil.c
---
> $(srcdir)/mbutil.c $(srcdir)/support/wcwidth.c
114c116,117
< text.o nls.o misc.o compat.o xmalloc.o $(HISTOBJ) $(TILDEOBJ)
---
> text.o nls.o misc.o compat.o xmalloc.o $(HISTOBJ) $(TILDEOBJ) \
> $(WCWIDTH_OBJ)
148a152,155
>
> wcwidth.o: $(srcdir)/support/wcwidth.c
> $(RM) $@
> $(CC) $(CCFLAGS) -c $(srcdir)/support/wcwidth.c
Index: aclocal.m4
===================================================================
RCS file: /cvs/src/src/readline/aclocal.m4,v
retrieving revision 1.4
diff -r1.4 aclocal.m4
1656c1656
< AC_CHECK_FUNC(wcwidth, AC_DEFINE(HAVE_WCWIDTH))
---
> AC_CHECK_FUNC(wcwidth, AC_DEFINE(HAVE_WCWIDTH),
AC_SUBST(WCWIDTH_OBJ,wcwidth.o))
----- Original Message -----
From: "Daniel Jacobowitz" <drow@mvista.com>
To: "Kris Warkentin" <kewarken@qnx.com>
Cc: <gdb-patches@sources.redhat.com>
Sent: Wednesday, February 26, 2003 12:37 PM
Subject: Re: [Patch] correctly configure wcwidth in readline
> On Wed, Feb 26, 2003 at 12:35:16PM -0500, Kris Warkentin wrote:
> > > Something like this needs to go through the maintainers of
> > > bash/readline first.
> >
> > The problem is that I couldn't get any response from the bash/readline
> > maintainers. I mailed the mailing lists and the owner and got no
response.
> > I also noticed that there is a readline/ChangeLog.gdb file with local
> > changes so I figured if I wasn't getting any lovin' from readline, I
might
> > at least get it merged into the gdb tree.
>
> Blech. Yeah, in that case I think this sort of patch is acceptable
> (that's not a comment on the actual patch - I don't know much about
> readline, I leave that to Elena :)
>
> --
> Daniel Jacobowitz
> MontaVista Software Debian GNU/Linux Developer
>
next prev parent reply other threads:[~2003-02-26 17:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-26 17:35 Kris Warkentin
2003-02-26 18:06 ` Daniel Jacobowitz
2003-02-26 17:44 ` Kris Warkentin [this message]
2003-02-26 17:51 ` Daniel Jacobowitz
[not found] ` <00fd01c2ddc0$28ab75e0$0202040a@catdog>
[not found] ` <20030226175915.GA15700@nevyn.them.org>
2003-02-26 18:43 ` Kris Warkentin
2003-02-26 20:14 ` Daniel Jacobowitz
2003-02-26 20:40 ` Kris Warkentin
2003-02-26 20:49 ` Daniel Jacobowitz
2003-02-26 20:52 ` Kris Warkentin
2003-03-03 2:55 ` Elena Zannoni
2003-03-03 14:46 ` Kris Warkentin
2003-02-26 21:26 ` Andreas Schwab
-- strict thread matches above, loose matches on Subject: below --
2003-02-26 20:14 Michael Elizabeth Chastain
2003-02-26 16:57 Michael Elizabeth Chastain
2003-02-26 18:23 ` Andrew Cagney
2003-02-26 16:47 Kris Warkentin
2003-02-26 16:54 ` 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='00e901c2ddbe$b23815e0$0202040a@catdog' \
--to=kewarken@qnx.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