Summary: | fcfreetype.c has wrong syntax making compilation impossible | ||
---|---|---|---|
Product: | fontconfig | Reporter: | Sergei Steshenko <sergstesh> |
Component: | library | Assignee: | Keith Packard <keithp> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | blocker | ||
Priority: | high | CC: | stush.halffull |
Version: | 2.3 | ||
Hardware: | x86 (IA32) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: |
'configure' log file
created by 'configure' Makefile overall build log file |
Description
Sergei Steshenko
2006-08-12 13:10:54 UTC
Created attachment 6536 [details]
'configure' log file
Created attachment 6537 [details]
created by 'configure' Makefile
Created attachment 6538 [details]
overall build log file
See how 'configure' and 'make' are called. Almost everything should be 'local',
i.e. from places my script defined, not from system locations.
Anybody ? This is fixed on the 2.4 branch; freetype changed quite a bit (In reply to comment #5) > This is fixed on the 2.4 branch; freetype changed quite a bit If I understand correctly, it is impossible to compile fontconfig-2.3.2 in principle - that's because FT_FREETYPE_H FT_INTERNAL_OBJECTS_H FT_TRUETYPE_TABLES_H FT_SFNT_NAMES_H FT_TRUETYPE_IDS_H FT_TYPE1_TABLES_H FT_INTERNAL_STREAM_H FT_INTERNAL_SFNT_H FT_INTERNAL_TRUETYPE_TYPES_H FT_XFREE86_H macros are defined nowhere in the source tarball and there is no '#include ...' statement in fcfreetype.c file which would make the macros defined. If it's the case, could you please remove any mentioning of fontconfig-2.3.2 from he project page ? It is really confusing. If it is not the case, could you please explain how/(where from) FT_FREETYPE_H FT_INTERNAL_OBJECTS_H FT_TRUETYPE_TABLES_H FT_SFNT_NAMES_H FT_TRUETYPE_IDS_H FT_TYPE1_TABLES_H FT_INTERNAL_STREAM_H FT_INTERNAL_SFNT_H FT_INTERNAL_TRUETYPE_TYPES_H FT_XFREE86_H macros get their values ? This is fixed in on the 2.4 branch. |
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.