From: Daniel Jacobowitz <drow@mvista.com>
To: Kris Warkentin <kewarken@qnx.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [Patch] correctly configure wcwidth in readline
Date: Wed, 26 Feb 2003 16:54:00 -0000 [thread overview]
Message-ID: <20030226165452.GA13402@nevyn.them.org> (raw)
In-Reply-To: <008501c2ddb6$b33de6c0$0202040a@catdog>
On Wed, Feb 26, 2003 at 11:47:07AM -0500, Kris Warkentin wrote:
> I have attached a patch that correctly deals with the absence of a wcwidth()
> function by building support/wcwidth.c and linking it into libreadline.
> Oddly enough, the HAVE_WCWIDTH check fails on other systems too (ie. Cygwin)
> but causes no problem since wcwidth() gets picked up elsewhere. On QNX
> Neutrino, however, we're actually missing wcwidth() so we get undefined
> references. What is the procedure for regenerating configure scripts?
> Should I regenerate it here and commit it or do you have a certain person
> who does it under a specific environment?
Kris, from MAINTAINERS:
readline/ Master version: ftp://ftp.cwru.edu/pub/bash/
Elena Zannoni ezannoni@redhat.com
Host maintainers (host dependant parts)
(but get your changes into the master version)
Something like this needs to go through the maintainers of
bash/readline first.
Yes, normally you regenerate any generated files when checking in a
patch.
> + HAVE_WCWIDTH = @HAVE_WCWIDTH@
> +
> + ifeq ($(HAVE_WCWIDTH), no)
> + WCWIDTH_SRC = $(srcdir)/support/wcwidth.c
> + WCWIDTH_OBJ = wcwidth.o
> + endif
> +
Can't do that. It's a GNU-make-ism. You have to move more of the
logic to configure.
> +
> + ifeq ($(HAVE_WCWIDTH), no)
> + $(WCWIDTH_OBJ): $(WCWIDTH_SRC)
> + $(RM) $@
> + $(CC) $(CCFLAGS) -c $(WCWIDTH_SRC)
> + endif
That should probably be an unconditional rule, a la:
wcwidth.o: $(srcdir)/support/wcwidth.c
$(RM) $@
$(CC) $(CCFLAGS) -c $(srcdir)/support/wcwidth.c
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-02-26 16:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-26 16:47 Kris Warkentin
2003-02-26 16:54 ` Daniel Jacobowitz [this message]
2003-02-26 16:57 Michael Elizabeth Chastain
2003-02-26 18:23 ` Andrew Cagney
2003-02-26 17:35 Kris Warkentin
2003-02-26 18:06 ` Daniel Jacobowitz
2003-02-26 17:44 ` Kris Warkentin
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
2003-02-26 20:14 Michael Elizabeth Chastain
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=20030226165452.GA13402@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=kewarken@qnx.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