Date: Wed, 18 Sep 2013 17:40:42 +0200 From: Dominic Fandrey <kamikaze@bsdforen.de> To: Niclas Zeising <zeising@freebsd.org> Cc: ports@FreeBSD.org, x11@FreeBSD.org Subject: Re: [CFT] Update of xorg libraries and MESA Message-ID: <5239C97A.5040506@bsdforen.de> In-Reply-To: <522DE093.9080504@freebsd.org> References: <522DC3EB.4060607@freebsd.org> <522DE093.9080504@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 09/09/2013 16:52, Niclas Zeising wrote:
> On 09/09/13 14:49, Niclas Zeising wrote:
>> [Cross-posted between x11@ and ports@, please respect reply-to]
>>
>> Hi!
>> It is time once again to update parts of the FreeBSD xorg stack, and the
>> x11@ team needs YOUR help in testing!
Build of graphics/dri fails on stable/9:
FreeBSD mobileKamikaze.norad 9.2-PRERELEASE FreeBSD 9.2-PRERELEASE #0 r254957: Tue Aug 27 19:07:40 CEST 2013 root@mobileKamikaze.norad:/usr/obj/HP6510b-9/amd64/usr/src/sys/HP6510b-9 amd64
The ports tree is up to date, so is the patch (just fetched).
CC intel_screen.lo
clang: warning: argument unused during compilation: '-fno-builtin-memcmp'
clang: warning: argument unused during compilation: '-fno-builtin-memcmp'
intel_context.c:1026:14: warning: unused variable 'max_attachments' [-Wunused-variable]
const int max_attachments = ARRAY_SIZE(attachments) / 2;
^
intel_screen.c:199:6: error: use of undeclared identifier '__DRI_IMAGE_FOURCC_ARGB8888'
{ __DRI_IMAGE_FOURCC_ARGB8888, __DRI_IMAGE_COMPONENTS_RGBA, 1,
^
intel_screen.c:199:35: error: use of undeclared identifier '__DRI_IMAGE_COMPONENTS_RGBA'
{ __DRI_IMAGE_FOURCC_ARGB8888, __DRI_IMAGE_COMPONENTS_RGBA, 1,
^
intel_screen.c:202:6: error: use of undeclared identifier '__DRI_IMAGE_FOURCC_XRGB8888'
{ __DRI_IMAGE_FOURCC_XRGB8888, __DRI_IMAGE_COMPONENTS_RGB, 1,
^
intel_screen.c:202:35: error: use of undeclared identifier '__DRI_IMAGE_COMPONENTS_RGB'
{ __DRI_IMAGE_FOURCC_XRGB8888, __DRI_IMAGE_COMPONENTS_RGB, 1,
^
intel_screen.c:205:6: error: use of undeclared identifier '__DRI_IMAGE_FOURCC_YUV410'
{ __DRI_IMAGE_FOURCC_YUV410, __DRI_IMAGE_COMPONENTS_Y_U_V, 3,
^
1 warning generated.
CC intel_span.lo
intel_screen.c:205:33: error: use of undeclared identifier
'__DRI_IMAGE_COMPONENTS_Y_U_V'
{ __DRI_IMAGE_FOURCC_YUV410, __DRI_IMAGE_COMPONENTS_Y_U_V, 3,
^
clang: warning: argument unused during compilation: '-fno-builtin-memcmp'
intel_screen.c:206:19: error: use of undeclared identifier '__DRI_IMAGE_FORMAT_R8'
{ { 0, 0, 0, __DRI_IMAGE_FORMAT_R8, 1 },
^
intel_screen.c:207:19: error: use of undeclared identifier '__DRI_IMAGE_FORMAT_R8'
{ 1, 2, 2, __DRI_IMAGE_FORMAT_R8, 1 },
^
intel_screen.c:208:19: error: use of undeclared identifier '__DRI_IMAGE_FORMAT_R8'
{ 2, 2, 2, __DRI_IMAGE_FORMAT_R8, 1 } } },
^
intel_screen.c:210:6: error: use of undeclared identifier '__DRI_IMAGE_FOURCC_YUV411'
{ __DRI_IMAGE_FOURCC_YUV411, __DRI_IMAGE_COMPONENTS_Y_U_V, 3,
^
intel_screen.c:210:33: error: use of undeclared identifier
'__DRI_IMAGE_COMPONENTS_Y_U_V'
{ __DRI_IMAGE_FOURCC_YUV411, __DRI_IMAGE_COMPONENTS_Y_U_V, 3,
^
intel_screen.c:211:19: error: use of undeclared identifier '__DRI_IMAGE_FORMAT_R8'
{ { 0, 0, 0, __DRI_IMAGE_FORMAT_R8, 1 },
^
intel_screen.c:212:19: error: use of undeclared identifier '__DRI_IMAGE_FORMAT_R8'
{ 1, 2, 0, __DRI_IMAGE_FORMAT_R8, 1 },
^
intel_screen.c:213:19: error: use of undeclared identifier '__DRI_IMAGE_FORMAT_R8'
{ 2, 2, 0, __DRI_IMAGE_FORMAT_R8, 1 } } },
^
CC intel_state.lo
intel_screen.c:215:6: error: use of undeclared identifier '__DRI_IMAGE_FOURCC_YUV420'
{ __DRI_IMAGE_FOURCC_YUV420, __DRI_IMAGE_COMPONENTS_Y_U_V, 3,
^
intel_screen.c:215:33: error: use of undeclared identifier
'__DRI_IMAGE_COMPONENTS_Y_U_V'
{ __DRI_IMAGE_FOURCC_YUV420, __DRI_IMAGE_COMPONENTS_Y_U_V, 3,
^
intel_screen.c:216:19: error: use of undeclared identifier '__DRI_IMAGE_FORMAT_R8'
{ { 0, 0, 0, __DRI_IMAGE_FORMAT_R8, 1 },
^
clang: warning: argument unused during compilation: '-fno-builtin-memcmp'
intel_screen.c:217:19: error: use of undeclared identifier '__DRI_IMAGE_FORMAT_R8'
{ 1, 1, 1, __DRI_IMAGE_FORMAT_R8, 1 },
^
intel_screen.c:218:19: error: use of undeclared identifier '__DRI_IMAGE_FORMAT_R8'
{ 2, 1, 1, __DRI_IMAGE_FORMAT_R8, 1 } } },
^
fatal error: too many errors emitted, stopping now [-ferror-limit=]
20 errors generated.
gmake[6]: *** [intel_screen.lo] Error 1
gmake[6]: *** Waiting for unfinished jobs....
gmake[6]: Leaving directory `/tmp/obj/mobileKamikaze.norad/amd64/usr/ports/graphics/dri/work/Mesa-9.1.6/src/mesa/drivers/dri/i915'
gmake[5]: *** [all-recursive] Error 1
gmake[5]: Leaving directory `/tmp/obj/mobileKamikaze.norad/amd64/usr/ports/graphics/dri/work/Mesa-9.1.6/src/mesa/drivers/dri'
gmake[4]: *** [all-recursive] Error 1
gmake[4]: Leaving directory `/tmp/obj/mobileKamikaze.norad/amd64/usr/ports/graphics/dri/work/Mesa-9.1.6/src/mesa/drivers'
gmake[3]: *** [all-recursive] Error 1
gmake[3]: Leaving directory `/tmp/obj/mobileKamikaze.norad/amd64/usr/ports/graphics/dri/work/Mesa-9.1.6/src/mesa'
gmake[2]: *** [all] Error 2
gmake[2]: Leaving directory `/tmp/obj/mobileKamikaze.norad/amd64/usr/ports/graphics/dri/work/Mesa-9.1.6/src/mesa'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory `/tmp/obj/mobileKamikaze.norad/amd64/usr/ports/graphics/dri/work/Mesa-9.1.6/src'
gmake: *** [all-recursive] Error 1
===> Compilation failed unexpectedly.
Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to
the maintainer.
*** [do-build] Error code 1
Stop in /usr/ports/graphics/dri.
--
A: Because it fouls the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5239C97A.5040506>