From: jjsullivan5196 <jjsullivan5196@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: zig: cross-compile the toolchain
Date: Fri, 18 Sep 2020 20:42:34 +0200 [thread overview]
Message-ID: <20200918184234.6OF0G_7Rl7kPH7u0j3G9285f8c2KnfQt_7OnkCdnSJk@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: 1169 bytes --]
New comment by jjsullivan5196 on void-packages repository
https://github.com/void-linux/void-packages/issues/24959#issuecomment-694765306
Comment:
I think I figured out the problem, more context from irc
```
<andrewrk> I think if you run `llvm-config --system-libs` or something like that it might spit out all the missing libs
<andrewrk> for me it prints `-lz -lrt -ldl -lpthread -lm` for your config it will probably include -lxml
<andrewrk> anyway point being that dependency comes from LLVM so it's kind of a question for the llvm project how to properly link in their dependency
<andrewrk> it sounds like a packaging mishap if `llvm-config --system-libs` doesn't resolve this for you
```
So it seems that `llvm-config --system-libs` should spit out linker flags for any dependencies it needs when linking, but as it stands it just prints a blank line. This is what the cmake uses for cross dependencies. This would make me think the problem is somewhere in the `llvm10` template.
For now, manually adding the packages/linker flags appears to work. There's also a weird problem where `ld` ignores the extra flags unless `-Wl,--no-as-needed` is set.
next prev parent reply other threads:[~2020-09-18 18:42 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 [this message]
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
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=20200918184234.6OF0G_7Rl7kPH7u0j3G9285f8c2KnfQt_7OnkCdnSJk@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).