Terminate Msys2 Without Returning to Shell and Check for Updates Again
I'm trying to utilize hunspell from msys in hopes that it can load dictionaries from paths containing non-ascii characters (the source hunspell distribution tin can't)
Does the --root option piece of work? I'd like it to install the package into an existing mingw location:
pacman -S --noconfirm mingw-w64-i686-hunspell --root "C:\Qt\Tools\mingw730_32" error: failed to initialize alpm library (could not discover or read directory: C:\Qt\Tools\mingw730_32/var/lib/pacman/) 
Root option is for other purposes so y'all can't employ information technology every bit you similar
What is the right option and then?
Root choice is for install the aforementioned files layout in dissimilar place
So if you specify for example /c/newroot folder
And so you get /c/newroot/{usr,mingw32,mingw64} and etc folders
But yous get-go demand to create some folders manually
If y'all need to install in your custom folder then you must copy needed files yourself from existed msys2 installation or extract from archives manually
This is similar yous prepare CHROOT environment on linux
Okay. I'll just copy out the files I demand after installation, that sounds easiest :)
Yous must understand what you are doing
Our mingw toolchain is GCC-9.one.0 with posix threads model
If your mingw installation is different yous can go hangs
You need to not mix libraries from dissimilar tool chains
Okay: the trouble I'1000 trying to solve is that hunspell needs to exist given a file path to load the dictionary. It has a workaround for Windows for non-ASCII paths, but MinGW does non implement a wchar_t interface needed for iostream::open up() - only MSVC does
Does the hunspell in msys2 have a fix for this? If information technology does we can consider switching over to it entirely. Right at present nosotros apply MinGW that comes with Qt.
As I recall we do not workaround wchar for hunspell but need to check
And while you can prefix the path with \\?\, I recall y'all still have to use the wchar_t type for that to take effect - I've tried everything...
My just other solution if this doesn't work is to re-create the files using Qt to a location without ASCII characters then feed that to hunspell. :|
You can attempt remove _MSC_VER from condition and rebuild hunspell with mingw
Ah, however, GCC viii.0.0 implements std::filesystem which should solve this
Perhaps if we use your mingw I can simply patch information technology with that instead - because Qt's MinGW is 7.3.0. Would that require a rebuild of Qt though?
I don't know what toolchain yous use so can't say
I see you lot take Qt packaged already
Perhaps it's an selection to switch to msys entirely
If you lot create patch for hunspell to piece of work throw libstdc++ filesystem - y'all can create pull asking on github for review
Johannes Schindelin
@dscho
TheGoddessInari
@TheGoddessInari
I'm sure it'southward been asked before, only is there some reason that msys-2.0.dll doesn't send with the DLL Tin Movement flag? I've been using it for years to make it piece of work with ALSR/ForceRelocateImages.
Ray Donnelly
@mingwandroid
Yes, it's considering of how Cygwin forks.
TheGoddessInari
@TheGoddessInari
Last I checked, DLL Can Move doesn't affect it if ALSR/etc isn't forced, but if ALSR is, then simply fustigate.exe/sh.exe/pacman.exe need ForceRelocateImages IFEO exceptions with the flag set. (Otherwise everything still crashes.)
Umm... One description. Do you propose to ready the DLL Can Move flag to yes, or no?
An fault occurred during the upgrade.
Error: libcurl: missing required signature Error: curl: missing required signature Mistake: failed to commit transaction (invalid or corrupted parcel) Errors occurred, no packages were upgraded.
@smalltalkman I'thou practice updates on some my PC without issues
probably something wrong with downloading
I removed the mirror server and the proxy configuration and re-downloaded the file. I nevertheless have this error.
I downloaded the file libcurl-7.65.2-1-i686.pkg.tar.xz from http://repo.msys2.org/msys/i686/ via the bitcomet tool, which has the same CRC-32 of the file downloaded past the pacman -Syu method.
@smalltalkman Im recreate signatures, endeavor again
@Alexpux Thank y'all very much, successfully upgraded
TheGoddessInari
@TheGoddessInari
@elieux I forgot, it's normally DYNAMICBASE in the linker, since msys-2.0.dll ships with it off for some reason. Since information technology merely allows it to be ALSR relocated, it shouldn't accept any downsides unless there'south something I'm not aware of, merely that said, I've been running with that on ever since MSYS2 came out in the beginning place with ALSR, HighEntropy, ForceRelocateImages, BottomUp, etc.
When upgrading "mintty", it will prompt "terminate MSYS2 without returning to vanquish and check for updates once more" and "for example shut your concluding window instead of calling exit", but afterwards endmost, the "pacman" process is not closed, I demand Manually close the process.
@smalltalkman yes, i dont know how to ready it
Johannes Schindelin
@dscho
This explains why the Cygwin runtime (and hence, the MSYS2 runtime) cannot be relocatable, and I think all of the flags you talked about are set accordingly.
Guillaume Jacquemin
@williamjcm
I saw that, on top of QtCreator (which I've been using for a while), MSYS2's repos have Codelite and Geany. Are these three the simply IDEs in MSYS2'southward repos, or are there others that I might accept missed ?
@williamjcm as I recall that's all
Source: https://gitter.im/msys2/msys2?at=5d2f70623b41924785d8e687