Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
GitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
When cross-compiling curl 7.69.0 with autoconf master, the build fails:
The build works fine with autoconf 2.69. This is OpenEmbedded, cross-compiling using gcc to a Linux platform.
I filed https://savannah.gnu.org/support/?110213 to get support from the autoconf side.
Pasting the digging I've done so far:
It fails like this:
Yes, I'm cross-compiling, but the invocation of
Adding some echos, CURL_CHECK_COMPILER succeeds but it never actually calls into the body of CURL_SET_COMPILER_BASIC_OPTS. The generated code looks like this:
Which is the beginning of CURL_SET_COMPILER_BASIC_OPTS . That eventually calls CURL_COMPILER_WORKS_IFELSE which has a AC_RUN_IFELSE wrapper without the cross-compiling fallback, but it is guarded with a $cross_compiling test.
Does autoconf now detect calls to AC_RUN_IFELSE without an if-cross-compiling option and abort ahead of time? If so, this breaks people who guard AC_RUN_IFELSE themselves, correct?
Solved! From that bug report:
I can confirm that removing that