[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAD0C5PDAa3m8M0Z68kv0wHN2d=m93CMXdG2XA63sW54yvJiR+A@mail.gmail.com>
Date: Tue, 12 Oct 2021 15:57:45 +1100
From: Matt Andrews <mattandrews@...il.com>
To: musl@...ts.openwall.com
Subject: Re: Newbie cross compiling with LLVM
> -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@...il.com> wrote:
> -fuse-ld=lld
>
> On Tue, Oct 12, 2021, 3:26 AM Jeffrey Walton <noloader@...il.com> wrote:
>
>> On Mon, Oct 11, 2021 at 7:55 PM Matt Andrews <mattandrews@...il.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
>>
>
Content of type "text/html" skipped
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
