forked from pool/mingw64-headers
Add support to use a different crt (boo#1243096) #2
Reference in New Issue
Block a user
Delete Branch "rhabacker/mingw64-headers:master"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
@@ -19,3 +19,3 @@Name: mingw64-headersVersion: 12.0.0Release: 0Release: 1This is useless and reset by OBS anyway.
@@ -56,2 +56,3 @@%build%_mingw64_configure --enable-sdk=all --with-default-msvcrt=msvcrt%_mingw64_configure --enable-sdk=all \%if 0%{suse_version} == 1600>=This would set UCRT to Tumbleweed as the default for all packages. Can there be problems with the mingwxx-binutils, mingwxx-gcc or other package, because maybe something needs to be adjusted there as well? 16.0 is still a work in progress, so we can't break anything there. I would postpone this until later.
If it's not good enough for Tumbleweed, it isn't good enough for Leap16.
d34fb76baato3fd2ed54063fd2ed5406to441669697aWhy the convoluted check, why not use the new headers from 16.0 on?
Also you need https://build.opensuse.org/request/show/1277215 or similar for this to work.
Based on past experience, I am somewhat conservative here, as I cannot currently estimate what problems this elementary change will cause with the existing 600 packages and thus what additional work will be required for analysis and correction. I would first create an integration branch and use it to test the compiler, binutils and other important packages before rolling this out. The 16.0 repo is still new and not productive and can therefore be understood as such.
I would first activate this package on Leap 16.0 only.
It is a devel project. It is meant to be used for devel. You can always add something to prjconf like
and then evalute that in specfiles.
(Note the difference between openSUSE_Tumbleweed and openSUSE_Factory)
On result from using the integration branch is that the changes for the mingxww-filesystem packages (https://build.opensuse.org/requests/1277215, https://build.opensuse.org/requests/1277677) must be applied before to avoid massive unresolved build failures.
441669697atoe96b766f05e96b766f05to6fc2bce094- Use UCRT on openSUSE Leap 16 by default (boo#1243096)to Add support to use a different crt (boo#1243096)ugh, this is nasty.
This means that if anyone links the package to other project they will get another result.
(I finally found the "accept review" button in gitea)
I concur with michals in that limiting ucrt to just "%_repository=16" is bad style, and it should just be unconditionally used. For now, we can try a first build with that, though.
A comparison of failed builds on openSUSE Leap 16.0 with Leap 15.6 (see Monitor) shows some packages that could be affected by this change.