As I have no knowledge about Mac OS X, I forwarded your bug
report to [EMAIL PROTECTED] which the mailing list
discussing on the new font-backend feature of
emacs-unicode-2 branch.  If you have not yet been subscribed
to it and want to join, please send the request to Eli
([EMAIL PROTECTED]).

---
Kenichi Handa
[EMAIL PROTECTED]

In article <[EMAIL PROTECTED]>, Peter Dyballa <[EMAIL PROTECTED]> writes:

> When I configure with this option, pkg-config returns quite correctly  
> for CFLAGS or LIBS:

>       -I/usr/local/include -I/usr/local/include/freetype2 -I/usr/X11R6/ 
> include
>       -L/usr/local/lib -L/usr/X11R6/lib -lfreetype -lXft -lXrender - 
> lfontconfig

> So in the end it comes to this gcc invocation:

>       gcc -I/sw/include -L/sw/lib -c -no-cpp-precomp -I/usr/include/ 
> openssl -I/usr/local/include/freetype2 -I/usr/local/include -I/sw/ 
> include/libpng12 -I/sw/include -Demacs -DHAVE_CONFIG_H -DUSE_LUCID  - 
> I. -I/Users/pete/Quellen/Emacs_CVS/emacs-23.0.0_NS-9.0pre3/src -I/usr/ 
> X11R6/include -I/usr/local/include -I/usr/local/include/freetype2 -I/ 
> usr/X11R6/include -fpascal-strings -DMAC_OSX -I../mac/src -Dtemacs  
> ftfont.c

> Instead of using /usr/local/include/ft2build.h for fontconfig and  
> freetype2 in /usr/local, /usr/X11R6/include/ft2build.h is found! And  
> ftfont.c can't be compiled:

>       ftfont.c: In function ‘ftfont_pattern_entity’:
>       ftfont.c:129: error: ‘FC_WEIGHT_REGULAR’ undeclared (first use in  
> this function)
>       ftfont.c:129: error: (Each undeclared identifier is reported only once
>       ftfont.c:129: error: for each function it appears in.)
>       ftfont.c:135: error: ‘FC_WIDTH’ undeclared (first use in this  
> function)
>       ftfont.c: In function ‘ftfont_list_generic_family’:
>       ftfont.c:191: error: ‘FC_WIDTH’ undeclared (first use in this  
> function)
>       ftfont.c: In function ‘ftfont_list’:
>       ftfont.c:439: error: ‘FC_WIDTH’ undeclared (first use in this  
> function)
>       ftfont.c:509: error: ‘FC_WEIGHT_REGULAR’ undeclared (first use in  
> this function)
>       make[2]: *** [ftfont.o] Error 1

> The configure invocation was:  ./configure --enable-font-backend -- 
> without-ns --without-carbon --with-x --without-sound --without-pop -- 
> with-xpm --with-jpeg --with-tiff --with-gif --with-png --enable- 
> locallisppath=... CPPFLAGS="-no-cpp-precomp -I/usr/include/openssl -I/ 
> usr/local/include/freetype2 -I/usr/local/include -I/sw/include/ 
> libpng12 -I/sw/include"


> Mac OS X has its own, elderly, X11R6. Its libfreetype is obviously  
> too old. Therefore I provided fontconfig (2.3.95) and libfreetype2  
> (2.2.1) in /usr/local.

> To me gcc's behaviour looks like a bug. When invoked with -v on  
> ftfont.c I get:

>       ignoring nonexistent directory "/usr/lib/gcc/powerpc-apple- 
> darwin8/4.0.1/../../../../powerpc-apple-darwin8/include"
>       ignoring duplicate directory "/usr/local/include"
>         as it is a non-system directory that duplicates a system directory
>       ignoring duplicate directory "/sw/include"
>       ignoring duplicate directory "/Users/pete/Quellen/Emacs_CVS/ 
> emacs-23.0.0_NS-9.0pre3/src"
>       ignoring duplicate directory "/usr/local/include"
>         as it is a non-system directory that duplicates a system directory
>       ignoring duplicate directory "/usr/local/include/freetype2"
>       ignoring duplicate directory "/usr/X11R6/include"
>       #include "..." search starts here:
>       #include <...> search starts here:
>       /sw/include
>       /usr/include/openssl
>       /usr/local/include/freetype2
>       /sw/include/libpng12
>       .
>       /usr/X11R6/include
>       ../mac/src
>       /usr/local/include
>       /usr/lib/gcc/powerpc-apple-darwin8/4.0.1/include
>       /usr/include
>       /System/Library/Frameworks
>       /Library/Frameworks
>       End of search list.

> Is there something to make GCC follow the -I paths more accurately?

> --
> Greetings

>    Pete

> »¿ʇı̣ əsnqɐ ʇ,uɐɔ noʎ ɟı̣
> ɓuı̣ɥʇʎuɐ sı̣ pooɓ ʇɐɥʍ«




> _______________________________________________
> emacs-pretest-bug mailing list
> [email protected]
> http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug



_______________________________________________
emacs-pretest-bug mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug

Reply via email to