Bug 16204 - Build fails with '--disable-xinerama'
Summary: Build fails with '--disable-xinerama'
Status: RESOLVED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: Server/General (show other bugs)
Version: git
Hardware: Other All
: medium normal
Assignee: Xorg Project Team
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 6009
  Show dependency treegraph
 
Reported: 2008-06-02 11:53 UTC by Ian Romanick
Modified: 2008-06-03 21:17 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Fix build wiht --disable-xinerama (1.30 KB, patch)
2008-06-02 12:08 UTC, Ian Romanick
no flags Details | Splinter Review

Description Ian Romanick 2008-06-02 11:53:54 UTC
Configuring with the following causes the xserver build to fail.  Removing '--disable-xinerama' causes it to work again.  I discovered this while trying to validate whether or not bugzilla #6009 still exists.

PKG_CONFIG_PATH=/opt/xorg-master-x86_64/lib64/pkgconfig ACLOCAL='aclocal -I /opt/xorg-master-x86_64/share/aclocal/' ./autogen.sh --prefix=/opt/xorg-master-x86_64 --libdir=/opt/xorg-master-x86_64/lib64 --with-mesa-source=/home/idr/devel/graphics/Mesa --disable-xinerama --disable-dmx --disable-xvfb --disable-xnest --disable-xwin --disable-xgl --disable-xglx --disable-xegl --disable-kdrive --disable-xprint --enable-glx --enable-glx-tls --enable-dri
Comment 1 Ian Romanick 2008-06-02 12:08:28 UTC
Created attachment 16876 [details] [review]
Fix build wiht --disable-xinerama

This simple patch fixes the build, but I don't know this part of the code well enough to know whether or not it will break something else.  Could someone review it please?

kthx
Comment 2 Peter Hutterer 2008-06-03 21:17:03 UTC
Ian: 
it was less invasive to make SyntheticMotion and PostSyntheticMotion to take
the device parameter. fixed with 45b661c67aca1a728f1793dd94d701488f1f196c.
Thanks for reporting.


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.