From: David Gibson <david@gibson.dropbear.id.au>
To: ehabkost@redhat.com, crosa@redhat.com, ldoktor@redhat.com
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Cryptic errors from PIP install if missing openssl-devel
Date: Thu, 29 Aug 2019 11:31:25 +1000 [thread overview]
Message-ID: <20190829013125.GG16342@umbus.fritz.box> (raw)
[-- Attachment #1: Type: text/plain, Size: 1761 bytes --]
If I attempt to run "make check-acceptance" on my POWER9, RHEL8.1
machine when the openssl-devel package isn't installed, I get the
following very cryptic error:
VENV /home/dwg/qemu/build/rhel8/tests/venv
PIP /home/dwg/qemu/tests/requirements.txt
Command "/home/dwg/qemu/build/rhel8/tests/venv/bin/python -u -c "import setuptools, tokenize;__file__='/tmp/pip-build-la4el5r5/cryptography/setup.py';f=getattr(tokenize, 'open', open)(__file__);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, __file__, 'exec'))" install --record /tmp/pip-1efs22iz-record/install-record.txt --single-version-externally-managed --compile --install-headers /home/dwg/qemu/build/rhel8/tests/venv/include/site/python3.6/cryptography" failed with error code 1 in /tmp/pip-build-la4el5r5/cryptography/
Using V=1 doesn't give any more useful information, and it's not
(easily) possible to manually re-run the given command since it relies
on things in /tmp that are removed once the attempt finishes.
I only figured out it was openssl-devel being missing that was the
problem by (mostly) guesswork. It would be really great if we could
generate a more helpful error here.
In addition, if I rerun "make check-acceptance" it no longer even
attempts the PIP install, since tests/venv already exists in my build
environment. It then sort of works, but I think it might be hitting
other errors because of the missing python packages. Sorry that's a
bit vague - I also seem to be getting unrelated errors that I'm still
trying to figure out.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2019-08-29 1:33 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-29 1:31 David Gibson [this message]
2019-08-29 1:51 ` [Qemu-devel] Cryptic errors from PIP install if missing openssl-devel David Gibson
2019-08-29 3:27 ` Cleber Rosa
2019-08-29 9:24 ` Philippe Mathieu-Daudé
2019-08-29 9:46 ` Philippe Mathieu-Daudé
2019-09-03 15:08 ` Cleber Rosa
2019-09-03 15:22 ` Philippe Mathieu-Daudé
2019-09-03 15:47 ` Cleber Rosa
2019-09-03 15:56 ` Lukáš Doktor
2019-09-03 15:57 ` Lukáš Doktor
2019-09-03 17:27 ` Eduardo Habkost
2019-09-03 22:33 ` Cleber Rosa
2019-09-03 15:18 ` Cleber Rosa
2019-08-30 17:56 ` Eduardo Habkost
2019-08-31 1:48 ` David Gibson
2019-09-03 15:31 ` Cleber Rosa
2019-09-04 19:57 ` Cleber Rosa
2019-09-05 2:09 ` David Gibson
2019-09-05 13:38 ` Cleber Rosa
2019-09-05 14:06 ` Eduardo Habkost
2019-09-05 15:24 ` Cleber Rosa
2019-09-06 0:34 ` David Gibson
2019-09-06 14:43 ` Eduardo Habkost
2019-09-06 14:52 ` Cleber Rosa
2019-09-06 15:14 ` Eduardo Habkost
2019-09-06 15:29 ` Cleber Rosa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190829013125.GG16342@umbus.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=crosa@redhat.com \
--cc=ehabkost@redhat.com \
--cc=ldoktor@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.