From: Kenichi Handa <handa@m17n.org>
Cc: emacs-devel@gnu.org
Subject: Re: [unicode branch] search.c:1537: error: 'this_pos_byte' undeclared
Date: Wed, 22 Nov 2006 10:59:28 +0900 [thread overview]
Message-ID: <E1GmhOa-0007DL-00@etlken> (raw)
In-Reply-To: <87vel8tfk2.fsf@mandala.my-fqdn.de> (message from Jhair Tocancipa Triana on Wed, 22 Nov 2006 02:50:53 +0100)
> After a cvs update today I get the following error:
> gcc -c -D_BSD_SOURCE -Demacs -DHAVE_CONFIG_H -DUSE_GTK -I. -I/home/jtocancipa/local/src/emacs_unicode_branch/emacs/src -D_BSD_SOURCE -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/freetype2 -I/usr/include/alsa -g -O2 -Wno-pointer-sign search.c
> search.c: In function 'simple_search':
> search.c:1537: error: 'this_pos_byte' undeclared (first use in this function)
> search.c:1537: error: (Each undeclared identifier is reported only once
> search.c:1537: error: for each function it appears in.)
> Shouldn't this change be applied?
> *** search.c 22 Nov 2006 02:36:14 +0100 1.174.2.32
> --- search.c 22 Nov 2006 02:44:15 +0100
> ***************
> *** 1531,1536 ****
> --- 1531,1537 ----
> {
> /* Try matching at position POS. */
> int this_pos = pos - len;
> + int this_pos_byte = pos_byte - len_byte;
> int this_len = len;
> unsigned char *p = pat;
No. That part is a code for unibyte case. The current
error is because the change in HEAD is applied to the
incorrect place in search.c. I've just installed a proper
fix.
---
Kenichi Handa
handa@m17n.org
prev parent reply other threads:[~2006-11-22 1:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-22 1:50 [unicode branch] search.c:1537: error: 'this_pos_byte' undeclared Jhair Tocancipa Triana
2006-11-22 1:59 ` Kenichi Handa [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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1GmhOa-0007DL-00@etlken \
--to=handa@m17n.org \
--cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).