Bug 27037 - mesa git shows a compilation error
Summary: mesa git shows a compilation error
Status: RESOLVED DUPLICATE of bug 27010
Alias: None
Product: Mesa
Classification: Unclassified
Component: Mesa core (show other bugs)
Version: git
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: mesa-dev
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-12 01:00 UTC by Jos van Wolput
Modified: 2010-03-12 01:15 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Jos van Wolput 2010-03-12 01:00:36 UTC
make shows the following error:
---
make[5]: Entering directory
`/home/jos/tmp/xorg/git-master/mesa/src/gallium/winsys/drm/radeon/egl'
gcc -c  -g -O2 -Wall -Wmissing-prototypes -std=c99 -ffast-math
-fvisibility=hidden -fno-strict-aliasing  -fPIC  -DUSE_X86_64_ASM -D_GNU_SOURCE
-DPTHREADS -DHAVE_POSIX_MEMALIGN -DUSE_EXTERNAL_DXTN_LIB=1 -DIN_DRI_DRIVER
-DGLX_DIRECT_RENDERING -DGLX_INDIRECT_RENDERING -DHAVE_ALIAS -D_GNU_SOURCE
-DPTHREADS -DHAVE_POSIX_MEMALIGN -DUSE_EXTERNAL_DXTN_LIB=1 -DIN_DRI_DRIVER
-DGLX_DIRECT_RENDERING -DGLX_INDIRECT_RENDERING -DHAVE_ALIAS dummy.c -o dummy.o
make[5]: *** No rule to make target
`../../../../../../src/gallium/winsys/xlib/libws_xlib.a', needed by
`egl_x11_radeon.so'.  Stop.
make[5]: Leaving directory
`/home/jos/tmp/xorg/git-master/mesa/src/gallium/winsys/drm/radeon/egl'
make[4]: *** [default] Error 1
make[4]: Leaving directory
`/home/jos/tmp/xorg/git-master/mesa/src/gallium/winsys/drm/radeon'
make[3]: *** [default] Error 1
make[3]: Leaving directory
`/home/jos/tmp/xorg/git-master/mesa/src/gallium/winsys/drm'
make[2]: *** [default] Error 1
make[2]: Leaving directory
`/home/jos/tmp/xorg/git-master/mesa/src/gallium/winsys'
make[1]: *** [subdirs] Error 1
make[1]: Leaving directory `/home/jos/tmp/xorg/git-master/mesa/src'
make: *** [default] Error 1
---
Comment 1 Michel Dänzer 2010-03-12 01:15:12 UTC

*** This bug has been marked as a duplicate of bug 27010 ***


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.