On Sat, Aug 24, 2024 at 12:14 AM Daniel Gomez (Samsung)
wrote:
>
> On Fri, Aug 23, 2024 at 6:13 PM Masahiro Yamada wrote:
> >
> > On Wed, Aug 7, 2024 at 8:10 AM Daniel Gomez via B4 Relay
> > wrote:
> > >
> > > From: Nick Desaulniers
> > >
> > > When building the Linux kernel on an aarch64 MacOS
On Fri, Aug 23, 2024 at 6:13 PM Masahiro Yamada wrote:
>
> On Wed, Aug 7, 2024 at 8:10 AM Daniel Gomez via B4 Relay
> wrote:
> >
> > From: Nick Desaulniers
> >
> > When building the Linux kernel on an aarch64 MacOS based host, if we don't
> > specify a value for ARCH when invoking make, we defau
On Wed, Aug 7, 2024 at 8:10 AM Daniel Gomez via B4 Relay
wrote:
>
> From: Nick Desaulniers
>
> When building the Linux kernel on an aarch64 MacOS based host, if we don't
> specify a value for ARCH when invoking make, we default to arm and thus
> multi_v7_defconfig rather than the expected arm64 a
On Wed, Aug 07, 2024 at 01:09:15AM +0200, Daniel Gomez via B4 Relay wrote:
> From: Nick Desaulniers
>
> When building the Linux kernel on an aarch64 MacOS based host, if we don't
> specify a value for ARCH when invoking make, we default to arm and thus
> multi_v7_defconfig rather than the expecte
From: Nick Desaulniers
When building the Linux kernel on an aarch64 MacOS based host, if we don't
specify a value for ARCH when invoking make, we default to arm and thus
multi_v7_defconfig rather than the expected arm64 and arm64's defconfig.
This is because subarch.include invokes `uname -m` wh
