I thought that Marc had said in his initial message that he installed xfree86 (i.e. XFree86-4.3.0) when he did his initial installation. Would this cause the same problem?
On Fri, 2003-06-13 at 13:56, Benjamin Reed wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > (I'm moving this to the fink-devel list, this is an issue for packagers.) > > Alexander Hansen wrote: > > > #0 0x0088c2b8 in FT_New_Face_From_SFNT > > #1 0x0088c58c in FT_New_Face_From_FOND > > #2 0x0088c3a0 in FT_New_Face_From_Suitcase > > #3 0x0088c83c in FT_New_Face > > #4 0x0049b074 in FcFreeTypeQuery > > #5 0x0049ac2c in FcFileScan > > #6 0x0049ae6c in FcDirScan > > #7 0x00495cd0 in FcConfigBuildFonts > > #8 0x0049bb5c in FcInitLoadConfigAndFonts > > #9 0x0049bbc0 in FcInit > > > > I'd be inclined to suspect some kind of conflict between the XFree86 > > builtin freetype libraries and those from the freetype* packages. > > Yes, and this is something that is going to get worse before it gets better. > > The problem, really, is the existence of freetype at all; depending on > the X server you're using, it can either cause problems or it won't. > > The reason is that FT_New_Face is a symbol that only exists in freetype > 2.1.3 or higher. > > XFree86 4.2.1 (which includes Apple X11) comes with freetype 2.0.9 I > believe (at least, it comes with something older than 2.1.3). If you > have it and the Fink freetype2 package installed, it's a crap shoot as > to which symbols you get, depending on include paths and other things. > > For example, say I have libfoo, that links against X11's freetype > because of the lib path used at compile time. It has no FT_New_Face. > Then I have libbar, that links against freetype 2.1.3, so it has the > FT_New_Face symbol. > > If I link application baz against libfoo and libbar, it will end up > following the library dependencies of libfoo and libbar, which will make > it load symbols from one or both libraries, which results in either > mixing and matching symbols (I think, anyways, if -bind_at_load is > enabled), loading the symbols from libfoo (which means libbar won't be > able to access the FT_New_Face from freetype), or loading the symbols > from libbar, which would work, since freetype 2.1.3 is > backwards-compatible with binaries built against 2.0.9. > > This is really ugly, and the only way I know of to truly clean it up is > to make sure everything is using one specific freetype library when > linking, which is gonna take a *lot* of manual work messing with include > and library paths. > > - -- > Benjamin Reed a.k.a. Ranger Rick -- http://ranger.befunk.com/ > Odelay IS a word, just look it up in the Becktionary! > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.2.2 (Darwin) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQE+6hBiUu+jZtP2Zf4RAslXAKCVxwqGAHB3Pyy6gFTfke0o2kny8wCgoKrY > HJ/rLbuTsp286EBIpUi/YjI= > =pL9T > -----END PGP SIGNATURE----- > > > > ------------------------------------------------------- > This SF.NET email is sponsored by: eBay > Great deals on office technology -- on eBay now! Click here: > http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 > _______________________________________________ > Fink-devel mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/fink-devel -- Alexander K. Hansen Associate Research Scientist, Columbia University, visiting MIT PSFC Levitated Dipole Experiment http://www.psfc.mit.edu/LDX ------------------------------------------------------- This SF.NET email is sponsored by: eBay Great deals on office technology -- on eBay now! Click here: http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
