Closed josephbisch closed 1 year ago
It is much more likely an issue with the configure script rather than the toolchain. We build a lot of code with this toolchain and it was built for us by Linaro.
I suggest you try adding --disable-ipv6
to the configure line as the error suggests.
Thanks for getting back.
I looked at the Python configure script closer and saw that explicitly setting --enable-ipv6
seems to override the result of the test. The build seems to proceed fine, but I haven't actually tried out the result yet. You are probably right, but I'll leave this open until I can verify the build works.
Using --disable-ipv6
is not an option for my case.
python3-devel
installation fixed the issue
I am trying to compile Python 2 using the tools in
arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian-x64/bin
. During the configure process, I get the following output:This seems to be a bug with these tools, because the same Python compiles for x86_64 Linux fine.
I know the configure script is picking up the tools correctly, because I see output like
checking host system type... arm-unknown-linux-gnueabihf
andchecking for arm-linux-gnueabihf-gcc... arm-linux-gnueabihf-gcc
.I am using the following Makefile to build Python. It is part of the depends system adopted from Bitcoin Core designed to build software dependencies in a reproducible way. It doesn't work standalone, but you can still get an idea of what it does.
As you can see it downloads Python 2.7.9 and verifies the hash. It runs
./configure
with some standard flags like--host
. I also supply--build
. Then it runs make and make DESTDIR=... install. This same exact Makefile works with x86_64-unknown-linux-gnu as the--host
parameter.The relevant section of configure.ac from Python is line 3514 of configure.ac. That is a link to Python 3, but you get the idea. It looks like there are a number of things checked in that one getaddrinfo() check, so I am not sure which one is actually the issue.