-
Notifications
You must be signed in to change notification settings - Fork 100
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
Compilation failure of node-ffi-napi for musl/arm platform #1520
Comments
@kesslerm Thank you! Merge after the test is run. |
merge: #1520 Signed-off-by: Hirokazu MORIKAWA <morikw2@gmail.com>
@kesslerm |
The issue first occured for me when building TurrisOS (hbd branch) for the turris omnia. Presumably any build for the |
I have merged the turris-omnia config into my existing test environment and tested it but could not reproduce it. I will try to prepare the turris-omnia environment and do a full build. That will take some time. |
I was able to reproduce it. The solution is simple, but I will investigate the cause of the suffix change. |
A quick look,
but I haven't been able to find out why the results of automake are different. |
The reason for the difference of suffix was due to this patch. Workarounds have been merged. |
Due to a hardcoded
gnu
suffix, the node-ffi-napi package fails to compile for other targets than libc.This could be resolved by using the
$(TARGET_SUFFIX)
variable, which resolves tognu
on platforms that useglibc
and are notarm
orarmeb
, but to e.g.muslgnueabi
on a target platform using themusl
libc library onarm
orarmeb
.The text was updated successfully, but these errors were encountered: