Mirror of forum.nim-lang.org

10333 :: crosscompiling - SSL

• mantielero (orginal) [2023-07-11T19:57:02+02:00] view original

  I end up with the following line in order to crosscompile from Linux in x64 with the target RPi1:

  
  nim c --cpu:arm --os:linux --cc:clang --os:linux  --clang.exe="zigcc" --clang.linkerexe="zigcc" --passC:"-target arm-linux-musleabi -mcpu=arm1176jzf_s -fno-sanitize=undefined" --passL:"-target arm-linux-musleabi -mcpu=arm1176jzf_s" alarma.nim
  Run

  Now I want to compile with SSL support. I tried: -d:ssl but that is not working. I have openssl-1.1.1 in the RPi.

  Any idea about what can I do to crosscompile with SSL support?

---

• mantielero (orginal) [2023-07-11T20:12:36+02:00] view original

  Using -d:nimDebugDlOpen gives the following when run:

  
  Dynamic loading not supported
  could not load: libcrypto.so.1.1
  Run

---

• arnetheduck (orginal) [2023-07-11T22:37:31+02:00] view original

  In chronos we use https://github.com/status-im/nim-bearssl to avoid this problem - ie the ssl library is compiled as part of your application.

---

• mantielero (orginal) [2023-07-11T23:32:19+02:00] view original

  Thanks for the info. How can I use it with std/httpclient? I just want to call a google script from the RPi.

---

• guzba (orginal) [2023-07-11T23:53:50+02:00] view original

  You'll probably have an easier time using https://github.com/treeform/puppy for simple HTTP requests.

---

• Yardanico (orginal) [2023-07-12T04:14:41+02:00] view original

  The actual issue in your case is pretty simple - you're statically compiling with musl, and statically compiled binaries can't load shared libraries (at least not the "default" way). So if you want to reuse the rpi openssl, it'd be better if you just cross-compile to whatever glibc version is on that RPi (zig cc can do that too).

---

• mantielero (orginal) [2023-07-12T15:49:39+02:00] view original

  Thank you both.

  The puppy solution is not working either because it aims to load dinamically libcurl:

  
  could not load: libcurl.so(|.4)
  Run

  As Yardinico mentioned, the issue was about mixing static and dynamic.

  For the record, fixed by compiling with:

  
  nim c -d:ssl -d:sslVersion=1.1  --cpu:arm --os:linux --cc:clang --os:linux  --clang.exe="zigcc" --clang.linkerexe="zigcc" --passC:"-target arm-linux-gnueabihf -mcpu=arm1176jzf_s -fno-sanitize=undefined" --passL:"-target arm-linux-gnueabihf -mcpu=arm1176jzf_s" alarma
  Run

  using arm-linux-gnueabihf as target.

---

• jtv (orginal) [2023-07-18T08:32:36+02:00] view original

  IIRC, OpenSSL, at least v3, gets dlopen()'d no matter what you do, which will then attempt to dynamically load things that are already statically linked. We played some low-level games to redirect the loader ourselves.

  The tech world uses static binaries heavily. It shouldn't so hard to get one in Nim (even when it's supported, it's often not easy).

---