2018-09-19 2:16 GMT+09:00 Nick Desaulniers :
> On Mon, Sep 17, 2018 at 7:32 PM Stefan Agner wrote:
>>
>> When using a GCC cross toolchain which is not in a compiled in
>> Clang search path, Clang reverts to the system assembler and
>> linker. This leads to assembler or linker errors, depending on
On Mon, Sep 17, 2018 at 7:32 PM Stefan Agner wrote:
>
> When using a GCC cross toolchain which is not in a compiled in
> Clang search path, Clang reverts to the system assembler and
> linker. This leads to assembler or linker errors, depending on
> which tool is first used for a given architecture
Hi Stefan,
2018-09-18 12:11 GMT+09:00 Stefan Agner :
> On 17.09.2018 20:06, Masahiro Yamada wrote:
>> Hi Stefan,
>>
>> 2018-09-18 11:31 GMT+09:00 Stefan Agner :
>>> When using a GCC cross toolchain which is not in a compiled in
>>> Clang search path, Clang reverts to the system assembler and
>>> l
On 17.09.2018 20:06, Masahiro Yamada wrote:
> Hi Stefan,
>
> 2018-09-18 11:31 GMT+09:00 Stefan Agner :
>> When using a GCC cross toolchain which is not in a compiled in
>> Clang search path, Clang reverts to the system assembler and
>> linker. This leads to assembler or linker errors, depending on
Hi Stefan,
2018-09-18 11:31 GMT+09:00 Stefan Agner :
> When using a GCC cross toolchain which is not in a compiled in
> Clang search path, Clang reverts to the system assembler and
> linker. This leads to assembler or linker errors, depending on
> which tool is first used for a given architecture.
When using a GCC cross toolchain which is not in a compiled in
Clang search path, Clang reverts to the system assembler and
linker. This leads to assembler or linker errors, depending on
which tool is first used for a given architecture.
It seems that Clang is not searching $PATH for a matching
as
6 matches
Mail list logo