i386

[tianon]

Similar to #37, i386 fails to build with error unknown case for SETCONTEXT_CLOBBERS_TLS (from https://github.com/gcc-mirror/gcc/blob/gcc-7_1_0-release/libgo/runtime/proc.c#L154).

[tianon]

(which isn't really related to #11, but cross-linking is probably useful anyhow)

[tianon]

Oh, additional thing worth mentioning:

I tried using export libgo_cv_lib_setcontext_clobbers_tls=no as a super hack to workaround what seems to be some bad detection (since proc.c doesn't have a case in that #if chain to handle Linux), and got the following fun behavior after a successful compile:

root@249ab9843e95:/# go get -d -v github.com/tianon/rawdns/...
fatal error: gogo setcontext returned

goroutine 16 [running]:

[srilakshmidj]

Hi,
I hit the same issue and found that SETCONTEXT_CLOBBERS_TLS was incorrectly #defined by the failed thread-safety test in the src/libgo/configure. The test process aborts after a getcontext call
if (getcontext (&c) < 0)
abort ();
The configure sees the exit code is non-zero (134) and enables SETCONTEXT_CLOBBERS_TLS, but this doesn't apply to linux. (It really should have checked that the exit code was 1. See the test code in the file for details)

And the getcontext failed because sigprocmask syscall was blocked in docker. After enabling the syscall, I was able to build gcc fine.

[liudonghua123]

Hi, I recommend to fix this issue and build a 32-bit images. Because many test should run on 32-bit environments.

[tianon]

As you can see above, I spent a fair amount of time trying to get it working. If you've got more ideas for how to make this work, they're welcome.

[tianon]

(A PR would be really helpful, or even just a patch as a starting point.)

[tianon]

I've just tested and this still exhibits across all four variants. 😞

[tianon]

Closing for now -- happy to reconsider if/when there's sufficient proof that the issues are resolved.