Around 18 o'clock on Feb 19, Juliusz Chroboczek wrote: > Why's that? Is setjmp/longjmp verboten in modules, or is FreeType > doing something non-portable?
I don't know. Setjmp and longjmp are magic that is partially supported by the compiler, so I fear they will be broken by the XFree86 loader architecture. But, I admit there's no fundemental reason they shouldn't work. I haven't been able to get the loadable server running with gdb since this problem surfaced; I'll see if I can't build my own version of gdb and figure out where the segfault is coming from. > Something that you've suggested before, and that I'm inclined to do > after 4.3, is to link (dynamically) the core server with FreeType, and > make a subset of FreeType an optional part of the fonts interface for > modules. Alternatively, you could have the FreeType module dlopen the FreeType library and resolve the necessary symbols by hand. Finally, if we could resolve the conflict between xtt and freetype, we could eliminate all of the font loaders aside from freetype and just link that statically into the server -- it supports all of the font file formats we're interested in, so there's no real reason to have extensibility beyond what it provides. -keith _______________________________________________ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
