From: jjsullivan5196 <jjsullivan5196@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: zig: cross-compile the toolchain
Date: Sat, 19 Sep 2020 00:52:43 +0200 [thread overview]
Message-ID: <20200918225243.1RT1sTJ_toeSuJN9Dp3DgbfYKGbx9Ohr3c9TJJJLXp0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24959@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 2750 bytes --]
New comment by jjsullivan5196 on void-packages repository
https://github.com/void-linux/void-packages/issues/24959#issuecomment-695118982
Comment:
For posterity, I did an `ldd` on the `x86_64 and `aarch64` binaries
x64:
```
linux-vdso.so.1 (0x00007ffe9e1e5000)
libLLVM-10.so => /usr/lib/libLLVM-10.so (0x00007f2021f6e000)
libpthread.so.0 => /usr/lib/libpthread.so.0 (0x00007f2021f4d000)
libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x00007f2021cd7000)
libm.so.6 => /usr/lib/libm.so.6 (0x00007f2021b92000)
libc.so.6 => /usr/lib/libc.so.6 (0x00007f20219cf000)
/lib/ld-linux-x86-64.so.2 (0x00007f2027356000)
libffi.so.7 => /usr/lib/../lib/libffi.so.7 (0x00007f20219c3000)
libedit.so.0 => /usr/lib/../lib/libedit.so.0 (0x00007f2021988000)
libz.so.1 => /usr/lib/../lib/libz.so.1 (0x00007f2021771000)
libdl.so.2 => /usr/lib/../lib/libdl.so.2 (0x00007f202176c000)
libncursesw.so.6 => /usr/lib/../lib/libncursesw.so.6 (0x00007f20216fa000)
libxml2.so.2 => /usr/lib/../lib/libxml2.so.2 (0x00007f2021594000)
libgcc_s.so.1 => /usr/lib/../lib/libgcc_s.so.1 (0x00007f202157a000)
libicui18n.so.67 => /usr/lib/../lib/libicui18n.so.67 (0x00007f2021279000)
libicuuc.so.67 => /usr/lib/../lib/libicuuc.so.67 (0x00007f2021094000)
libicudata.so.67 => /usr/lib/../lib/libicudata.so.67 (0x00007f202108f000)
liblzma.so.5 => /usr/lib/../lib/liblzma.so.5 (0x00007f2021066000)
```
aarch64:
```
linux-vdso.so.1 (0x0000007fb282d000)
libdl.so.2 => /usr/lib/libdl.so.2 (0x0000007fb27d4000)
libncursesw.so.6 => /usr/lib/libncursesw.so.6 (0x0000007fb2757000)
libz.so.1 => /usr/lib/libz.so.1 (0x0000007fb2732000)
libxml2.so.2 => /usr/lib/libxml2.so.2 (0x0000007fb25c2000)
libpthread.so.0 => /usr/lib/libpthread.so.0 (0x0000007fb2592000)
libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x0000007fb231a000)
libm.so.6 => /usr/lib/libm.so.6 (0x0000007fb2271000)
libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x0000007fb224d000)
libc.so.6 => /usr/lib/libc.so.6 (0x0000007fb20df000)
/lib/ld-linux-aarch64.so.1 => /usr/lib/ld-linux-aarch64.so.1 (0x0000007fb27ff000)
libicui18n.so.67 => /usr/lib/libicui18n.so.67 (0x0000007fb1de7000)
libicuuc.so.67 => /usr/lib/libicuuc.so.67 (0x0000007fb1bf9000)
libicudata.so.67 => /usr/lib/libicudata.so.67 (0x0000007fb1be7000)
liblzma.so.5 => /usr/lib/liblzma.so.5 (0x0000007fb1bb2000)
```
So I guess that the cross step in cmake does force static linking for llvm, I only set what's in the template I linked above, no explicit options for static/dynamic.
next prev parent reply other threads:[~2020-09-18 22:52 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-17 21:42 [ISSUE] zig: cross-compile support jjsullivan5196
2020-09-17 22:07 ` jjsullivan5196
2020-09-18 9:36 ` jjsullivan5196
2020-09-18 9:36 ` jjsullivan5196
2020-09-18 11:20 ` zig: cross-compile the toolchain jjsullivan5196
2020-09-18 11:21 ` jjsullivan5196
2020-09-18 11:21 ` jjsullivan5196
2020-09-18 11:35 ` jjsullivan5196
2020-09-18 18:42 ` jjsullivan5196
2020-09-18 18:43 ` jjsullivan5196
2020-09-18 20:54 ` jjsullivan5196
2020-09-18 21:10 ` q66
2020-09-18 21:46 ` andrewrk
2020-09-18 21:47 ` andrewrk
2020-09-18 22:02 ` Johnnynator
2020-09-18 22:02 ` Johnnynator
2020-09-18 22:03 ` andrewrk
2020-09-18 22:03 ` andrewrk
2020-09-18 22:03 ` jjsullivan5196
2020-09-18 22:33 ` jjsullivan5196
2020-09-18 22:34 ` andrewrk
2020-09-18 22:36 ` jjsullivan5196
2020-09-18 22:36 ` jjsullivan5196
2020-09-18 22:52 ` jjsullivan5196
2020-09-18 22:52 ` jjsullivan5196 [this message]
2020-09-18 22:53 ` jjsullivan5196
2020-09-19 22:39 ` jjsullivan5196
2020-09-19 22:41 ` jjsullivan5196
2020-09-20 23:49 ` jjsullivan5196
2021-01-21 17:44 ` ericonr
2021-01-21 17:44 ` [ISSUE] [CLOSED] " ericonr
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200918225243.1RT1sTJ_toeSuJN9Dp3DgbfYKGbx9Ohr3c9TJJJLXp0@z \
--to=jjsullivan5196@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).