In few words: SliTaz Next still far from the usable state.
Although you may see long green bars that represent the completeness of the packages re-creation, it doesn't make many sense.
Sometimes there come such moments as now, when I do not know what to do next and when I just want to give up.
In order.
Toolchain issues.
New shiny Glibc-2.26 broke mathematics in the C++ programs and you will see something like this:
${src}/mfbt/decimal/Decimal.cpp:689:14: error: '__builtin_isfinite' is not a member of 'std'
${src}/mfbt/decimal/Decimal.cpp:692:14: error: '__builtin_isinf_sign' is not a member of 'std'
ERROR: cook failed
I'm not "in topic" with all these changes in Glibc, but I clearly see the message. Well, I can just remove "std::" prefix. And know what? It works!
But not in the case of Qt5. It just broke in the very beginning...
Then I found the page describing the same problem, and yesterday I was tried to apply the patches... I'm not a programmer, and even I don't know C or C++: I have only very general idea about what that programs do. But this does not prevent me from repairing programs...
And then GCC failed to build when I applied these patches to Glibc! Looks like it out of my possibilities. I can only try Glibc-2.27 instead of current Glibc-2.26 without or with these patches.
Making usable toolchain is always hard process for me and it is still a half of magic...
Next.
Lesser problems.
RPC. Glibc obsolete RPC some years ago, but it was the possibility to use them using the option --enable-obsolete-rpc (like Archlinux use it, but LFS don't). I tried and it fails for unknown (for me) reason.
What Glibc maintainers to think, how to live without these RPC? Seems the solution is to use libtirpc package, but it is not the 100% substitution, and some programs can use it, while some other need to be tweaked/patched.
OpenSSL. I switched to the 1.1 branch (like LFS and Archlinux) by default, and have additional package for previous branch (openssl10). Newer programs will use OpenSSL-1.1 without any problem. Older programs should be updated or be tweaked to use openssl10 package (like alpine or tls).
Old software. It is sad, but some old software exists, released 8-10 and possible many years ago, unmaintained since then, that don't fit current environment and rejects to build. I found many strange (for me, of course) packages, but don't know what to do with them. I'm just putting them off to the very end.
----
Please keep yourself from posting here posts that are not suitable for this topic!
This will make me even more sad and irritable.