Bug 107423 - vc4 build failure: "v3d_decoder.c:893: undefined reference to `clif_lookup_bo'"
Summary: vc4 build failure: "v3d_decoder.c:893: undefined reference to `clif_lookup_bo'"
Status: RESOLVED FIXED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/vc4 (show other bugs)
Version: git
Hardware: ARM Linux (All)
: medium normal
Assignee: Eric Anholt
QA Contact: Eric Anholt
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-07-30 07:41 UTC by Fabio Pedretti
Modified: 2018-08-01 18:40 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Fabio Pedretti 2018-07-30 07:41:18 UTC
Since a couple of days I get a build failure on arm64.

Full build log including configure options here:
https://launchpadlibrarian.net/380758857/buildlog_ubuntu-xenial-arm64.mesa_18.2~git1807300730.0a3f65~oibaf~x_BUILDING.txt.gz

Error:
../../../../src/broadcom/cle/.libs/libbroadcom_cle.a(cle_libbroadcom_cle_la-v3d_decoder.o): In function `v3d_field_iterator_next':
/<<PKGBUILDDIR>>/build/src/broadcom/../../../src/broadcom/cle/v3d_decoder.c:893: undefined reference to `clif_lookup_bo'
/<<PKGBUILDDIR>>/build/src/broadcom/../../../src/broadcom/cle/v3d_decoder.c:893: undefined reference to `clif_lookup_bo'
../../../../src/gallium/drivers/vc4/.libs/libvc4.a(vc4_cl_dump.o): In function `vc4_dump_cl':
/<<PKGBUILDDIR>>/build/src/gallium/drivers/vc4/../../../../../src/gallium/drivers/vc4/vc4_cl_dump.c:45: undefined reference to `clif_dump_init'
/<<PKGBUILDDIR>>/build/src/gallium/drivers/vc4/../../../../../src/gallium/drivers/vc4/vc4_cl_dump.c:82: undefined reference to `clif_dump_destroy'
collect2: error: ld returned 1 exit status
Makefile:1012: recipe for target 'gallium_dri.la' failed
make[5]: *** [gallium_dri.la] Error 1
Comment 1 Eric Anholt 2018-07-30 17:53:43 UTC
I fixed the meson build yesterday.  Automake is, as always, more painful.
Comment 2 Eric Anholt 2018-07-30 17:54:28 UTC
(though, if you're building vc4 on your architecture, you should probably be building v3d as well)
Comment 3 Fabio Pedretti 2018-07-31 10:08:49 UTC
When enabling also v3d it builds fine indeed.
Maybe a quick workaround would be to automatically force it when vc4 is requested?
Comment 4 Juan A. Suarez 2018-08-01 07:45:42 UTC
Fix proposal at https://patchwork.freedesktop.org/series/47509/
Comment 5 Juan A. Suarez 2018-08-01 18:40:12 UTC
Pushed in upstream


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.