failure building www/webkit-gtk2 on 8.2-STABLE

[Koop Mast]

On 1-12-2011 14:23, William Bulley wrote:
> According to Robert Bonomi<bonomi at mail.r-bonomi.com>  on Wed, 11/30/11 at 16:12:
>>>  From owner-freebsd-questions at freebsd.org  Wed Nov 30 09:14:56 2011
>>> Date: Wed, 30 Nov 2011 10:12:23 -0500
>>> From: William Bulley<web at umich.edu>
>>> To: freebsd-questions at freebsd.org
>>> Cc: gnome at freebsd.org
>>> Subject: failure building www/webkit-gtk2 on 8.2-STABLE
>>>
>>> This is a freshly csup'd ports tree as of 11/24/2011 and uname -a gives:
>>>
>>>     FreeBSD dell 8.2-STABLE FreeBSD 8.2-STABLE #0: Sun May 29 08:36:55 EDT 2011
>>>     root at dell:/usr/obj/usr/src/sys/DELL  amd64
>>>
>>> When I try to "make install" in www/xxxterm this is what I get:
>>>
>>> ===>    xxxterm-1.518 depends on file: /usr/local/bin/perl5.14.1 - found
>>> ===>    xxxterm-1.518 depends on file: /usr/local/bin/intltool-extract - found
>>> ===>    xxxterm-1.518 depends on executable: pkg-config - found
>>> ===>    xxxterm-1.518 depends on shared library: gnutls.47 - found
>>> ===>    xxxterm-1.518 depends on shared library: soup-2.4 - found
>>> ===>    xxxterm-1.518 depends on shared library: webkitgtk-1.0 - not found
>> *THIS* 'not found' indicates the linking (at least) of the exuecutable will
>> probably fail.
> Thanks for the reply.  This knowledge is not all that useful.  The process of
> making this port will, of course, make all dependencies of this port.  By not
> finding that item forces the installation of www/webkit-gtk2 below.  This is
> not an error.
>
>>> ===>     Verifying install for webkitgtk-1.0 in /usr/ports/www/webkit-gtk2
>>> ===>   Building for webkit-gtk2-1.4.3
>>> gmake  all-am
>>> gmake[1]: Entering directory `/usr/ports/www/webkit-gtk2/work/webkit-1.4.3'
>>>    GEN    WebKit-1.0.gir
>>> /usr/local/bin/gmkdir -p ./.deps/DerivedSources
>>> /usr/include/machine/endian.h:123: syntax error, unexpected '{' in ' return (__extension__ ({ register __uint64_t __X = (_x); __asm ("bswap %0" : "+r" (__X)); __X; }));' at '{'
>>> /usr/include/machine/endian.h:123: syntax error, unexpected ';' in ' return (__extension__ ({ register __uint64_t __X = (_x); __asm ("bswap %0" : "+r" (__X)); __X; }));' at ';'
>>> /usr/include/machine/endian.h:130: syntax error, unexpected '{' in ' return (__extension__ ({ register __uint32_t __X = (_x); __asm ("bswap %0" : "+r" (__X)); __X; }));' at '{'
>>> /usr/include/machine/endian.h:130: syntax error, unexpected ';' in ' return (__extension__ ({ register __uint32_t __X = (_x); __asm ("bswap %0" : "+r" (__X)); __X; }));' at ';'
>> _these_ errors may be a separate issue   They indicate an incompatibility
>> between the code and the -compiler- being used.  This could be an artifact
>> of other errors, like the one implied below, or they could be from unrelated
>> causes.   Eliminate the other errors, and see if this remains.
> The port maintainers are responsible for assuring the compiler matches the
> code, and that the code compiles with that compiler.  This is clearly an
> error, but one that I have no idea how to fix.
>
>>> Source/WebKit/gtk/webkit/webkitversion.h:33: Warning: WebKit: symbol='WEBKITGTK_API_VERSION': Unknown namespace for symbol 'WEBKITGTK_API_VERSION'
>> This is "probably" directly related to the 'not found' error above.
> Not so sure about that.  But again, how is this (and other errors) to be
> fixed?  Why don't the port maintainers respond to this thread?
>
>>> /usr/ports/www/webkit-gtk2/work/webkit-1.4.3/tmp-introspectiHsaMf/WebKit-1.0.o(.data+0x2e8): undefined reference to `webkit_dom_html_media_element_get_type'
>>> /usr/ports/www/webkit-gtk2/work/webkit-1.4.3/tmp-introspectiHsaMf/WebKit-1.0.o(.data+0x3c0): undefined reference to `webkit_dom_media_error_get_type'
>>> /usr/ports/www/webkit-gtk2/work/webkit-1.4.3/tmp-introspectiHsaMf/WebKit-1.0.o(.data+0x450): undefined reference to `webkit_dom_time_ranges_get_type'
>> as are all these.
> Again, not so sure about that.
>
>>> Can anyone tell me what is going on here and how I can correct it?
>>> Can it be that this port does not build correctly on AMD hardware?
> Again, thanks for the reply, but it doesn't get me all that much closer
> to getting this port built.  Anyone else have any ideas or pointers?
>
> Regards,
>
> web...
>

Can you check if you got the video option selected? "make config" if you 
haven't, please select it and do a "make clean"  before trying to build it.

-Koop