Armen Zambrano G.

The Python version via Homebrew works: ```/opt/homebrew/Cellar/[email protected]/3.8.12_1/bin/python3 uwsgiconfig.py -b``` `-lintl` does not show up in the clang command: ``` clang -o uwsgi ... -lpthread -lm -lz -L/opt/homebrew/Cellar/pcre/8.45/lib -lpcre -L/opt/homebrew/Cellar/yajl/2.1.0/lib -lyajl...

I've worked around it by building a wheel via the working Python installation and then uploading the wheel to a GC bucket. ``` /opt/homebrew/Cellar/[email protected]/3.8.12_1/bin/python3 -m pip install "uWSGI==2.0.19.1" DEPRECATION: Configuring...

> Have you tried with `UWSGI_INCLUDES=/opt/homebrew` instead? I tried the full path `/opt/homebrew/lib` w/o success: I can't try for now as my M1 is out for repairs.

I've not had time to try it as my laptop is out of commission. Maybe later this week.

I'm back! :) I run: `UWSGI_INCLUDES=/opt/homebrew ~/.pyenv/versions/3.8.12/bin/python uwsgiconfig.py -b` and it failed with (as in my opening output): ``` [thread 3][clang] plugins/router_fcgi/router_fcgi.o *** uWSGI linking *** clang -o uwsgi core/utils.o...

Just to make it easier to see, I'm *only* going to list from the point that the clang command differs. In this order: - Using Python 3 from pyenv: -...

This works for Python installations that fail with `-lintl` missing: > LDFLAGS=-L/opt/homebrew/Cellar/gettext/0.21/lib pip install "uWSGI==2.0.19.1" @sajoku @DanielKorsa let me know if this works for you

> Why don't merge this? Because it is not good. This is the Docker image that is used as part of the release work and we cannot be adding hacks...

Unfortunately, I don't. I gave access to Will Lachance and some people from his team at some point.

> nit: "Various changes" in commit message is a bit ambiguous, is there an overall theme to the refactors? (or should these be separate PRs?) Mostly making the following PRs...