[llvm-dev] ld.lld fails with "undefined symbol: _fopen" on macOS, while working as expected on Linux

[Ivan Medoedov via llvm-dev]

> There's no official source really. Systems can vary so much that it's
probably best to take it from the system you're cross-compiling for.

I think it would be good to add this information to the docs:
https://clang.llvm.org/docs/CrossCompilation.html

Right now it says "When you have extracted your cross-compiler from a zip
file into a directory", so it's not clear that the user must assemble this
zip file themselves.


On Fri, Jun 7, 2019 at 11:28 PM Ivan Medoedov <ivan.medoedov at gmail.com>
wrote:

> I managed to make it work by just copying everything from /usr/include,
> /usr/lib/, and /lib.
>
> It works surprisingly well.
>
> Thanks a lot, Tim!
>
> On Fri, Jun 7, 2019 at 11:07 PM Tim Northover <t.p.northover at gmail.com>
> wrote:
>
>> On Fri, 7 Jun 2019 at 13:44, Ivan Medoedov <ivan.medoedov at gmail.com>
>> wrote:
>> > I have a silly question: where can I download the mentioned zip file
>> with all bin, lib, and include files for x64 Linux target?
>>
>> There's no official source really. Systems can vary so much that it's
>> probably best to take it from the system you're cross-compiling for.
>>
>> > So far I've been copying files one by one (/lib64/ld-linux-x86-64.so.2
>> /usr/lib/x86_64-linux-gnu/crt1.o /usr/lib/x86_64-linux-gnu/crti.o, etc) and
>> it's been a painful process.
>>
>> I'd probably tar up all of /usr/lib, /usr/include, and /lib rather
>> than copying them one at a time. For many use-cases that would be
>> enough, but if you've got a build-system that uses pkg-config or
>> something things rapidly get harder.
>>
>> Cheers.
>>
>> Tim.
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20200217/f77dff06/attachment.html>