> -----Original Message----- > From: Jerin Jacob <jerinjac...@gmail.com> > Sent: Sunday, October 4, 2020 10:30 AM > To: Juraj Linkeš <juraj.lin...@pantheon.tech> > Cc: Thomas Monjalon <tho...@monjalon.net>; David Marchand > <david.march...@redhat.com>; Aaron Conole <acon...@redhat.com>; > Michael Santana <maicolgabr...@hotmail.com>; dpdk-dev <dev@dpdk.org> > Subject: Re: [dpdk-dev] [PATCH v2 1/3] build: add aarch64 clang to meson > cross- > compile > > On Thu, Oct 1, 2020 at 4:07 PM Juraj Linkeš <juraj.lin...@pantheon.tech> > wrote: > > > > Create meson cross file arm64_armv8_linux_clang_ubuntu1804. > > Use clang/LLVM toolchain with sysroot pointing to gcc cross stdlib. > > > > Signed-off-by: Juraj Linkeš <juraj.lin...@pantheon.tech> > > --- > > config/arm/arm64_armv8_linux_clang_ubuntu1804 | 20 > > +++++++++++++++++++ > > IMO, if we are adding a specific OS distribution-specific configuration then > it > won't scale. > Why not have just arm64_armv8_linux_clang ?
CFLAGS, LDFLAGS, c_args and c_link_args don't work when cross-compiling (at least they didn't work when I tested it) and that means we have to put the paths to stdlib (which llvm/clang doesn't implement) into a cross file. The arm64_armv8_linux_clang_ubuntu1804 contains paths that work with ubuntu clang/gcc packages (and would thus be used in CI). We can't have a generic cross file for clang because of this path limitation.
