[Buildroot] [PATCH] package/crucible: disable cgo to fix 32-bit build failures

[Buildroot] [PATCH] package/crucible: disable cgo to fix 32-bit build failures

[Fabio Estevam]

The Buildroot autobuilder fails when building crucible on 32-bit
architectures (notably i386) due to unresolved _cgo_* symbols during
linking.

Crucible does not require cgo, and building it with CGO_ENABLED=0
avoids toolchain and linker issues while producing a fully functional
binary.

Disable cgo explicitly to ensure reliable builds across all supported
architectures.

Fixes:

https://autobuild.buildroot.org/results/0b59fb382f7a1d9c3644da71e7bd53b6a19418ce/build-end.log

Signed-off-by: Fabio Estevam <festevam@gmail.com>
---
 package/crucible/crucible.mk | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/package/crucible/crucible.mk b/package/crucible/crucible.mk
index 9b34cc52d950..6f6d1dfab94b 100644
--- a/package/crucible/crucible.mk
+++ b/package/crucible/crucible.mk
@@ -10,4 +10,7 @@ CRUCIBLE_LICENSE = BSD-3-Clause
 CRUCIBLE_LICENSE_FILES = LICENSE
 CRUCIBLE_GOMOD = ./cmd/crucible
 
+# Disable cgo to avoid toolchain/linker issues on 32-bit architectures
+CRUCIBLE_GO_ENV = CGO_ENABLED=0
+
 $(eval $(golang-package))
-- 
2.34.1

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

Re: [Buildroot] [PATCH] package/crucible: disable cgo to fix 32-bit build failures

[Thomas Petazzoni via buildroot]

Hello Fabio,

Thanks for the patch. Adding Christian to the loop. Christian, could
you comment on the below patch and help us understand whether this is
the right fix?

Fabio, one comment/request below.

On Sat, 27 Dec 2025 18:22:44 -0300
Fabio Estevam <festevam@gmail.com> wrote:

> The Buildroot autobuilder fails when building crucible on 32-bit
> architectures (notably i386) due to unresolved _cgo_* symbols during
> linking.
> 
> Crucible does not require cgo, and building it with CGO_ENABLED=0
> avoids toolchain and linker issues while producing a fully functional
> binary.
> 
> Disable cgo explicitly to ensure reliable builds across all supported
> architectures.
> 
> Fixes:
> 
> https://autobuild.buildroot.org/results/0b59fb382f7a1d9c3644da71e7bd53b6a19418ce/build-end.log
> 
> Signed-off-by: Fabio Estevam <festevam@gmail.com>

In commit logs, we like to have some details on what initially
introduced the problem, so that we can understand whether the patch is
a fix that should be backported to our LTS release. Ideally a pointer
to the Buildroot commit introducing the problem. If not, at least some
indication that the problem exists since <some time> (to be specified,
with an old autobuilder failure). In our case, we're mostly interested
in understanding whether that fix should be backported to Buildroot
2025.02.x. So if the problem already existed prior to February 2025, we
will want to backport it.

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

Re: [Buildroot] [PATCH] package/crucible: disable cgo to fix 32-bit build failures

[Christian Stewart via buildroot]

Hi all,

On Tue, Jan 6, 2026 at 1:07 PM Thomas Petazzoni
<thomas.petazzoni@bootlin.com> wrote:
>
> Hello Fabio,
>
> Thanks for the patch. Adding Christian to the loop. Christian, could
> you comment on the below patch and help us understand whether this is
> the right fix?
>
> Fabio, one comment/request below.
>
> On Sat, 27 Dec 2025 18:22:44 -0300
> Fabio Estevam <festevam@gmail.com> wrote:
>
> > The Buildroot autobuilder fails when building crucible on 32-bit
> > architectures (notably i386) due to unresolved _cgo_* symbols during
> > linking.
> >
> > Crucible does not require cgo, and building it with CGO_ENABLED=0
> > avoids toolchain and linker issues while producing a fully functional
> > binary.
> >
> > Disable cgo explicitly to ensure reliable builds across all supported
> > architectures.
> >
> > Fixes:
> >
> > https://autobuild.buildroot.org/results/0b59fb382f7a1d9c3644da71e7bd53b6a19418ce/build-end.log
> >
> > Signed-off-by: Fabio Estevam <festevam@gmail.com>
>

If Cgo is not required, then disabling it should be OK.

Looks good to me!

Reviewed-by: Christian Stewart <christian@aperture.us>
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

Re: [Buildroot] [PATCH] package/crucible: disable cgo to fix 32-bit build failures

[Fabio Estevam]

Hi Thomas,

On Tue, Jan 6, 2026 at 6:07 PM Thomas Petazzoni
<thomas.petazzoni@bootlin.com> wrote:

> In commit logs, we like to have some details on what initially
> introduced the problem, so that we can understand whether the patch is
> a fix that should be backported to our LTS release. Ideally a pointer
> to the Buildroot commit introducing the problem. If not, at least some
> indication that the problem exists since <some time> (to be specified,
> with an old autobuilder failure). In our case, we're mostly interested
> in understanding whether that fix should be backported to Buildroot
> 2025.02.x. So if the problem already existed prior to February 2025, we
> will want to backport it.

This failure has been present since the introduction of the crucible
support in Buildroot.

It is OK to backport this fix to older releases.

Thanks
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

Re: [Buildroot] [PATCH] package/crucible: disable cgo to fix 32-bit build failures

[Fabio Estevam]

On Tue, Jan 6, 2026 at 11:06 PM Fabio Estevam <festevam@gmail.com> wrote:
>
> Hi Thomas,
>
> On Tue, Jan 6, 2026 at 6:07 PM Thomas Petazzoni
> <thomas.petazzoni@bootlin.com> wrote:
>
> > In commit logs, we like to have some details on what initially
> > introduced the problem, so that we can understand whether the patch is
> > a fix that should be backported to our LTS release. Ideally a pointer
> > to the Buildroot commit introducing the problem. If not, at least some
> > indication that the problem exists since <some time> (to be specified,
> > with an old autobuilder failure). In our case, we're mostly interested
> > in understanding whether that fix should be backported to Buildroot
> > 2025.02.x. So if the problem already existed prior to February 2025, we
> > will want to backport it.
>
> This failure has been present since the introduction of the crucible
> support in Buildroot.
>
> It is OK to backport this fix to older releases.

Ping. I keep receiving emails of crucible build failures.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot