On Wed, Dec 04, 2024 at 02:22:09PM +, Jamie Landeg-Jones wrote:
> I'm puzzled to why this doesn't get extracted to WRKDIR, and executed there?
>
> Or is it because the downloaded toolchain is not an archive, but a bare
> executable itself? If so, I'd expect it still to be copied to WRKDIR befo
Robert Clausecker wrote:
> The reason for this is that your package requires Go 1.22 to build, but
> Go 1.21 has been configured as the toolchain to use for this package.
> Go helpfully downloads a Go 1.22 toolchain and tries to use that to build
> the package, which fails as the distfiles are no
Hi Jamie,
Am Wed, Dec 04, 2024 at 02:22:09PM + schrieb Jamie Landeg-Jones:
> Robert Clausecker wrote:
>
> > The reason for this is that your package requires Go 1.22 to build, but
> > Go 1.21 has been configured as the toolchain to use for this package.
> > Go helpfully downloads a Go 1.22 t
Hi Jamie,,
Am Wed, Dec 04, 2024 at 02:22:09PM + schrieb Jamie Landeg-Jones:
> Robert Clausecker wrote:
>
> > The reason for this is that your package requires Go 1.22 to build, but
> > Go 1.21 has been configured as the toolchain to use for this package.
> > Go helpfully downloads a Go 1.22
Am Wed, Dec 04, 2024 at 11:36:23AM +0900 schrieb Koichiro Iwao:
> Hello folks,
>
> I got the following error when trying to build some go packages. I found
> the cause so I'd like to share it if this help someone.
>
> # portmaster www/gohugo
> ===> License APACHE20 accepted by the user
> ===>
On Wed, Dec 04, 2024 at 11:36:23AM +0900 I heard the voice of
Koichiro Iwao, and lo! it spake thus:
>
> I got the following error when trying to build some go packages. I found
> the cause so I'd like to share it if this help someone.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281491
--
