Wayland and Weston 1.0.3 releases out

[Pekka Paalanen]

On Wed, 17 Apr 2013 08:17:46 +0200 (CEST)
Jan Engelhardt <jengelh at inai.de> wrote:

> 
> On Wednesday 2012-12-19 09:20, Jan Engelhardt wrote:
> >
> >On Wednesday 2012-12-19 08:27, Pekka Paalanen wrote:
> >>> make[3]: Entering directory
> >>> `/home/abuild/rpmbuild/BUILD/weston-1.0.3/tests' FAIL:
> >>> surface-test.la [..].
> >>> ==========================================================================
> >>> 6 of 6 tests failed
> >>
> >>could we see the logs from the tests? I mean the files that go into
> >>$abs_topbuilddir/tests/logs.
> 
> Revisiting the matter with 1.1.0 which is supposed to have
> fbdev/headless backends, I get

Unfortunately, these are still not hooked up to the tests, AFAIK.

> abuild at ares07:~/rpmbuild/BUILD/weston-1.1.0/tests/logs> cat
> xwayland_test-serverlog.txt
> Date: 2013-04-17 UTC
> [06:14:49.735] weston 1.1.0
>                http://wayland.freedesktop.org/
>                Bug reports to:
>  https://bugs.freedesktop.org/enter_bug.cgi?product=Wayland&component=weston&version=1.1.0
>                Build:  
> [06:14:49.735] OS: Linux, 3.7.10-jng11-default, #1 SMP Thu Feb 28
> 19:14:27 UTC 2013 (b44c26b), x86_64
> [06:14:49.736] Loading module
>  '/home/abuild/rpmbuild/BUILD/weston-1.1.0/tests/../src/.libs/wayland-backend.so'
> [06:14:49.738] failed to create display: No such file or directory

This error should be due to not running the tests under another Wayland
compositor, nor having DISPLAY set to use the x11 backend. Yes,
http://cgit.freedesktop.org/wayland/weston/tree/tests/weston-tests-env
could use some love.

> [06:14:49.738] fatal: failed to create compositor
> 
> The module file definitely exists, but has a lot of unresolved
> dependencies (reported by `ldd -r`) -- you should ./configure
> LDFLAGS="-Wl,-z,defs" to make these problems visible at build time.

Does your 'ldd -r' check load the weston binary, too? These modules
rely on being loaded by "weston", and they use symbols directly from
the weston binary. That should explain all the unresolved symbols.

Btw. do you have a suggestion how to make the module linking phase in
the build take into account also symbols exported by the weston binary,
and report only the remaining unresolved symbols as errors?


Thanks,
pq