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
Version 0.18 broken on 32-bit #2847
Comments
Thanks, yea, this is the old "atomic requires 64-bit alignment for struct field access", which obviously changes when we do any structural changes of the struct. We should get a 32 bit CI test server. |
@bep glad you at least know what it is. I always have a love/hate relationship with those sorts of bugs: "Oh, that." |
I can reproduce this with the |
On an added note, you don't need Windows to trigger this:
Fails even on macOS; this passes:
|
Seems like this fixed it |
On behalf of the Debian Go packaging team, I would like to express our heartfelt thanks for getting this fixed so quickly. A gentleman on our team has, to my pleasant surprise, packaged the Debian 0.18-2 during my extended absence, but he noticed that Hugo failed to build on i386 and armhf, which would prevent Hugo's entry into the upcoming Debian 9.0 ("stretch") if not resolved by 15 January 2017. So yes, it is, again, to our pleasant surprise, that this issue is already reported and fixed, and a v0.18.1 regression fix release is on the way! |
I'm going to release it tomorrow. |
Wonderful! Thank you Bjørn! |
Cc: @toddy15 |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Running 32-bit Hugo 0.18 on 32-bit Windows 7 crashes:
Version information for the problematic install:
The same site works with Hugo 0.17 installed through Chocolatey on the same machine, with the following version info:
the site also works with Hugo 0.18 on a 64-bit Ubuntu machine. Let me know what other info you need. We are using version 0.17 for now, so we are operable, but I thought you might like to know.
The text was updated successfully, but these errors were encountered: