![]() usr/bin/x86_64-w64-mingw32-gcc-7 because associated file Update-alternatives: warning: skip creation of Update-alternatives: using /usr/bin/x86_64-w64-mingw32-gcc-posix to provide Update-alternatives: using /usr/bin/i686-w64-mingw32-gcc-win32 to provide Update-alternatives: using /usr/bin/i686-w64-mingw32-gcc-posix to provide Makefile to translate the debian variant to the upstream identifier. The MinGW-w64 project's gcc-7.2.0 identifies its version as 7.2.0,īut debian's MinGW-w64 release uses 7.2-win32 instead. Work around a dubious debian cross-compiler change Posix thread models for previous versions):Ĭommit 0ced710acb5e559ccd00a93662c009b6e24ff534 Makes me wonder whether the problem is the '-win32' suffix that debian addedīeginning with gcc-7 (I don't remember how they distinguished the win32 and Update-alternatives: warning: skip creation of /usr/bin/i686-w64-mingw32-gcc-7īecause associated file /usr/bin/i686-w64-mingw32-gcc-7.2-win32 (of link groupĪlternative /usr/bin/i686-w64-mingw32-gcc-win32 Update-alternatives: warning: forcing reinstallation of alternative ![]() That, and then see if Kim's willing to upgrade in parallel. Upgrade my "buster" chroot, because what could go wrong?įirst of all, the cross compiler got upgraded, so I guess I'll have to test Mozilla/5.0 (X11 Linux x86_64 rv:52.0) Gecko/20100101 Thunderbird/52.6.0įacing a large backlog of work on a Friday afternoon, I thought I'd just ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2022
Categories |