From: Johnnynator <Johnnynator@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: zig: cross-compile the toolchain
Date: Sat, 19 Sep 2020 00:02:21 +0200 [thread overview]
Message-ID: <20200918220221.Z1lfzJsZgcD3widKnIzKS_AifOP_DP9bTtAj3lU71xM@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: 537 bytes --]
New comment by Johnnynator on void-packages repository
https://github.com/void-linux/void-packages/issues/24959#issuecomment-695106184
Comment:
> How could you be getting an undefined reference to -ldl if it's dynamically linked?
You can obviously get undefined references if you don't link against libdl, you only need to link against it, if you want to use any of the symbols it provides. If you use `dlopen` or `dlclose` you should link against `${CMAKE_DL_LIBS}` https://cmake.org/cmake/help/latest/variable/CMAKE_DL_LIBS.html
next prev parent reply other threads:[~2020-09-18 22:02 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 [this message]
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=20200918220221.Z1lfzJsZgcD3widKnIzKS_AifOP_DP9bTtAj3lU71xM@z \
--to=johnnynator@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).