Bug 67962 - undefined reference to `wayland_drm_buffer_get'
Summary: undefined reference to `wayland_drm_buffer_get'
Status: VERIFIED FIXED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Other (show other bugs)
Version: git
Hardware: Other All
: medium critical
Assignee: mesa-dev
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-08-10 00:28 UTC by U. Artie Eoff
Modified: 2013-08-15 15:10 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

Attachments
make output (93.94 KB, text/plain)
2013-08-10 00:28 UTC, U. Artie Eoff 		Details
View All

Description U. Artie Eoff 2013-08-10 00:28:08 UTC 
Created attachment 83913 [details]
make output

Weston fails to compile with Mesa master since Mesa commit 2c2e64edaba0f6aeb181ca5b51eb8dea8e9b39f9 (http://cgit.freedesktop.org/mesa/mesa/commit/?id=2c2e64edaba0f6aeb181ca5b51eb8dea8e9b39f9):

$WLD/install/lib/libgbm.so: undefined reference to `wayland_drm_buffer_get'

wayland (master) heads/master-0-gdbc41f0
drm (master) heads/master-0-g3c967e7
mesa (master) heads/master-0-g2c2e64e
weston (master) heads/master-0-g1bf1481
Comment 1 Hrvoje Senjan 2013-08-10 22:29:41 UTC 
Also Mesa-demo:
[   79s] xeglgears.c: In function 'main':
[   79s] xeglgears.c:919:9: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
[   79s]          (EGLClientBuffer) color_rb, NULL);
[   79s]          ^
[   79s] /usr/lib64/libgbm.so.1: undefined reference to `wayland_drm_buffer_get'
[   79s] collect2: error: ld returned 1 exit status


and cairo:
[  155s] libtool: link: gcc -D_REENTRANT -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libdrm -I/usr/include/libdrm -I/usr/include/libpng16 -Wall -Wextra -Wold-style-definition -Wdeclaration-after-statement -Wmissing-declarations -Werror-implicit-function-declaration -Wnested-externs -Wpointer-arith -Wwrite-strings -Wsign-compare -Wstrict-prototypes -Wmissing-prototypes -Wpacked -Wswitch-enum -Wmissing-format-attribute -Wbad-function-cast -Wvolatile-register-var -Wstrict-aliasing=2 -Winit-self -Wunsafe-loop-optimizations -Wno-missing-field-initializers -Wno-unused-parameter -Wno-attributes -Wno-long-long -Winline -flto -fno-strict-aliasing -fno-common -Wp,-D_FORTIFY_SOURCE=2 -Wno-unused-but-set-variable -D_REENTRANT -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -fmessage-length=0 -grecord-gcc-switches -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -fasynchronous-unwind-tables -g -o .libs/cairo-sphinx cairo_sphinx-sphinx.o  ../../util/cairo-script/.libs/libcairo-script-interpreter.so ../../boilerplate/.libs/libcairoboilerplate.a /home/abuild/rpmbuild/BUILD/cairo-1.12.14/src/.libs/libcairo.so -lpthread -lpixman-1 -lfontconfig -lfreetype -lEGL -lpng16 -lxcb-shm -lxcb-render -lxcb -lXrender -lX11 -lXext -lz -lGL -ldl ../../src/.libs/libcairo.so -lglib-2.0 -lrt -lm -Wl,-rpath -Wl,/usr/lib64
[  156s] /usr/lib64/libgbm.so.1: undefined reference to `wayland_drm_buffer_get'
[  156s] collect2: error: ld returned 1 exit status
[  156s] make[4]: *** [cairo-sphinx] Error 1
Comment 2 Armin K 2013-08-10 22:31:57 UTC 
I've sent a fix today

http://lists.freedesktop.org/archives/mesa-dev/2013-August/043097.html
Comment 3 Armin K 2013-08-11 15:28:52 UTC 
(In reply to comment #2)
> I've sent a fix today
> 
> http://lists.freedesktop.org/archives/mesa-dev/2013-August/043097.html

Discard this, I've sent a v2 patch today which really fixes the build.
Comment 4 U. Artie Eoff 2013-08-12 14:38:56 UTC 
(In reply to comment #3)
> (In reply to comment #2)
> > I've sent a fix today
> > 
> > http://lists.freedesktop.org/archives/mesa-dev/2013-August/043097.html
> 
> Discard this, I've sent a v2 patch today which really fixes the build.

Patch v2 worked for me:  http://lists.freedesktop.org/archives/mesa-dev/2013-August/043119.html
Comment 5 Chad Versace 2013-08-12 21:35:11 UTC 
Artie, I wrote the guilty commit. Next time I'm the guilty one, please add me to bugs CC list.

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.