On Mon, 4 Jul 2016 15:23:48 +0100 Emil Velikov <emil.l.veli...@gmail.com> wrote:
> Hi all, > > Here is a respin of the earlier series which changes how libweston is > named, and thus shipped. I believe all the logic/reasoning is explicitly > stated, although if something feels amiss, please let me know. > > NOTE: WARNING: The series exposes a fatal bug in weston thus the tests > fail to build (let alone run). > Namely: atm some/many of the modules are built with unresolved symbols. > Is that a bug or by design ? From a quick look it seems to be the > latter. Hi Emil, what unresolved symbols? You mean the symbols that are resolved from Weston the executable? Or maybe the symbols that libweston exports, and test modules expect to be present without actually linking to libweston? Yeah, all that needs to be fixed in time. Should we link all modules to libweston? I'd assume that should fix almost all of them, but I haven't looked yet. Obviously we cannot land patches that break the tests. > If anyone is interested in resolving this please grep through mesa for > "no-undefined" - it handles both -no-undefined and -Wl,--no-undefined in > a portable manner. Preferably all the binaries we build would be using no-undefined. It was not possible before libweston because weston the executable provided lots of them, but now it should be achievable and a very good improvement in catching stupid bugs. Thanks, pq
pgpD6h0kJ6yJY.pgp
Description: OpenPGP digital signature
_______________________________________________ wayland-devel mailing list wayland-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-devel
