Re: [Buildroot] crucible: Build failure on riscv64/mips64el

From: Arnout Vandecappelle via buildroot <buildroot@buildroot.org>
To: Fabio Estevam <festevam@gmail.com>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: Christian Stewart <christian@aperture.us>,
	buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] crucible: Build failure on riscv64/mips64el
Date: Thu, 19 Sep 2024 13:55:53 +0200	[thread overview]
Message-ID: <18b7c354-da3a-47fd-a424-d0391eea9fac@mind.be> (raw)
In-Reply-To: <CAOMZO5DbYXhKjwpyoLUFhV97_VZ076ExChBWmAzU8Z5FN-M6kQ@mail.gmail.com>

On 19/09/2024 05:21, Fabio Estevam wrote:
> Hi,
> 
> On Wed, Jul 24, 2024 at 5:10 PM Thomas Petazzoni
> <thomas.petazzoni@bootlin.com> wrote:
> 
>> I agree that we don't really care about crucible on RISC-V 64-bit and
>> mips64el. However, the build failures you're pointing to don't seem to
>> be caused by anything ARM-specific in the crucible code base. Instead
>> they look like relatively generic issues with our Go integration.
>>
>> Christian, do you think you could have a look at the above two
>> failures, which really don't seem to be related to the crucible code,
>> but more general Go issues.
>>
>> The first one:
>>
>> $WORK/b071/_pkg_.a(_x001.o): unknown relocation type 17; compiled without -fpic?
>> $WORK/b078/_pkg_.a(_x005.o): unknown relocation type 17; compiled without -fpic?
>>
>> is really mysterious to me.
>>
>> The second one:
>>
>> /home/autobuild/autobuild/instance-9/output-1/host/lib/gcc/mips64el-buildroot-linux-gnu/13.3.0/../../../../mips64el-buildroot-linux-gnu/bin/ld: /tmp/go-link-2044248803/go.o: linking -mnan=legacy module with previous -mnan=2008 modules
>>
>> is related to the fact that different object files/libraries have been
>> built with diffent -mnan arguments, and we try to link them together,
>> which isn't correct. The configuration has BR2_MIPS_NAN_2008=y, so
>> we're supposed to be building everything with -mnan=2008, but it seems
>> like some Go stuff tries to use -mnan=legacy instead.
>>
>> If you could help with those weird Go issues, it would be much, much
>> appreciated.
> 
> Can anyone please help with these Go issues?
> 
> I keep getting build failure reports for the crucible package.
> 
> Here is another one:
> https://autobuild.buildroot.org/results/b56d9376bd758081e27bc349c192783ece22a4fb/build-end.log

  If we don't find a solution I think we should disable Go entirely for these 
architectures. Until someone shows up who is willing to put in the effort to 
make it work.

  Regards,
  Arnout

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