-
Notifications
You must be signed in to change notification settings - Fork 7
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
Linux build instructions fail on aarch64 because base library's CPU timept support is implemented only for x64/x86/IA64 #4
Comments
Ah, the issue is that
which are only defined if the symbol For reference: https://stackoverflow.com/questions/40454157/is-there-an-equivalent-instruction-to-rdtsc-in-arm |
Reading BL_HAS_CPU_TIMEPT and failing gracefully (#error) or providing a fallback from malc would probably have been preferable. You seem to be mostly right. I'm not planning it to add it (and especially testing it) myself but I can take an MR. Note that the heavy lifting is already done by e.g. the Google Benchmark project, it should be pretty straightforward to add: On the base library there are these headers which can be useful to make the reduce a bit the #ifdef mess: |
That's fair enough. If I end up adding support I will certainly raise a PR for you, but I'm not sure I'll get a chance. |
Hi,
I'm investigating running mini-async-log-c on a Raspberry Pi to log some time-sensitive code. The Raspberry Pi is running the PiCAT 4 version of Raspberry Pi OS, aarch64. This version of Raspberry Pi OS is derived from Debian Buster 10.
I followed the readme's Linux build instructions for Debian/Ubuntu-type systems, but didn't get a successful build. The output from the
meson
process looks fairly reasonable to my inexperienced eyes:I'm not sure if the "missing usable header" for
io.h
is a problem. My system does havebuild-essential
installed and I have various files namedio.h
under/usr/src/linux-headers-.....
Anyway, running the build with
ninja $MYBUILDDIR
fails, apparently on test code. C is not a language I'm very expert in, but these "implicit declaration of function" warnings look more like something basic is missing from the build environment, to me:Am I missing some dependency that I should have installed before attempting to build
malc
?Re-running the build command generated slightly different output each time, but has eventually stabilised on the following:
Is there any other information I can provide that would help identify the root cause?
The text was updated successfully, but these errors were encountered: