Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/9] iMX6S-PICO: add default config file (imx6spico_defconfig)
Date: Wed, 11 Oct 2017 17:34:25 +0200	[thread overview]
Message-ID: <20171011173425.175f716e@windsurf.lan> (raw)
In-Reply-To: <CAKrb2soZLWtymDeToLxPmk=Vtdt0E+wT5KHMcCa6x-BLukSCaQ@mail.gmail.com>

Hello,

Please do not reply just to me, keep the mailing list in Cc by using
"Reply All" instead of "Reply". Thanks. I've re-added the mailing list
in Cc.

On Wed, 11 Oct 2017 17:32:08 +0200, Alexandre Gambier wrote:

> > > If I use the latest GCC version, it fails building the root fs.  
> >
> > With what error? We definitely want to fix this, and not paper over the
> > problem by reverting back to gcc 5.x.
> >  
> 
> It fails building uboot here's the log...

Ok, so it doesn't fail when building the rootfs, but when building
U-Boot.


> scripts/kconfig/conf --silentoldconfig Kconfig
>   CHK     include/config.h
>   UPD     include/config.h
>   GEN     include/autoconf.mk
>   GEN     include/autoconf.mk.dep
>   GEN     spl/include/autoconf.mk
> In file included from include/linux/compiler.h:54:0,
>                  from include/linux/byteorder/little_endian.h:12,
>                  from ./arch/arm/include/asm/byteorder.h:29,
>                  from include/compiler.h:125,
>                  from include/image.h:19,
>                  from ./include/common.h:82:
> include/linux/compiler-gcc.h:114:30: fatal error: linux/compiler-gcc6.h: No
> such file or directory

This is known issue with old versions of U-Boot.

You can try adding
board/roseapplepi/patches/uboot/0001-compiler-.h-sync-include-linux-compiler-.h-with-Linu.patch
as a U-Boot patch, or preferably update your U-Boot to a more recent
version.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  parent reply	other threads:[~2017-10-11 15:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-11 12:19 [Buildroot] [PATCH 1/9] iMX6S-PICO: add default config file (imx6spico_defconfig) Alexandre Gambier
2017-10-11 12:19 ` [Buildroot] [PATCH 2/9] iMX6S-PICO: add linux default config file (defconfig) Alexandre Gambier
2017-10-11 12:19 ` [Buildroot] [PATCH 3/9] iMX6S-PICO: add post image scripts Alexandre Gambier
2017-10-11 12:19 ` [Buildroot] [PATCH 4/9] iMX6S-PICO: add firmware files (nvram*) Alexandre Gambier
2017-10-11 12:19 ` [Buildroot] [PATCH 5/9] iMX6S-PICO: add firmware files (bcm*) Alexandre Gambier
2017-10-11 12:19 ` [Buildroot] [PATCH 6/9] iMX6S-PICO: add firmware files (bcmfmac*) Alexandre Gambier
2017-10-11 13:14 ` [Buildroot] [PATCH 1/9] iMX6S-PICO: add default config file (imx6spico_defconfig) Thomas Petazzoni
2017-10-11 16:34   ` Arnout Vandecappelle
2017-10-11 13:17 ` Thomas Petazzoni
     [not found]   ` <CAKrb2srEz1UeT-RJgY7NCEDp28OX7xGq=JD5qOvR_eZBkkahKg@mail.gmail.com>
     [not found]     ` <20171011164908.3cc14130@windsurf.lan>
     [not found]       ` <CAKrb2soZLWtymDeToLxPmk=Vtdt0E+wT5KHMcCa6x-BLukSCaQ@mail.gmail.com>
2017-10-11 15:34         ` Thomas Petazzoni [this message]
2017-10-11 16:04 ` Fabio Estevam
2017-10-11 16:06   ` Fabio Estevam
2017-10-11 16:26 ` Arnout Vandecappelle

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20171011173425.175f716e@windsurf.lan \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox