ld: /usr/lib/liberasurecode.so: unknown type [0x13] section `.relr.dyn'
ld: skipping incompatible /usr/lib/liberasurecode.so when searching for -lerasurecode
2. Despite the pyeclib wheel-build failure, the image-build job still succeeds
3. We're still advertising the py2 build as "latest"
I'm not actually sure how to address that first one, but I think it may be moot because of the third. I'll try to get a patch together to publish the py3 build as both "py3" and "latest".
Thanks for the bug report, and all the investigation so far! I see about three problems so far:
1. Looking at recent image build jobs, there's an error building pyeclib wheels. In particular, when it goes to run
gcc -shared build/temp. linux-x86_ 64-2.7/ src/c/pyeclib_ c/pyeclib_ c.o -L/usr/lib -L/usr/lib -Wl,-R/usr/lib -lerasurecode -lpython2.7 -o build/lib. linux-x86_ 64-2.7/ pyeclib_ c.so
there's a bunch of errors like
ld: /usr/lib/ liberasurecode. so: unknown type [0x13] section `.relr.dyn' liberasurecode. so when searching for -lerasurecode
ld: skipping incompatible /usr/lib/
2. Despite the pyeclib wheel-build failure, the image-build job still succeeds
3. We're still advertising the py2 build as "latest"
I'm not actually sure how to address that first one, but I think it may be moot because of the third. I'll try to get a patch together to publish the py3 build as both "py3" and "latest".