Re: xtt/freetype grumpy
Juliusz Chroboczek <[EMAIL PROTECTED]> writes: > In 4.1, you could load them simultaneously, in which case the first > one loaded would be the one that manages TrueType fonts. In 4.2, > due to an accidental name clash, the loader will not allow you to > load both. > > In 4.3, if two modules register for the same type of fonts, a > warning will be printed to the log. > > Hope this explains things, Yep. That's what I figured. Since it's going to cause people's X configurations to break now, maybe the configuration script shoud explicitly force a selection. I think you'd do something like this in xserver-xfree86.templates : Template: xserver-xfree86/config/xtt_versus_freetype Type: select Choices: freetype, xtt The freetype and xtt modules should not be enabled at the same time, as they are incompatible. The freetype module should be used for Western languages and anti-aliased font support; the xtt module should be used for East Asian character set support (specifically, for CID-keyed fonts). . Please select one or the other. I think I made it work, after a fashion, but I don't think anyone would want my nasty patch (I'm certainly not installing on my system!). Russell -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: xtt/freetype grumpy
Juliusz Chroboczek <[EMAIL PROTECTED]> writes: > In 4.1, you could load them simultaneously, in which case the first > one loaded would be the one that manages TrueType fonts. In 4.2, > due to an accidental name clash, the loader will not allow you to > load both. > > In 4.3, if two modules register for the same type of fonts, a > warning will be printed to the log. > > Hope this explains things, Yep. That's what I figured. Since it's going to cause people's X configurations to break now, maybe the configuration script shoud explicitly force a selection. I think you'd do something like this in xserver-xfree86.templates : Template: xserver-xfree86/config/xtt_versus_freetype Type: select Choices: freetype, xtt The freetype and xtt modules should not be enabled at the same time, as they are incompatible. The freetype module should be used for Western languages and anti-aliased font support; the xtt module should be used for East Asian character set support (specifically, for CID-keyed fonts). . Please select one or the other. I think I made it work, after a fashion, but I don't think anyone would want my nasty patch (I'm certainly not installing on my system!). Russell -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: xtt/freetype grumpy
RN> However, X still refused to start on account of a duplicate symbol for RN> freetype in /usr/X11R6/lib/modules/fonts/libxtt.a. Removing xtt from RN> the configuration "fixed" the problem. That's okay. X-TT and FreeType have always been mutually exclusive. They should not be loaded simultaneously. In 4.1, you could load them simultaneously, in which case the first one loaded would be the one that manages TrueType fonts. In 4.2, due to an accidental name clash, the loader will not allow you to load both. In 4.3, if two modules register for the same type of fonts, a warning will be printed to the log. Hope this explains things, Juliusz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: xtt/freetype grumpy
RN> However, X still refused to start on account of a duplicate symbol for RN> freetype in /usr/X11R6/lib/modules/fonts/libxtt.a. Removing xtt from RN> the configuration "fixed" the problem. That's okay. X-TT and FreeType have always been mutually exclusive. They should not be loaded simultaneously. In 4.1, you could load them simultaneously, in which case the first one loaded would be the one that manages TrueType fonts. In 4.2, due to an accidental name clash, the loader will not allow you to load both. In 4.3, if two modules register for the same type of fonts, a warning will be printed to the log. Hope this explains things, Juliusz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
gcc 3.1 vs XF4.2
Hello, Has anyone else tried to rebuild Branden's test xfree86 4.2.0-0pre1v1 packages against the current gcc 3.1.1? On debian ppc sid, I find that while the build appears to work in general there is at least one glitch compared to the gcc 2.95.4 build. I see under the gcc 3.1 packages the following failure in /var/log/XFree86.0.log (II) LoadModule: "GLcore" (II) Loading /usr/X11R6/lib/modules/extensions/libGLcore.a No symbols found in this module Failed to load debug_xform.o (EE) Failed to load /usr/X11R6/lib/modules/extensions/libGLcore.a (II) UnloadModule: "GLcore" (EE) Failed to load module "GLcore" (loader failed, 270336000) When I do nm on the gcc 3.1 built libGLcore.a I see... debug_xform.o: compared to... debug_xform.o: t gcc2_compiled. for the gcc 2.95.4 built one. Anyone had any idea why the loader should be having such problems just because one of the object files used to create libGLcore.a has no symbols in it? Thanks for advice. Jack -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
