On Wed, 18 Apr 2018 20:58:30 +0100 Peter Flynn <pe...@silmaril.ie> said:
> On 18/04/18 20:32, Peter Flynn wrote: > > On 18/04/18 09:56, Carsten Haitzler (The Rasterman) wrote: > >> On Wed, 18 Apr 2018 09:11:33 +0100 Peter Flynn <pe...@silmaril.ie> said: > >>> I know meson is terribly fashionable these days, but I have tried > >>> to get it to work on at least five Linux distros and it's never > >>> worked properly -- always been missing some unfindable component. > >> > >> ummm maybe its just the distros you tried that don't stay up to date > >> that easily? > > > > Is Meson that neglected in some places? I had sort of assumed it would > > be under heavy support as it's become so popular. > > > > So far I have tried Ubuntu, RedHat, CentOS, Bodhi, and raw Debian. > > Just tried Mint: > > > pentacle ~ # apt install git autoconf automake autopoint libtool gettext > > meson ninja Reading package lists... Done > > Building dependency tree > > Reading state information... Done > > autoconf is already the newest version (2.69-9). > > automake is already the newest version (1:1.15-4ubuntu1). > > autopoint is already the newest version (0.19.7-2ubuntu3). > > gettext is already the newest version (0.19.7-2ubuntu3). > > libtool is already the newest version (2.4.6-0.1). > > git is already the newest version (1:2.7.4-0ubuntu1.3). > > Some packages could not be installed. This may mean that you have > > requested an impossible situation or if you are using the unstable > > distribution that some required packages have not yet been created > > or been moved out of Incoming. > > The following information may help to resolve the situation: > > > > The following packages have unmet dependencies: > > meson : Depends: ninja-build (>= 1.6) but it is not going to be installed > > E: Unable to correct problems, you have held broken packages. > > pentacle ~ # > > Unfortunately, apt doesn't say *why* it won't install ninja-build, so I > have no way of knowing how the problem can be fixed. did you try install ninja-build on its own and see what version it was? perhaps its too old? did you customize the pkg repo urls to have extra ones there that are not standard? perhaps mint is just broken if it can't install its own pkgs dependencies if everything you have is stock... but that'd be a pretty horrible break there, so my suspects are custom pkg repos of your own breaking up dependencies somehow... > ///Peter > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > enlightenment-users mailing list > enlightenment-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-users > -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- Carsten Haitzler - ras...@rasterman.com ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ enlightenment-users mailing list enlightenment-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-users
