Cannot change autoconf binary being used!!!! #880
Labels
Comments
|
The tar.gz files on the release pages include all of the autoconf/make generated files. You shouldn't need to use those tools. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am trying to build a micropython binary using open source code. I am also including libffi repo as a dependency for micropython. During the build of libffi submodule (which can be triggered from micropython ports/unix/Makefile libffi "deplibs" target) "autoconf" and "autoreconf" utilities are run.
At my company, we are currently using version 2.69 but 2.71 is required at part of libffi toolchain. We cannot upgrade our build machines to autoconf 2.71 because there are still too many dependencies on 2.69. So what our Jenkins server AMI person did was adding version 2.71 as autoconf271 binary to the same location as regular autoconf which is still 2.69.
My devbox version is 2.71 so my local built works, but on our Jenkins servers I get an error that it's still 2.69 because it's autoconf that is being called not autoconf271. So, my question is if it's possible to set libffi to use autoconf271 not autoconf? I tried the following steps,
From micropython/lib/libffi directory:
config AUTOCONF=autoconf271
export AUTOCONF=autoconf271
autoreconf -i
autoupdate
It seems like at the autoreconf -i step it actually complained that there is no autoconf271 on my devbox. So, I ran "ln -sf /usr/bin/autoconf /usr/bin/autoconf271" command, successfully ran the autoreconf -i, and autoupdate as suggested by autoreconf output. Next, I deleted the autoconf271 symlink above and was expecting the get an error during the build. But instead it runs to completion because it is still using autoconf instead of autoconf271
The text was updated successfully, but these errors were encountered: