-
Notifications
You must be signed in to change notification settings - Fork 0
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
aws cli pip install error: ld.lld: error: unknown argument '-fatal_warnings', did you mean '-fatal-warnings' #1
Comments
@timblaktu I probably need to update my instructions, awsdocs/aws-cli-user-guide#11 (comment) shows somewhat different way, if this doesn't work I'd love to help you figure this out |
Yeah, those are actually the instructions I followed ( The most recent ones from may in that link you sent). ( Sorry about the line formatting problems in my post...). I'll try to post more information on it Later today. |
@missingcharacter I updated my OP to include the full error. The
I cant grep any reference to either "fatal warning" option in the awscli repo, branch v2 at HEAD commit b06369b1d5b5e98e93974bd4ea714dc024e87850:
So i'm guessing this is a problem with my local termux clang or lld package. Ill try to go deeper to see where these linker options are being set. You have any bright ideas? Edit: i dont see any reference to this linker option in llvm's lld nor gnu ld. Hmm... Also im using python 3.10.6 and newer awscli v2 commit. Maybe you can try to repro in your environment to upgrade your awscli? |
@timblaktu I was able to reproduce: $ pkg upgrade
$ pkg install -y rust
$ python -m venv newvenv
$ source newvenv/bin/activate
$ git clone -b v2 https://github.com/aws/aws-cli.git new-aws-cli
$ cd new-aws-cli
$ pip install --upgrade pip
$ pip install ruamel.yaml==0.17.17
$ pip install -e . Let me see if I can fix it |
@missingcharacter turns out this is just a bug in awscrt python project, reported a couple months ago.. Ill try to track down the commit that added this bogus linker argument and try to build the previous version, or fork and fix.. Edit: bullseye |
@timblaktu I was able to build with these instructions, let me know if these work and I'll update my docs $ pkg upgrade
$ pkg install -y rust
$ python -m venv newvenv
$ source newvenv/bin/activate
$ git clone -b v2 https://github.com/aws/aws-cli.git new-aws-cli
$ cd new-aws-cli
$ pip install --upgrade pip
$ pip install ruamel.yaml==0.17.17
$ pip install awscrt==0.13.0
$ vim setup.cfg
$ git diff
diff --git a/setup.cfg b/setup.cfg index 91abf8b80..30dcf0048 100644 --- a/setup.cfg
+++ b/setup.cfg @@ -36,7 +36,7 @@ install_requires =
wcwidth<0.2.0 prompt-toolkit>=3.0.24,<3.0.29 distro>=1.5.0,<1.6.0
- awscrt>=0.12.4,<=0.14.0
+ awscrt==0.13.0
python-dateutil>=2.1,<3.0.0
jmespath>=0.7.1,<1.1.0
urllib3>=1.25.4,<1.27
$ pip install -e .
$ aws --version aws-cli/2.7.29 Python/3.10.6 Linux/5.10.107-android13-4-00008-g466e95df8c7c-ab8760753 source/aarch64 prompt/off |
@missingcharacter Oh i see you used an old version of awscrt. You could also pre-imstall the awscrt dependency from my fork to get a newer version that works, using:
|
Wow, the state of python packaging is really messy. (Its been a while for me). So... @missingcharacter, I was able to get my fork/branch working with the latest awscli version by modifying awscli's setup.py using:
Once they merge the awscrt PR, we can remove this hack.. |
Following your instructions for installing aws cli on termux, last step produces:
Using:
With:
The text was updated successfully, but these errors were encountered: