It is rather difficult to participate in a discussion where only half of it is showing up and quoting is done alternatingly top and bottom, but I think I know what is going on, or at least half of it.
I'll use the mailing list standard method and mix my answer with the quotes. Alexander K. Hansen wrote: > Benjamin Shive wrote: >> Looks like it's the same for me too (running 10.4.9). Please let me >> know if there's any more information I can provide that will help - or >> things to try. >> >> % fink dumpinfo -fallversions freetype219 >> Information about 7072 packages read in 17 seconds. >> allversions: >> bi 2.2.1-4 This version of freetype2 does not allow the use of freetype internal headers any more. These used to be in the header file nicknamed FT_INTERNAL_OBJECTS_H, and that is the macro the compiler is complaining about here: [] >>>> gcc -DHAVE_CONFIG_H -I. -I. -I.. >>>> -I/sw/lib/freetype219/include/freetype2 >>>> -I/sw/lib/freetype219/include -DFONTCONFIG_PATH=\"/etc/fonts\" -I.. >>>> -I../src -I/sw/include -fno-common -g -c fcfreetype.c -fno-common >>>> -DPIC -o .libs/fcfreetype.o >>>> fcfreetype.c:53:10: error: #include expects "FILENAME" or <FILENAME> >>>> fcfreetype.c: In function 'FcVendorFoundry': While the cause of this is clear - the fontconfig2-dev package in stable has been allowed to slowly rot, whereas all fixes have gone into the version in unstable - it is not clear to me why your build of fontconfig2-dev picks up freetype219 at all. The package maintainer did indeed intend this to happen, and he put some pious wish to that effect in the form of BuildDepends: freetype219 export FREETYPE_CONFIG="%p/lib/freetype219/bin/freetype-config" into the package description. But this has never worked for me. When I build this version of fontconfig2-dev, I get instead of your compiler line the following: gcc -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/X11R6/include -I/usr/X11R6/include/freetype2 -DFONTCONFIG_PATH=\"/etc/fonts\" -I.. -I../src -I/sw/include -fno-common -g -c fcfreetype.c -fno-common -DPIC -o .libs/fcfreetype.o This gives no error, because the old version of freetype2 from Apple's X11 does still contain the private headers. I am not sure if I really want to find out why this happens in the way it does or whether we should spend any energy on fixing that version of fontconfig2-dev in stable. It would probably be better to see if version 2.3.2-13 from unstable wouldn't do a better job in stable, too. -- Martin ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Fink-beginners mailing list Fink-beginners@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-beginners
