Am Dienstag, 5. Juni 2007 19:11 schrieb Koji Yokota:
> Georg Baum wrote:
> > Jean-Marc Lasgouttes wrote:
> >> - how can we test whether freebsd's wchat_t support is good enough?
> > First of all is wchar_t really 32 bit on freebsd? I know that some 
unices
> > have 16bit wchar_t, IIRC AIX. This could be tested with a small test
> > program that simply prints sizeof(wchar_t). I know that the configure 
test
> > is supposed to find that out, but who knows.
> 
> I tried this and the result was sizeof(wchar_t) = 4.

I expected that, but it is always better to be 100% sure.

> > I also see that it is installed in /usr/local. If that means that he
> > compiled himself from source then I would guess that something went 
wrong
> > with the configuration of the compiler. gcc has tons of configuration
> > options, and with many combinations you can get an unusable result 
(BTDT).
> 
> This gcc 4.1 was installed via ports (a package management system) as 
> the default gcc used by the system is gcc 3.4.6. Since it is tested by 
> the port maintainer and used by many people in the same setup, I think 
> it is fairly reliable (although it may not be as solid as the system 
gcc).

I tend to agree. Just for completeness, could you try to compile LyX with 
the system gcc please? gcc 3.4.x is supposed to be good enough as well, 
and since it uses the same abi as gcc 4.1 you can even use it with 
libraries compiled with g++ 4.1.

> > Another thing to try is to force Enricos facet implementation by 
applying
> > the attached patch. Does that change anything?
> 
> Unfortunately, this didn't change anything.

That means that the gcc locale facets are probably not the problem.

>  > Then Koji could fire up a debugger, set a breakpoint in
>  > parse_printf_directive() and report what the result of the narrow() 
call
>  > is.
> 
> I will try this and post the result soon.

I believe now that this is the only way to find out the problem. Don't be 
surprised if you seem to see wild jumps in the debugger, when I debugged 
the locale code last time there was a lot of inlined stuff that gdb could 
not relate to the correct line in the correct file.


Georg

Reply via email to