From: andrewrk <andrewrk@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: zig: cross-compile the toolchain
Date: Fri, 18 Sep 2020 23:46:04 +0200 [thread overview]
Message-ID: <20200918214604.jQtlhmiUOusNmazPZhKH01_kAV2jYiNckolzKF-ZGv8@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: 853 bytes --]
New comment by andrewrk on void-packages repository
https://github.com/void-linux/void-packages/issues/24959#issuecomment-695100315
Comment:
howdy! I'm happy to help out here, it's not my intention to play the blame game, I'm here to help get everything working :)
> it needs an AVR codegen target for cross targets
this is not quite right - we enable it for the bootstrap build but it's not required for system packages to have it enabled. anyway it hardly matters because AVR is enabled by default in LLVM 11.
> (.text._ZN4llvm3sys14DynamicLibrary9HandleSet7DLCloseEPv+0x0): undefined reference to `dlclose'
How could you be getting an undefined reference to -ldl if it's dynamically linked?
@jjsullivan5196 what happens if you follow the directions from Zig's README using all default options, and don't try to do anything clever?
next prev parent reply other threads:[~2020-09-18 21:46 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 [this message]
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=20200918214604.jQtlhmiUOusNmazPZhKH01_kAV2jYiNckolzKF-ZGv8@z \
--to=andrewrk@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).