Issue building pango on FreeBSD 10.0 amd64 (r226893) with clang

Brandon Falk falkman at
Sat Oct 29 16:45:58 UTC 2011

On 10/29/2011 1:51 AM, Brandon Falk wrote:
> I'm currently getting this issue building pango (everything, including world
> and kernel, have been built with clang):
> /usr/ports/x11-toolkits/pango/work/pango-1.28.4/pango/pango-color-table.h:762:
> syntax error, unexpected identifier in '    guint16 name_offset;' at
> 'guint16'
> /usr/ports/x11-toolkits/pango/work/pango-1.28.4/pango/pango-color-table.h:768:
> syntax error, unexpected identifier, expecting ',' or ';' in 'static const
> ColorEntry color_entries[] = {' at 'color_entries'
> /usr/ports/x11-toolkits/pango/work/pango-1.28.4/pango/pango-language-sample-table.h:52:
> syntax error, unexpected identifier in 'LANGUAGE(' at 'LANGUAGE'
>    CCLD
>    CCLD
> /usr/bin/ld: /usr/local/lib/libXft.a(xftdpy.o): relocation R_X86_64_32
> against `_XftDisplayInfo' can not be used when making a shared object;
> recompile with -fPIC
> /usr/local/lib/libXft.a: could not read symbols: Bad value
> clang: error: linker command failed with exit code 1 (use -v to see
> invocation)
> gmake[4]: *** [] Error 1
> gmake[4]: *** Waiting for unfinished jobs....
> g-ir-scanner: Pango: warning: 57 warnings suppressed (use --warn-all to see
> them)
> gmake[4]: Leaving directory
> `/usr/ports/x11-toolkits/pango/work/pango-1.28.4/pango'
> gmake[3]: *** [all-recursive] Error 1
> gmake[3]: Leaving directory
> `/usr/ports/x11-toolkits/pango/work/pango-1.28.4/pango'
> gmake[2]: *** [all] Error 2
> gmake[2]: Leaving directory
> `/usr/ports/x11-toolkits/pango/work/pango-1.28.4/pango'
> gmake[1]: *** [all-recursive] Error 1
> gmake[1]: Leaving directory
> `/usr/ports/x11-toolkits/pango/work/pango-1.28.4'
> gmake: *** [all] Error 2
> *** Error code 1
> Any ideas? Perhaps it's just some crazy temporary issue? I'll look into it
> tomorrow, but I gotta catch some sleep.
> Thanks in advance,
> Brandon Falk
> _______________________________________________
> freebsd-hackers at mailing list
> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe at"

(I'm the original poster... just on a different email)

I went to bed, and woke up, and the port(s) were fixed and the issues 
went away.

[NOTE: This was not a clang issue, gcc acted the same way]

To continue with my build (of vim which has now succeeded), I had to 
deinstall and reinstall the following ports (due to getting the same 
errors on these ports):


Perhaps I'll have the same issue on other ports, and I'll have to 
reinstall them. But I doubt anyone has really experienced this issue, as 
it seems like it was a small window in ports where this error occurred? 
Or perhaps it's a 10.0 issue that's been ongoing and discussed elsewhere.

Anyways... this is FIXED.

Brandon Falk

More information about the freebsd-hackers mailing list