Bug 6650

Summary:	Segmentation fault when trying to build latest buildroot
Product:	buildroot	Reporter:	daniel.karlsson
Component:	Other	Assignee:	unassigned
Status:	RESOLVED INVALID
Severity:	major	CC:	buildroot, daniel.karlsson
Priority:	P5
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Linux
Host:		Target:
Build:
Attachments:	Log output when bug occured

Description daniel.karlsson 2013-10-31 10:12:31 UTC

Created attachment 5114 [details]
Log output when bug occured

When trying to compile latest buildroot (checked out from git repo 2013-10-31) with the sama5d3ekdemo_defconfig, I get the following error:

/home/daniel/buildroot-at91/output/toolchain/gcc-4.7.2/libgcc/libgcc2.c: In function '__absvdi2':
/home/daniel/buildroot-at91/output/toolchain/gcc-4.7.2/libgcc/libgcc2.c:273:1 internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://bugs.buildroot.net/> for instructions.
make[2]: *** [_absvdi2.o] Error 1

There are more error of the sam type that follows, but this is the first error detected (see attachment, sorry for some words being in swedish).

Comment 1 Thomas Petazzoni 2013-10-31 10:46:23 UTC

As you can see in http://git.buildroot.net/buildroot/tree/configs, we don't have a sama5d3ekdemo_defconfig in the mainline Buildroot.

Are you sure you are using the mainline Buildroot version? We unfortunately cannot support the numerous Buildroot forks that are made by various people/organizations.

Comment 2 daniel.karlsson 2013-10-31 11:39:43 UTC

(In reply to comment #1)
> As you can see in http://git.buildroot.net/buildroot/tree/configs, we don't
> have a sama5d3ekdemo_defconfig in the mainline Buildroot.
> 
> Are you sure you are using the mainline Buildroot version? We unfortunately
> cannot support the numerous Buildroot forks that are made by various
> people/organizations.

I'm using the mainline Buildroot version but the config, as you've pointed out, is not a mainline one. I'll get in touch with the developer of that one instead.

Thank you for your swift reply!

Comment 3 Thomas Petazzoni 2013-10-31 12:02:24 UTC

Ok, if you use the mainline Buildroot, then it's fine. We should support whatever configuration you use. Can you share the defconfig you're using, and the exact Buildroot version you tested? Thanks!

Comment 4 daniel.karlsson 2013-10-31 12:10:19 UTC

(In reply to comment #3)
> Ok, if you use the mainline Buildroot, then it's fine. We should support
> whatever configuration you use. Can you share the defconfig you're using, and
> the exact Buildroot version you tested? Thanks!

There's no need. Apparently, the developer of the config had their own buildroot branch where it all worked. I also had an outdated version of the defconfig, when I tried the "new" one with the mainline buildroot, it complained about "legacy configurations", which is correct behaviour, I guess.

Thank you for your help

Comment 5 Thomas Petazzoni 2013-10-31 12:28:58 UTC

Ok, well. If you have any issue with the mainline Buildroot version, whatever configuration you use, please open a bug with the version + configuration, and we'll look into it.

In the mean time, I'll close this bug.