Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Bryce Johnson <bryce@redpinelabs.com>
Cc: buildroot@buildroot.org, Suniel Mahesh <sunil@amarulasolutions.com>
Subject: Re: [Buildroot] [PATCH] package/arm-gnu-toolchain: Add $(HOSTARCH) so it can be built with aarch64
Date: Tue, 22 Oct 2024 23:12:43 +0200	[thread overview]
Message-ID: <20241022231243.7ab36afc@windsurf> (raw)
In-Reply-To: <CADXxVS+0bHz+Hqe4437vb5K3=Qmt3DLfNSFMEmsWJTFXGkiFTg@mail.gmail.com>

Hello Bryce,

On Tue, 22 Oct 2024 14:36:44 -0600
Bryce Johnson <bryce@redpinelabs.com> wrote:

> Yes I'll do that. Finally got the git send email with my gmail account
> working and thought the Signed-off-by got added.  I'll clean up that
> and the line length as well.

Thanks, I have seen your v2, which I have applied. However, did you see
the remainder of my review? See below.

> > > -ARM_GNU_TOOLCHAIN_SOURCE = arm-gnu-toolchain-$(ARM_GNU_TOOLCHAIN_VERSION)-x86_64-arm-none-eabi.tar.xz
> > > +ARM_GNU_TOOLCHAIN_SOURCE = arm-gnu-toolchain-$(ARM_GNU_TOOLCHAIN_VERSION)-$(HOSTARCH)-arm-none-eabi.tar.xz  
> >
> > The change looks correct as-is of course, as it doesn't make anything
> > worse. However, I believe to make things cleaner, we should perhaps
> > introduce a package/arm-gnu-toolchain/Config.in.host file, with a blind
> > option BR2_HOST_PACKAGE_ARM_GNU_TOOLCHAIN, that has a "depends on" the
> > host architectures that are supported. And the packages that use
> > host-arm-gnu-toolchain would have to be careful to propagate those
> > depends on, so that we do not allow using host-arm-gnu-toolchain on
> > configurations that do not allow using the host-arm-gnu-toolchain
> > package. However this can be done as a separate patch, as again your
> > change is not making things any worse than they already are :)
> >
> > Could you send a v2 of your patch with the proposed changes?

Thanks!

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2024-10-22 21:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-22 18:05 [Buildroot] [PATCH] package/arm-gnu-toolchain: Add $(HOSTARCH) so it can be built with aarch64 bryce
2024-10-22 19:28 ` Thomas Petazzoni via buildroot
2024-10-22 20:36   ` Bryce Johnson
2024-10-22 21:12     ` Thomas Petazzoni via buildroot [this message]
2024-10-22 22:59       ` Bryce Johnson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20241022231243.7ab36afc@windsurf \
    --to=buildroot@buildroot.org \
    --cc=bryce@redpinelabs.com \
    --cc=sunil@amarulasolutions.com \
    --cc=thomas.petazzoni@bootlin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox