Following recent discussions and to reduce the maintenance burden, I'm
planning to start merging native and mingw packages. Initially, I'll be
looking at these packages where I maintain both variants:
I'm performing test builds here . Once I've got them all building
there, if there are no objections, I plan to push to F37 and retire all
the corresponding mingw repos.
So I'm trying to build a project that does have some nono instances of
"using namespace std", however, I have removed them and I STILL get this
Is it possible for mingw to conflict with itself?!?!?
In file included from
reference to 'byte' is ambiguous
579 | byte *pRecord;
I have removed the instance of it in logger.cxx and it does not exist in
lgbook.h or in fltk AFAIKT...
What now? From what I can tell (and I'm no C/C++ expert) this problem was
introduced in C++17 so perhaps building in C++14 will work around the issue
but I can't seem to find a REAL fix.
In mingw-filesystem-131 I've landed a new dependency generator for
mingw-python packages, which uses pythondistdeps.py like the native
python packages. This revealed two packages with unsatisfied
requirements, which are therefore now FailsToInstall. I've submitted the
two missing packages for review, which I'd appreciate if someone could
mingw-python-charset-normalizer - needed for mingw-python-requests
mingw-pyproj - needed for mingw-python-OWSLib
Both are straight forward mingw-python packages. Happy to review in
I've tested the mingw-openssl-3.0 update in this COPR repo . All
builds succeeded right away except for mingw-spice-gtk which I needed to
update from version 0.37 to 0.39 (and as a dependency
mingw-spice-protocol from version 0.14.0 to 0.14.3).
If there are no objections I'd file a self-contained change to get this
into F37. I'd also file a self-contained change for the toolchain updae
(GCC12 and possibly binutils 2.38).