Things that killed my motivation to play with wayland

[sardemff7+wayland at sardemff7.net]

On 12/06/2013 02:49, darxus at chaosreigns.com wrote:
> 1) This mesa bug:  https://bugs.freedesktop.org/show_bug.cgi?id=61919
> make fails without C_INCLUDE_PATH set.  It pretty much destroyed my build
> testing setup (I was build testing 46 related repos every few hours).
> I never managed to work out the obvious workaround of just setting
> C_INCLUDE_PATH for mesa builds (which I had working for another repo).
> I included the commit where the problem started.  Three months ago.
> (Build test script I wrote: http://www.chaosreigns.com/code/buildtest/ )

I provided a patch on this one, and even if I didn’t test it, it should 
work in your case. If not, I’m willing to help, just ask me for another 
patch with some relevant logs.


> 2) The XWayland segfault bug:
> https://bugs.freedesktop.org/show_bug.cgi?id=59983
> This was the reason I stopped using weston as my primary UI at home in
> September.  Tiago said he had a fix for it in one of his branches a long
> time ago, but I guess it wasn't compatible with the changes made to the
> plan to handle xwm.  Blows my mind that this isn't the top priority of the
> project.  I'm sure there's fine reasons.  It would be nice to know what
> they are.

I just rebased the full xwayland branch to xorg-server master, and also 
the intel and wlshm DDX.

http://git.sardemff7.net/wayland/xorg-server/log/?h=xwayland-1.15
http://git.sardemff7.net/wayland/xf86-video-intel/log/?h=xwayland
http://git.sardemff7.net/wayland/xf86-video-wlshm/

If Tiago can point me to the fix commit, I can include it in there, so 
we can start using a new base to hack on.


> 3) The state of cairo's build testing, particularly this bug:
> https://bugs.freedesktop.org/show_bug.cgi?id=62375
> Cairo has a huge and glorious build test suite.  But it looked very
> much to me like nobody could've gotten it to pass all tests in any
> subset in years.  psychon was very helpful in tracking down and fixing
> problems.  This one last bug was in the way of me being able to get a full
> subset of tests to pass, so I could automate running them reasonably.
> The maintainer of cairo, Chris Wilson, included a patch to fix it in a
> comment to that bug, but we haven't been able to get him to commit it,
> in three months.  (Lots of stuff, including weston and gtk, are heavily
> dependent on cairo, which tends to break.  Which isn't surprising with
> its unusable build tests.  And the fact that the build test instructions
> specify a method that doesn't allow cairo-gl to be tested.)

Tests are good, but if all of them fail badly, you *can* ignore them. In 
this case, they should be fixed, but that shouldn’t prevent you from 
using cairo. IMO, you should keep trying to get the tests fixed, without 
forcing them in your test script.
I’ll try to support you and provide patches on cairo too, please point 
me to the relevant bugs.

Cheers,

-- 

Quentin “Sardem FF7” Glidic