On Mon, Dec 06, 2004 at 07:18:26PM +0100, Mario Kemper wrote:
> On Mon, Dec 06, 2004 at 12:42:14AM +0100, Krister Walfridsson wrote:
> > 
> > 
> > Yes, using gmake makes this problem go away.
> > 
> > But the build on my test-machine then fails with:
> >   cc -c -Wall -Wno-switch -Winline -Wmissing-prototypes -Wsign-compare  
> >   -Wundef -Wstrict-prototypes -Wpointer-arith -Wshadow  
> >   -Wmissing-declarations -O2 -Dunix -I/usr/pkg/include -I/usr/include 
> >   -I/usr/pkg/include -I/usr/include -Demacs -I. -DHAVE_CONFIG_H 
> >   -I/usr/pkg/include -I/usr/pkgsrc/editors/xemacs-current/work 
> >   -I/usr/X11R6/include mule-canna.c
> >   mule-canna.c: In function `Fcanna_initialize':
> >   mule-canna.c:441: `jrBeepFunc' undeclared (first use in this function)
> >   mule-canna.c:441: (Each undeclared identifier is reported only once
> >   mule-canna.c:441: for each function it appears in.)
> >   mule-canna.c:447: warning: implicit declaration of function 
> >   `wcKanjiControl'
> > 
> Canna support seems to be broken. It shouldn't be enabled by default
> but it looks like the new options.mk enables it unconditionally.

This comes from:

mk/defaults/mk.conf
USE_CANNA?= YES

mk/defaults/obsolete.mk
.if defined(USE_CANNA) && !empty(USE_CANNA:M[yY][eE][sS])
PKG_DEFAULT_OPTIONS+=   canna
.endif

It seems this has been default for a long time. Perhaps we should
just remove 'canna' from PKG_SUPPORTED_OPTIONS in xemacs-current's
options.mk?

 Thomas