[kde-freebsd] LANG setting of UTF-16 causes automoc to crash

[Max Brazhnikov]

On Thu, 09 Sep 2010 13:51:22 -0300, Raphael Kubo da Costa wrote:
> At Thu, 9 Sep 2010 11:26:38 -0400,
> 
> Dwayne MacKinnon wrote:
> > Hi all,
> > 
> > I ran into this while trying to upgrade to 4.5.1:
> > 
> > Generating moc_FakeBackend.cpp
> > ��/
> > automoc4: process for
> > /usr/ports/x11/kdelibs4/work/kdelibs-4.5.1/build/kdecore/moc_FakeBackend.
> > cpp failed: Unknown error
> > pid to wait for: 0
> > Generating moc_HelperProxy.cpp
> > Generating moc_kauthactionreply.cpp
> > /usr/ports/x11/kdelibs4/work/kdelibs-4.5.1/kdecore/auth/kauthactionreply.
> > h:0: Warning: No relevant classes found. No output generated.
> > returning failed..
> > gmake[2]: *** [kdecore/CMakeFiles/kdecore_automoc] Error 1
> > gmake[2]: Leaving directory
> > `/usr/ports/x11/kdelibs4/work/kdelibs-4.5.1/build' gmake[1]: ***
> > [kdecore/CMakeFiles/kdecore_automoc.dir/all] Error 2 gmake[1]: Leaving
> > directory `/usr/ports/x11/kdelibs4/work/kdelibs-4.5.1/build' gmake: ***
> > [all] Error 2
> > *** Error code 1
> > 
> > Stop in /usr/ports/x11/kdelibs4.
> > 
> > (Generated using -DDISABLE_MAKE_JOBS -DCMAKE_VERBOSE)
> > 
> > The two weird characters made me wonder if my choice of default character
> > encoding (I had en_CA.UTF-16 set as $LANG) was the problem. I changed it
> > to UTF-8 and the problem vanished. I also verified it with en_US.UTF-16.
> > 
> > I'll leave it up to wiser KDE heads then mine if this should be reported
> > upstream.
> 
> I'm still unsure whether it is the LANG setting itself that's causing
> this problem, but unless the ports guys say otherwise, I'd take this
> to the kde-buildsystem mailing list in KDE itself.

I doubt whether *.UTF-16 locales make sense on FreeBSD, `locale -a' gives 
nothing for UTF-16.

Max