Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update MSYS2 #2927

Closed
MSP-Greg opened this issue Apr 30, 2019 · 5 comments

Comments

@MSP-Greg
Copy link

commented Apr 30, 2019

Currently, updating only the 64 bit toolchain results in 82 MiB downloaded, 462 MiB installed...

@IlyaFinkelshteyn

This comment has been minimized.

Copy link
Member

commented Jul 16, 2019

@vadz

This comment has been minimized.

Copy link

commented Aug 3, 2019

Not sure if it's really useful to report this, but this update resulted in compiler (which is now gcc 9.1) crashing reliably when compiling our unit tests, see e.g. this build log.

@IlyaFinkelshteyn

This comment has been minimized.

Copy link
Member

commented Aug 3, 2019

Do you believe it is MSYS issue. or it is something AppVeyor can fix? As a temporary workaround you can set image to the previous one, image: Previous Visual Studio 2015 I believe in your case. But this workaround would be valid only till next update.

@MSP-Greg

This comment has been minimized.

Copy link
Author

commented Aug 4, 2019

@vadz

Just for testing, have you tried a 64 bit build using MSYS2? Most the building I'm familiar with is Ruby itself or extension gems. In many cases, the toolchain is updated, so we've always been using the most current MSYS2 gcc compilers. Never had any issues. I've also built a fair number of MSYS2 packages, but I don't recall how often I ran 32 bit builds...

@vadz

This comment has been minimized.

Copy link

commented Aug 4, 2019

Thanks for your replies! I had indeed switched to the previous image to avoid this problem for now, but since then another member of our project (@MaartenBent) has found a workaround for this bug, so the problem is fixed now.

I've mostly commented here just in case it could be useful for others running into the same problem, as it took some time to realize that the new build failures were due to the compiler update (and not just due to some cosmic rays triggering compiler crashes).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.