Problem compiling on Manjaro (either via AUR or directly)

[Alan E. Davis]

Some issues have come to light recently regarding libc-2.0, apparently due to changes in the most recent gcc. 

I have encountered this elsewhere.  Entangle is critical for me, so as I rebuild my recently lost system (do to a number of causes, including trust issues) this is a huge deal breaker.  Entangle is the easiest image capture solution for me. 

I am not a programmer, so any effort on my part is a shot in the dark. 

The problem has been pinpointed as belonging to libc-2.0; to the best of my ability, I will attempt to approach upstream developers of that package.  No matter what, the following information may be useful to anyone trying to install Entangle.

Dependency glib-2.0 found: YES 2.80.3 (cached)
env[PKG_CONFIG_PATH]:
env[PKG_CONFIG]: /usr/bin/pkg-config
-----------
Called: `/usr/bin/pkg-config --variable=glib_mkenums glib-2.0` -> 0
stdout:
/usr/bin/glib-mkenums
-----------
Got pkg-config variable glib_mkenums : /usr/bin/glib-mkenums
Program /usr/bin/glib-mkenums found: NO

src/backend/meson.build:72:39: ERROR: Dependency 'glib-2.0' tool variable 'glib_mkenums' contains erroneous value: '/usr/bin/glib-mkenums'

This is a distributor issue -- please report it to your glib-2.0 provider.

It is my understanding that a command like option should resolve this issue, but I'm uncertain how to apply it.  The idea is to convert errors of this kind to warnings.  Note the following message from a developer, about a different package:

GCC version 14 got
strict about pointer types.  The issue is explained under the header "Type
checking on pointer types (-Werror=incompatible-pointer-types)" here: 
https://gcc.gnu.org/gcc-14/porting_to.html

Farther down, "Turning errors back into warnings" suggests that -Wno-
error=incompatible-pointer-types should be enough to make it build.  Best, DWF

Thank you for any advice.  Watch out, take care, beware,

Alan Davis