Am 07.03.22 um 13:25 schrieb Miro Hrončok:
Building pypy is nontrivial. I don't know if you can "just" build it on x86_64
for i686 without using mock, but you should be able to do it in mock:
Btw: How do you handle/fix build issues when you can only build inside mock?
So for example your mock build fails because some paths or binaries are wrong
and it is not obvious from the error what needs to be changed. In these
situations I'd like to have some kind of interactive repl shell similar to pdb.
Is there something like that for mock? Or some other trick to fix such problems?
I found that fixing a build is really time consuming especially if the error
only happens in the %check section and build times are high. I thought about
using a reverse shell (+ enable network for mock) but I guess there is a better
way to do this?
Felix
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
