when linking with -bdirect libXft is broken and makes the X server not to start. telling it can't find fonts. similar problems with libXt and libXfont. with -bdirect some application like emacs, xpdf, xdvi, gv, fails with: Error: Unresolved inheritance operation the should be another error too in some lib (i don't know) because xedit fails with the same previous error, even after filtering the flags on xft, xfont and xt.
Here is what you got with -bdirect enabled for libXfont (taken from a diff of two logfiles): +Could not init font path element /usr/share/fonts/misc, removing from list! +Could not init font path element /usr/share/fonts/Type1, removing from list! +Could not init font path element /usr/share/fonts/TTF, removing from list! +Could not init font path element /usr/share/fonts/ttf-bitstream-vera, removing from list! +Could not init font path element /usr/share/fonts/75dpi, removing from list! +Could not init font path element /usr/share/fonts/100dpi, removing from list! + +Fatal server error: +could not open default font 'fixed' If there is any way I could help to find the problem, just ask. Oh, and should we do one bugreport for each lib, I have no problems (maybe becouse I don't use those other applications) except for libXfont, and even if the problems is similar (at least in the sense "use -bdirect and they will not work") they may be very unlike each other? I think it is better with one "tracking-bug" if central bugreport feels needed is needed, also easier to search with seperated bugs.
Oh, and Petrizio is wrong, it is libXfont (as stated by me above) that kills xorg-server, it is the only package I have compiled without -bdirect for the moment of the libX*....
you're right. libXfont for X server start and libXt for xpdf and friend error. (changed the summary)
believed to be fixed in Xfont head, can you test?
i'm going to close this as bdirect (even experimental) is dropped by glibc/binutils
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.