On Fri, Sep 13, 2002 at 10:22:09AM +0100, Josef Karthauser wrote: > I've not looked too deeply as to the cause, but I'm hoping someone here > can shed some light on it for me. I'm having trouble building openjade > from the ports on -current. The build bombs out with: > > LangObj.cxx: In member function `virtual bool > RefLangObj::areEquivalent(const > StringC&, const StringC&, short unsigned int) const': > LangObj.cxx:122: `wcsxfrm' undeclared (first use this function)
wcsxfrm() is not implemented. > LangObj.cxx:122: (Each undeclared identifier is reported only once for > each > function it appears in.) > LangObj.cxx: In member function `virtual bool RefLangObj::isLess(const > StringC&, const StringC&) const': > LangObj.cxx:146: `wcscoll' undeclared (first use this function) wcscoll() is not implemented. > gmake[2]: *** [LangObj.lo] Error 1 > gmake[2]: Leaving directory > `/data/ports/workdirs/usr/ports/textproc/openjade/work/openjade-1.3.1/style' > gmake[1]: *** [style] Error 2 > gmake[1]: Leaving directory > `/data/ports/workdirs/usr/ports/textproc/openjade/work/openjade-1.3.1' > gmake: *** [all] Error 2 > *** Error code 2 > > > Is this a known problem (it builds find under -stable), or is > something spammed at my end? Some GNU (and GNU-style) programs assume that the presence of the restartable multibyte/wide character functions (mbsrtowcs(), wcsrtombs()) means that all of the other ISO C90 Amd.1 wide character functions exist. The restartable mb/wc functions were added recently and do not exist in -stable. Making blind assumptions like this defeats the purpose of using autoconf at all.. a hack solution is probably to tell it not to use wcscoll/wcsxfrm by editing config.h. The real solution is for us to implement these functions, and for whoever wrote the autoconf gunk to be more careful. Tim To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
