-
Notifications
You must be signed in to change notification settings - Fork 228
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
CPUFEATURES cross-compile. #158
Comments
Yes, You should be able to override on the command line, no? |
For whatever reason that didn't work. |
I can't reproduce this, setting CPUFEATURES_ARCH on the command line works fine here:
|
oh, I guess you probably tried with env vars. Try on the command line like I did instead. All that said, I forget why CPUFEATURES_ARCH does its own lookup, having it default to the value of ARCH would be reasonable |
…ARCH,UNAME}. Change CPUFEATURES_{ARCH,UNAME} defaults to use {ARCH,UNAME} values. Fixes #158
Try that commit? |
Ah. Yes. I pushed them on env. But the suggested solution works nicely for me. As a side note I'm using dump1090 with librtlsdr 0.8.0 under an qemu emulated aarch64 on an embedded x86_64 AMD R1000 with the footprint of a RPi. :) Works ok, even with instruction emulation. Thanks for the help! |
Having issues with cross compiling.
Makefile.cpufeatures:
CPUFEATURES_UNAME := $(shell uname)
CPUFEATURES_ARCH := $(shell uname -m)
Immediate set instead of lazy set?
ARCH=aarch64 breaks as uname -m is a x86_64 host.
The text was updated successfully, but these errors were encountered: