Closed digitalentropy closed 4 years ago
reveng compilation error under mingw64 has now been fixed.
I am not sure what this issue has to do with reveng, anyway...
ProxSpace was not really meant to be updated with "pacman -Syuu". Running "pacman -Syuu" will update mingw-w64-x86_64-gcc to the latest version. Due to a previous issue with gcc on x64 prior of version 8.2 that cause an error for avx acceleration (hardnested), ProxSpace will download and install mingw-w64-x86_64-gcc 8.2.0-3 if any other version of mingw-w64-x86_64-gcc is installed. At the time when I created this fix, the latest stable mingw-w64-x86_64-gcc package version was 7.3.
Msys2 did have a major update and nowadays the latest gcc version is 9.2. Unfortunately for now, you should not update ProxSpace with "pacman -Syuu".
I will update ProxSpace to include the latest msys2 updates, this could cause other problems so I need to test it excessively. You can expect a major ProxSpace update in the next days.
Well two issues were reported in this single issue. I reacted on the "After the update compiling in the x64 environment also fails with the following error" part.
I did not know reveng had changes, now it makes sense. I did not look too closely at the compilation errors and just thought it had to do with broken packages.
Huge thank you to the both of you for the hard efforts made in supporting the code base and the community.
I will do my best to test out changes as time is available and provide functional feedback.
The reason I updated MSYS2 is because in the current default distribution tab auto-complete seems to be broken within the environment unless I update. If you don’t know what I’m talking about I’ll try to document and open a new issue ticket.
On Aug 15, 2019, at 1:16 PM, Gator96100 notifications@github.com<mailto:notifications@github.com> wrote:
I did not know reveng had changes, now it makes sense. I did not look too closely at the compilation errors and just thought it had to do with broken packages.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/Gator96100/ProxSpace/issues/16?email_source=notifications&email_token=AAKYZPQ4OKOKKUAP32SIZSLQEW2QHA5CNFSM4IL3OU32YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4M4CFI#issuecomment-521781525, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AAKYZPRYUOUJWH6XWP53J2DQEW2QHANCNFSM4IL3OU3Q.
There is now a untested version of the new ProxSpace update avalible: https://github.com/Gator96100/ProxSpace/tree/v3.2
I could compile the pm3 on your v3.2 64b without issues (I did it without QT for hdd space reasons). One minor thing: the terminal window title says still "Select ProxSpace v3.0 - MINGW64" instead of v3.2 May I also suggest to include astyle? (mingw-w64-x86_64-astyle / mingw-w64-i686-astyle) Thanks !
ProxSpace is now using the latest msys2 packages. I also did upload already setup versions of ProxSpace to the GitHub releases.
Steps to reproduce:
Every time I've done this or any combination of the steps, the 64-bit shell seems to get stuck in an update loop where I get the following errors and warnings every time the 64-bit shell starts:
Unfortunately I am not familiar enough with MSYS2 to have a good understanding of what the issue is other than an apparent dependency conflict that doesn't seem to resolve. After the update compiling in the x64 environment also fails with the following error:
Any suggestions?