Need clarity on SCRAMPLE app build for Linux aarch64 ?

[patilmangesh508]

update on build for linux aarch64- SCRAMPLE

able to compile for Linux aarch64 with the correct aarch64 toolchain, but the build fails at link time because a Baselibs dependency (acl-deb) provides an x86_64 static library (libacl.a) which is coming from external repo, causing file in wrong format / EM:62 (architecture mismatch).

basically the build fails because some auto-downloaded module dependencies aren’t aarch64 aware by default and fetching x86_64 .deb libraries (libacl) even when targeting aarch64, that creates an architecture mismatch

not able to find it out from where it is fetching this so we can update for aarch64

[FScholPer]

Please provide more info what toolchain and config you use to build the repo? Also log would be helpful

[btirunagaru]

Faced similar issue on our platform as well . The following issue solved it. pasting the patch info - please double from your end.

diff --git a/third_party/acl/BUILD b/third_party/acl/BUILD
index 7fdb429..0d6e743 100644
--- a/third_party/acl/BUILD
+++ b/third_party/acl/BUILD
@@ -1,5 +1,19 @@
+
+
+cc_library(
+    name = "libacl",
+    linkopts = [
+        "-lacl",
+    ],
+    target_compatible_with = ["@platforms//os:linux", "@platforms//cpu:aarch64"],
+    visibility = ["//visibility:public"],
+)
+
 alias(
     name = "acl",
-    actual = "@acl-deb//:acl",
+    actual = select({
+		"@platforms//cpu:aarch64": ":libacl",
+		"//conditions:default": "@acl-deb//:acl",
+		}),
     visibility = ["//visibility:public"], 
 )
\ No newline at end of file

[4og]

It's a baselibs topic. I created an issue eclipse-score/baselibs#78

[4og]

@patilmangesh508, The issues is addressed in baselibs with eclipse-score/baselibs@2c0ac6f