Bug 302 - XORG-RELEASE-1 build failure in xc/programs/fonttosfnt/
Summary: XORG-RELEASE-1 build failure in xc/programs/fonttosfnt/
Status: RESOLVED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: * Other (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: highest blocker
Assignee: Default Bug Report Assignee
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-03-12 06:00 UTC by Roland Mainz
Modified: 2011-10-15 15:49 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Roland Mainz 2004-03-12 06:00:54 UTC
It seems that today's XORG-RELEASE-1 tree does not build on (SuSE 8.2)
Linux/x86:
-- snip --
gcc -m32 -O2 -fno-strength-reduce -fno-strict-aliasing -ansi -pedantic -Wall
-Wpointer-arith -Wstrict-prototypes                     -Wmissing-prototypes
-Wmissing-declarations                      -Wredundant-decls -Wnested-externs
-Wundef   -I../../exports/include/X11/fonts -I/usr/include/freetype2
-I/usr/include/freetype2/config  -I../../exports/include/X11  -I../..
-I../../exports/include   -Dlinux -D__i386__
-D_POSIX_C_SOURCE=199309L                          -D_POSIX_SOURCE
-D_XOPEN_SOURCE                            -D_BSD_SOURCE
-D_SVID_SOURCE                             
-D_GNU_SOURCE                            -DFUNCPROTO=15 -DNARROWPROTO    
-DXFREE86_FT2    -c -o read.o read.c
read.c: In function `readFile':
read.c:108: error: `BDF_PropertyRec' undeclared (first use in this function)
read.c:108: error: (Each undeclared identifier is reported only once
read.c:108: error: for each function it appears in.)
read.c:108: error: parse error before "prop"
read.c:139: warning: implicit declaration of function `FT_Get_BDF_Property'
read.c:139: error: `prop' undeclared (first use in this function)
read.c:140: error: `BDF_PROPERTY_TYPE_ATOM' undeclared (first use in this
function)
read.c:199: error: `BDF_PROPERTY_TYPE_INTEGER' undeclared (first use in this
function)
make[4]: *** [read.o] Error 1
make[4]: Leaving directory
`/home/gismobile/projects/xorg/freetype_update/xorg_release1/xc/programs/fonttosfnt'
make[3]: *** [all] Error 2
make[3]: Leaving directory
`/home/gismobile/projects/xorg/freetype_update/xorg_release1/xc/programs'
make[2]: *** [all] Error 2
make[2]: Leaving directory
`/home/gismobile/projects/xorg/freetype_update/xorg_release1/xc'
make[1]: *** [World] Error 2
make[1]: Leaving directory
`/home/gismobile/projects/xorg/freetype_update/xorg_release1/xc'
make: *** [World] Error 2
-- snip --
Comment 1 Roland Mainz 2004-03-13 16:02:06 UTC
The following hack works around the problem:
-- snip --
Index: xc/config/cf/linux.cf
===================================================================
RCS file: /cvs/xorg/xc/config/cf/linux.cf,v
retrieving revision 1.1.4.5.2.4
diff -u -r1.1.4.5.2.4 linux.cf
--- a/xc/config/cf/linux.cf     11 Mar 2004 09:16:51 -0000      1.1.4.5.2.4
+++ b/xc/config/cf/linux.cf     13 Mar 2004 23:56:08 -0000
@@ -144,8 +144,8 @@
 #  define BuildHtmlManPages            NO
 
 /* we build-depend on libfreetype6-dev (FreeType 2.x) */
-#   define BuildFreetype2Library       NO
-#   define HasFreetype2                        YES
+#   define BuildFreetype2Library       YES
+#   define HasFreetype2                        NO
 /* m68k has no 2.4 kernel yet */
 #   ifndef Mc68020Architecture
 #    define HasLinuxInput              YES
@@ -491,7 +491,7 @@
 #endif
 
 #ifndef HasFreetype2
-# define HasFreetype2          YES
+# define HasFreetype2          NO
 #endif
-- snip --

One solution would be to add a way to statically link with the freetype version
in the tree and make that the default (this would also get rid of the (very
unfortunate) situation that old FreeType2 library versions are buggy - which
affects the quality and stability of the resulting product).
Comment 2 Egbert Eich 2004-03-15 06:13:06 UTC
On SUSE 8.2 you either need to update freetype or use 
#define HasFreetype2 NO 
to build the version that's in the tree. In this case the version it the tree
will be linked into the libfreetype.a module statically.


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.