-
Notifications
You must be signed in to change notification settings - Fork 79
Wolfi OS and installation fails. #134
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I got little further and now error seems like / # pip install aws-lambda-python-runtime-interface-client-2.0.10.tar.gz × python setup.py egg_info did not run successfully. |
Similar error here: awslabs/aws-lambda-cpp#116 What is the |
Hi, this seems to be the same issue as with #144. In the mean time I'd recommend using an earlier version of autoconf. I am closing this as duplicate for now. |
I'm trying to use this inside wolfi OS https://github.com/wolfi-dev/os/tree/main
However, I could not make this work since the setup fails here
/home/aws-lambda-python-runtime-interface-client-2.0.10 # python setup.py *** Do not use buildconf. Instead, just use: autoreconf -fi Can't exec "libtoolize": No such file or directory at /usr/share/autoconf/Autom4te/FileUtils.pm line 318. autoreconf: error: libtoolize failed with exit status: 2 Traceback (most recent call last): File "/home/aws-lambda-python-runtime-interface-client-2.0.10/setup.py", line 98, in <module> ext_modules=get_runtime_client_extension(), ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/aws-lambda-python-runtime-interface-client-2.0.10/setup.py", line 46, in get_runtime_client_extension extra_link_args=get_curl_extra_linker_flags(), ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/aws-lambda-python-runtime-interface-client-2.0.10/setup.py", line 19, in get_curl_extra_linker_flags check_call(["./scripts/preinstall.sh"]) File "/usr/lib/python3.12/subprocess.py", line 413, in check_call raise CalledProcessError(retcode, cmd) subprocess.CalledProcessError: Command '['./scripts/preinstall.sh']' returned non-zero exit status 2.
is there any debugging options available to see whats missing the host OS ?
what that method trying to find please ?
Also should I use autoconf ?
thanks much
The text was updated successfully, but these errors were encountered: