-
Notifications
You must be signed in to change notification settings - Fork 551
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
Difficult to cross-compile (e.g. Yocto) #104
Comments
My Yocto bitbake recipe
I'm currently using Yocto |
I'm not sure if those patches are suitable for incorporating into the mainline code. If you think they are, I could submit a pull request. |
357cb60 should fix the "unresolved symbol pthread_atfork" problem. |
Please submit a PR to add |
Will be in the next uvloop release (0.9.0) soon. |
Please try uvloop v0.9.0. |
I've tried uvloop v0.9.0, and it fixes the two issues nicely. Thanks very much! |
Is there a solution for uvloop_0.20.0.bb ? when I try to run this in kirkstone: SUMMARY = "Fast implementation of asyncio event loop on top of libuv" PYPI_PACKAGE = "uvloop" inherit pypi setuptools3 SRC_URI[md5sum] = "c3395ddc1746e2bf4b2987d88c4707e8" I get the error: checking whether we are cross compiling... configure: error: in File "/home/dev/yocto/build/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/python3-uvloop/0.20.0-r0/recipe-sysroot-native/usr/lib/python3.10/subprocess.py", line 526, in run |
PYTHONASYNCIODEBUG
in env?: N/AI am trying to make a Yocto bitbake recipe to build uvloop. At the
build_ext
step it gives an error for thelibuv
./configure
call, saying for cross-compilation it needs the--host
parameter specified.It might be possible to use the
--use-system-libuv
option, but at the moment Yocto doesn't support custom options for thebuild_ext
step.I applied the following patch to work around this:
But then I had another problem, which is when I tried to import
uvloop
, I got an error regarding an unresolved symbolpthread_atfork
. I used the following patch to resolve this:The text was updated successfully, but these errors were encountered: