[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Problem with meson and glib2-tools
To be brief: I had the (bad) idea to want to update clang, for
development testing purposes.
This lead of course to a failure because the cmake version
was not exactly what it wanted (but it failed after configure, not
before, checking the version)
-> so trying to build cmake, with some dependencies not
-> so necessiting to replace various shared libraries, used
by some monsters (firefox...)
-> etc. etc. etc.: hell!
From the various things to be replaced, a common failure:
.work/configure meson ...
while meson was installed, but apparently not a compatible version. So
there seems to be missing dependencies about it, at least for the
version, in various places.
For others, the failure was with glib-mkenums provided by glib2-tools.
Here too, obviously, a missing dependency on the version.
Another one was about itstool: the major.minor.revision was OK,
but the nb was not: it failed with the current installed; and passed
with the next...
A proposal: If this is not already the case or if there is no such
thing, could a proposal, for example for a GSoC participant, be made
so that a checking build system is written, manipulating the
namespace around a package so that:
1) Only the tools and the dependencies explicitely required are
accessible in the namespace---so that the build will fail if there is
something not recorded needed;
2) That the needed things would all be the minimum version required
_including the pkgsrc "nb" variant_ (i.e. if this is not specified,
the nb1 variant)---so that the build will fail if there is an error on
3) That installation of the package is made so that problem at
installation time are seen---the example of the "Conflicting PLIST
Thierry Laronde <tlaronde +AT+ polynum +dot+ com>
Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C
Main Index |
Thread Index |