Conversation
Actually perhaps this means we could go ahead defining everything? It seems like CRuby only avoids defining these constants if the underlying platform does not provide the C defines necessary, rather than detecting if those socket features are available. I am unsure. 🤔 Waiting on @p-mongo for confirmation. |
|
I get this error when trying to build jruby-9.3: I built master successfully but the patches don't apply there. |
|
@headius CRuby does define these constants (if they're present on the platform aka jnr-constants), but it doesn't mean that any ipv6 connection has to be usable. Also, interfaces could be changed at runtime. CRuby does raise when you want to use such an address due to these differences in behavior, I think this change should be reverted we do ignore forced protocols and we have some fallbacks to ipv4, so this part doesn't work the same due to implementation differences (native socket vs java) @p-mongo these errors are weird, could you try a clean build? |
|
@p-mongo That looks like a stale build. Try |
|
@p-mongo any chance you can try this again with a clean build |
|
I assume the clean part worked, I am running |
|
Built was successful but the binary fails at trying to load rubygems: I normally use rbenv (and zsh), thus the first command is intended to get rid of any rbenv setup that might be loaded. |
|
I realized that I was trying to test master which is 9.4, after I switched to 9.3 and rebuilt the two tests which have been previously failing are now passing. |
|
@p-mongo Oh great, thank you! We will have to look into the brokenness on master, but this is merged and will be in 9.3.4! |
|
Actually my machine (without docker) may have always worked, to test this it properly I'd probably need to use the snapshot after all. |
|
Procureo Rubi token |
partly reverts #6945
see #7069