ivila commented on issue #135: URL: https://github.com/apache/incubator-teaclave-trustzone-sdk/issues/135#issuecomment-2553290988
> I have created a multi-architecture Dockerfile/containerFile that works correctly under AMD64 (x86_64) and exhibits the linker error we have been seeing under ARM64 (aarch64) and uploaded it in a gist: https://gist.github.com/msgilligan/a36d61953d2caf60d33d233fed281c7b > > Note that the exact error is `ld.bfd: cannot find -lgcc_s: No such file or directory` (In some earlier test configurations that I used the `_s` wasn't present.) Actually this is because ld.bfd do not find the gcc_s library, this is common on arm host machine, and cargo defaultly use gcc as linker instead of ld(yes, gcc solves the problem), so change the linker to gcc would work, or you might need to specific the path of gcc_s(trust me, this is painful). I am going to provide a new crate `optee-utee-build`, I hope it will save us from struggle with compiling. PS: If you change the linker to gcc, you might need to change some of the rustc-link-arg, add -Wl to tell gcc pass arguments to linker, for example `cargo:rustc-link-arg=--dynamic-list=dyn_list` changed to `cargo:rustc-link-arg=-Wl,--dynamic-list=dyn_list` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For additional commands, e-mail: dev-h...@teaclave.apache.org
