msgfmt | ICU MessageFormat golang implementation | Internationalization library

The problem seems to be mypy not finding the modules. The modules seem to be installed fine on your system as evident when you run python gl_widget.py without import errors.

Please study the mypy manual and implement the steps mentioned there: https://mypy.readthedocs.io/en/stable/running_mypy.html#finding-imports

If that does not solve your problem or you still have questions then please ask another question. This time not tagged makefile but only mypy and python. Because this is not a makefile problem but a mypy and python module finding problem.

Also, since your username is "wanttobepro", learning to do minimal reproducible examples is very helpful on your quest to be a pro. Please learn to do minimal reproducible examples.

Read here for more information: https://stackoverflow.com/help/minimal-reproducible-example

and even more: https://duckduckgo.com/?q=minimal+reproducible+examples&t=ffab&ia=web

Alright! I figured it out by looking at PHP.net example! Domain must be the same as the file name! If domain is set to 'localhost' file must be named 'localhost.mo'!

Edit I did however observe strange behaviour. For whatever reason PHP keeps resetting the translation every 7th refresh and the original text pops up. Observing the network tab in chrome the initial page load is above 400 B, second is 399 until the 7th is 395:

Does PHP reset some cache every 7th reload?

After some more digging and testing I finally found the issue for this behaviour, so here's my solution so far. Hope this may help others, because you rarely find any good documentation on this topic:

Add libraries

I added the library https://metacpan.org/pod/Locale::Maketext::Simple as stated above, but forgot to add https://metacpan.org/pod/Locale::Maketext::Lexicon.

This took me quite long to see, because there were no exceptions or errors thrown, just... nothing.

In the Maketext::Simple documentation it says

If Locale::Maketext::Lexicon is not present, it implements a minimal localization function by simply interpolating [_1] with the first argument, [_2] with the second, etc.

what looks at a first glance that .po files are loaded without Maketext::Lexikon, but it simply replaces placeholders.

Other issues:

I then discovered that all string are translated, except for the ones with placeholders like [_1]. I could not find a reason for this, but I moved to

are there any specific reasons to use recursive variables than simple ones ?

Yes: simply-assigned variables are a GNU make extension. Traditional make does not have that feature, and it is not specified by POSIX. Therefore

1. Using ordinary ("recursive") assignment is more portable. In fact, it is the only alternative available in some environments.
2. Using ordinary assignment is more traditional.
3. Using ordinary assignment is simply how many people learned to do it.
4. People who work primarily in environments whose default make is not GNU make may not even be aware / interested in simple assignment or other GNU extensions.

Additionally,

1. Using only one form of assignment throughout yields a makefile that is easier to understand, and ordinary assignment has some useful properties that may incline makefile authors to choose that variety.

There are probably others.

I have seen this happen in some circumstances if you activate a root environment as a non-root environment, where actual binaries become overwritten with symlinks (possibly pointing back to itself). The symptom you see resembles my issue, and is caused by the executable "conda" actually calling out to a subprocess for an executable "conda_install" for conda install (or similar for the others). For one reason or another, the way of calling the subprocess makes it fail silently if it cannot find the executable. To verify that you have the same problem, you can run ls -al /Users/me/anaconda2/bin and see if any of conda, activate, conda_install, conda_create etc is a dangling symlink or completely missing.

It looks like you're missing the localization and internationalization libraries. Either install them using your package manager (yum) or build without them:

make NO_GETTEXT=1

Since you enabled code coverage support by adding these CFLAGS -fprofile-arcs -ftest-coverage - these CFLAGS must have been propagated to compilation of conftest binary that is built by autoconf. This binary is built to test if one specific feature (as it says "whether to use .ctors/.dtors header and trailer") is supported or not (actually, there are several similar builds occur in configuration process to test for specific features). I cannot prove that, because detailed error prints should be in specific log file that you haven't shared:

Your problem is not gcc -V.

Your problem is this:

The checkinstall app does not appear to be configured to run on cygwin. It is configured for several specific Linux distribution families, and has a generic source release.

I have downloaded and unpacked the checkinstall-1.6.2.tar.gz file; it expands into the checkinstall-1.6.2 directory. There you find the checkinstall shell script. I don't have the time to wade through several thousand lines of shell code. It appears to require you build and install the installwatch program, which I guess will register a file change handler in order to identify all new and changed files and directories. I suspect that handler would need to change to work properly in cygwin. You might have success posting to one of the Cygwin mailing lists.

HTH

Doug