On Mon, Jan 15, 2024 at 9:49 AM Richard Purdie
wrote:
>
> On Mon, 2024-01-15 at 08:56 -0800, Khem Raj wrote:
> > Hi
> >
> > On Mon, Jan 15, 2024 at 5:19 AM Richard Purdie
> > wrote:
> > > On Sat, 2024-01-13 at 21:58 -0800, Khem Raj wrote:
> > > > target rust recipe builds ( cross compile ) calls
On Mon, 2024-01-15 at 08:56 -0800, Khem Raj wrote:
> Hi
>
> On Mon, Jan 15, 2024 at 5:19 AM Richard Purdie
> wrote:
> > On Sat, 2024-01-13 at 21:58 -0800, Khem Raj wrote:
> > > target rust recipe builds ( cross compile ) calls llvm-config
> > > from
> > > target sysroot which works ok as long as
Hi
On Mon, Jan 15, 2024 at 5:19 AM Richard Purdie <
richard.pur...@linuxfoundation.org> wrote:
> On Sat, 2024-01-13 at 21:58 -0800, Khem Raj wrote:
> > target rust recipe builds ( cross compile ) calls llvm-config from
> > target sysroot which works ok as long as C++ runtime it needs is
> >
On Sat, 2024-01-13 at 21:58 -0800, Khem Raj wrote:
> target rust recipe builds ( cross compile ) calls llvm-config from
> target sysroot which works ok as long as C++ runtime it needs is
> available on build host e.g. libstdc++ etc. which is commonly the
> case, however when using clang and llvm
target rust recipe builds ( cross compile ) calls llvm-config from
target sysroot which works ok as long as C++ runtime it needs is
available on build host e.g. libstdc++ etc. which is commonly the
case, however when using clang and llvm runtime this falters since
it should be using libc++ from