From: Nagakamira <nagakamira@gmail.com>
To: musl@lists.openwall.com
Subject: Re: [musl] Newbie cross compiling with LLVM
Date: Tue, 12 Oct 2021 09:09:18 +0300 [thread overview]
Message-ID: <CAEqUM+eC90xzbVzznE9ZU+QUhf3vSHqRKeEWhTSQ-NyahZZXPQ@mail.gmail.com> (raw)
In-Reply-To: <CAD0C5PDA_Q3mWZMvLokmLqtpFTLBRR36eAXn5un3DL84vG=RuA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1923 bytes --]
You can pass --unwindlib=libunwind and rtlib, they are both link options
On Tue, Oct 12, 2021, 8:55 AM Matt Andrews <mattandrews@gmail.com> wrote:
> > --rtlib=compiler-rt
>
> Is that a compiler option or a linker option? I used it in both places,
> but still get the same error.
>
> On Tue, Oct 12, 2021 at 4:00 PM Nagakamira <nagakamira@gmail.com> wrote:
>
>> --rtlib=compiler-rt
>>
>> On Tue, Oct 12, 2021, 7:58 AM Matt Andrews <mattandrews@gmail.com> wrote:
>>
>>> > -fuse-ld=lld
>>>
>>> I actually used
>>>
>>> -fuse-ld=ld.lld
>>>
>>> That did the trick, but has unlocked another error
>>>
>>> ld.lld: error: unable to find library -lgcc
>>> ld.lld: error: unable to find library -lgcc_eh
>>>
>>> I thought musl compiles with it's own headers?
>>>
>>> On Tue, Oct 12, 2021 at 3:54 PM Nagakamira <nagakamira@gmail.com> wrote:
>>>
>>>> -fuse-ld=lld
>>>>
>>>> On Tue, Oct 12, 2021, 3:26 AM Jeffrey Walton <noloader@gmail.com>
>>>> wrote:
>>>>
>>>>> On Mon, Oct 11, 2021 at 7:55 PM Matt Andrews <mattandrews@gmail.com>
>>>>> wrote:
>>>>> >
>>>>> > >> How do I specify which linker to use?
>>>>> > >
>>>>> > >LD. Also see
>>>>> https://www.gnu.org/software/make/manual/html_node/Implicit-Variables.html
>>>>> .
>>>>> >
>>>>> > Looking at the ./configure for musl (which is not based on autoconf
>>>>> according to the docs), there is no mention of LD. Setting LD for
>>>>> ./configure and/or the call to make still results in the error.
>>>>> >
>>>>> > Who calls the linker? The compiler or make? Shouldn't clang know
>>>>> where it's linker is? How to tell clang which linker to use?
>>>>>
>>>>> You can have the compiler driver call the linker for you by specifying
>>>>> -o with an output file name. In that case, $CC or $CXX will drive the
>>>>> link. And in this case, your LDFLAGS should prefix options with -Wl to
>>>>> tell the compiler driver the option is for the linker.
>>>>>
>>>>> Jeff
>>>>>
>>>>
[-- Attachment #2: Type: text/html, Size: 3808 bytes --]
next prev parent reply other threads:[~2021-10-12 6:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-10 20:56 Matt Andrews
2021-10-10 22:43 ` Quentin Rameau
2021-10-10 23:21 ` Matt Andrews
2021-10-11 17:20 ` Khem Raj
2021-10-11 17:40 ` Jeffrey Walton
2021-10-11 23:55 ` Matt Andrews
2021-10-12 0:24 ` Jeffrey Walton
2021-10-12 4:53 ` Nagakamira
2021-10-12 4:57 ` Matt Andrews
2021-10-12 5:00 ` Nagakamira
2021-10-12 5:55 ` Matt Andrews
2021-10-12 6:09 ` Nagakamira [this message]
2021-10-13 2:34 ` Matt Andrews
2021-10-13 5:35 ` Nagakamira
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=CAEqUM+eC90xzbVzznE9ZU+QUhf3vSHqRKeEWhTSQ-NyahZZXPQ@mail.gmail.com \
--to=nagakamira@gmail.com \
--cc=musl@lists.openwall.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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).