WAF using system versions instead of in tree versions
jelmer at samba.org
Thu Nov 3 10:09:43 MDT 2011
-----BEGIN PGP SIGNED MESSAGE-----
On 03/11/11 16:54, Sean Dague wrote:
> I ran into some very bizarre breaks in my test tree yesterday, which
were driving me nuts, until I realized what was going on.
> I had run: apt-get build-dep samba4 on Ubuntu 11.10 as a shortcut to
make sure I had all the right header files to build required bits. This
brought in packaged versions of libtalloc-dev, libtevent-dev, and
> Even though WAF correctly identified talloc and tevent as too old in
the configure stage, it still attempted to use them in the link stage.
The issue appears to be that when waf looks for system libraries, it
first checks the pkg-config file. If that exists it also checks the
version. If the pkg-config file exists but is too old it still continues
looking for the library, and then falls back to checking for the library
by simply checking if it exists. This means that it will use the system
library even if it is too old.
We should fix waf to only use the pkg-config file in cases where we can
(e.g. subunit, tevent, talloc, etc) and be strict about the version.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-----END PGP SIGNATURE-----
More information about the samba-technical