Skip to contentSkip to conversation

BR2_HOST_GCC_AT_LEAST_4_8 not set but toolchain > linaro-7.3-2018.05 !?

Buildroot Andreas Ziegler 2 participants 4 messages Feb 6, 2021 – Feb 9, 2021 2 messages not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw
Quoted 5 lines

Date: Fri, 5 Feb 2021 20:07:34 +0100
Subject: [Buildroot] BR2_HOST_GCC_AT_LEAST_4_8 not set but toolchain

	linaro-7.3-2018.05 !?
Message-ID:
	<CAGshWo2d2hWBWQ-02Eb89YpdnR7Ck6cezX=+grKu91sRf1ObQw@mail.gmail.com>

Hi Emmanuel,

Quoted 3 lines

I build buildroot 2018.11.4 with external toolchain linaro-7.3-2018.05. I could not activate the QT5WEBENGINE because I have BR2_HOST_GCC_AT_LEAST_4_8 [=n]

HOST_GCC is your host compiler, the Linaro toolchain the cross compiler.

HOST_GCC refers to the toolchain on your build machine. Since it is improbable your host computer has a compiler with version < 5 installed, something must be wrong in your configuration or the way you start the Buildroot make. Do you have environment variables set related to compiler or cross compiling? The host path should not contain the target toolchain,@least not in first place ...

Buildroot parses the output of 'gcc --version' to eventually set the BR2_HOST_GCC_AT_LEAST variables, so maybe start looking there.

Kind regards,
Andreas

A message that is not in the archive (sent off-list or not yet received): CAGshWo1TDiuuYmRWOF-=jbxdMkbDeuK6Ukp3fnzvx6PKtbad5A@mail.gmail.com

#3 lore raw

Hi Emmanuel,

... please keep the mailing list on CC.

Quoted 4 lines · manu f

I think the problem come from the fact my gcc host is version 9 and there are no rule in buildroot 2018.11.x version I compile for this version (gcc 9 was not existing)
Could you confirm this ?

You already found it by yourself: the 2018 version stops at gcc-8; gcc-9 was added in Feb 2020. [1]

I can think of three options:

(1) Patch your current Buildroot installation (no support)
(2) Upgrade to Buildroot 2020.02 (may break your target firmware)
(3) Install gcc 8.x on your host machine

Any specific reason for the 2018.11 version?

Kind regards,
Andreas

[1] https://github.com/buildroot/buildroot/commit/1776190fb19f

#4 lore raw

Sorry Andreas ..
Reason is the initial project was with this version. Regards

Le mar. 9 f?vr. 2021 ? 18:05, Andreas Ziegler <[email protected]> a ?crit :

Quoted 20 lines

Hi Emmanuel,

... please keep the mailing list on CC.

Quoted 4 lines · manu f

I think the problem come from the fact my gcc host is version 9 and there are no rule in buildroot 2018.11.x version I compile for this version (gcc 9 was not existing)
Could you confirm this ?

You already found it by yourself: the 2018 version stops at gcc-8; gcc-9 was added in Feb 2020. [1]

I can think of three options:

(1) Patch your current Buildroot installation (no support)
(2) Upgrade to Buildroot 2020.02 (may break your target firmware)
(3) Install gcc 8.x on your host machine

Quoted 7 lines

Any specific reason for the 2018.11 version?

Kind regards,
Andreas

[1] https://github.com/buildroot/buildroot/commit/1776190fb19f

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20210209/fe282303/attachment.html>

#5 lore raw

Hi Emmanuel

Quoted 1 line · manu f

Sorry Andreas ..

No problem.

Quoted 1 line

Reason is the initial project was with this version.

You could try a quick port. Export /import your defconfig into a more recent Buildroot version. If this builds with less problems, stick with the new version, otherwise recreate the original build environment, starting with the Linux distribution.

Kind regards,
Andreas