Thank you, but it is just the preflight check which should only report the
additional library missing when it would actually be required. It does not
break the build process itself, just confuses a bit when actually
checking the output before starting the ninja build, because such a NO normally
means the build will fail or some functionality will be missing from the result,
so the normal reaction to this is to go and install any missing packages, which
in this case
just leads to a wild-goose chase, especially for less experienced users, which
is why I found it
worth reporting, even if it is not such a big deal.
I am not really familiar with the meson/ninja tools, so I am a
bit clueless as to where and how to fix the test. It is just a petitesse,
something like a minor cosmetic issue. Manipulating the package-installed
system libraries
to merely make the message go away may have other side effects for the build
system later on, so I
would not recommend it.
Regards
Peter
On Sat, 13 Nov 2021, Carla Sensa wrote:
You can try out the below command before (re)building Enlightenment and
related applications.
sudo ln -sf /usr/lib/x86_64-linux-gnu/preloadable_libintl.so
/usr/lib/libintl.so
--
_______________________________________________
enlightenment-users mailing list
enlightenment-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-users
