From owner-freebsd-hackers@FreeBSD.ORG Sat Oct 29 16:45:58 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8E4481065687 for ; Sat, 29 Oct 2011 16:45:58 +0000 (UTC) (envelope-from falkman@gamozo.org) Received: from fireblade.netcore2k.net (fireblade.netcore2k.net [92.48.127.72]) by mx1.freebsd.org (Postfix) with ESMTP id 10B528FC08 for ; Sat, 29 Oct 2011 16:45:57 +0000 (UTC) Received: by fireblade.netcore2k.net with ESMTP id p9TGW5hM029335 ; Sat, 29 Oct 2011 17:32:07 +0100 Message-ID: <4EAC2A84.7070805@gamozo.org> Date: Sat, 29 Oct 2011 12:32:04 -0400 From: Brandon Falk User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1 MIME-Version: 1.0 To: Brandon Falk References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: Issue building pango on FreeBSD 10.0 amd64 (r226893) with clang X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Oct 2011 16:45:58 -0000 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 libpangoxft-1.0.la > CCLD libpangocairo-1.0.la > /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]: *** [libpangoxft-1.0.la] 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@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" (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): x11-fonts/libXft x11/libXi x11/libXrandr x11/libXcursor x11/libXcomposite x11/libXdamage 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. Regards, Brandon Falk