All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Christian Stewart <christian@aperture.us>
Cc: "Yann E . MORIN" <yann.morin.1998@free.fr>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v1 1/1] package/go: add toolchain as dependency of host-go
Date: Sat, 29 Jul 2023 23:05:03 +0200	[thread overview]
Message-ID: <20230729230503.774545db@windsurf> (raw)
In-Reply-To: <CA+h8R2qG4w+mHrZTZ0EmTXjH=txfGQT8-p3f_K_GqP0+8bP8hQ@mail.gmail.com>

On Fri, 28 Jul 2023 18:19:46 -0700
Christian Stewart <christian@aperture.us> wrote:

> > to ensure we build a host-go compiler capable of building code for the
> > target if the target is supported, but in all cases builds a Go
> > compiler capable of compiling code for the host. Indeed, host-go might
> > also be needed solely to build host utilities, which would be relevant
> > even if the target architecture isn't supported by Go.  
> 
> I suppose if you don't set CC_FOR_TARGET nor CXX_FOR_TARGET then the
> Go compiler will simply use CC and CXX which are HOSTCC_NOCCACHE and
> HOSTCXX_NOCCACHE.

It'd be nicer to have more certainty than "I suppose" :-)

> I noticed there's already a line which adds toolchain as a dependency
> if cgo is enabled.

Hu, where is that?

> Will mark this patch as not applicable for now and consider why the
> build failed in the TestMender test case when running "make host-go"
> without building the toolchain first. I guess that's a case where cgo
> is not enabled and yet BR2_PACKAGE_HOST_GO_TARGET_ARCH_SUPPORTS=y.
> 
> We should move the toolchain dependency to be if
> BR2_PACKAGE_HOST_GO_TARGET_ARCH_SUPPORTS instead of if Cgo is enabled,
> I think.

Possibly, and this would make sense, if indeed Go needs the target
C/C++ compiler to build the target Go stuff.

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:[~2023-07-29 21:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-28  5:25 [Buildroot] [PATCH v1 1/1] package/go: add toolchain as dependency of host-go Christian Stewart via buildroot
2023-07-28  7:26 ` Thomas Petazzoni via buildroot
2023-07-29  1:19   ` Christian Stewart via buildroot
2023-07-29 21:05     ` Thomas Petazzoni via buildroot [this message]

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=20230729230503.774545db@windsurf \
    --to=buildroot@buildroot.org \
    --cc=christian@aperture.us \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=yann.morin.1998@free.fr \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.