From: Herve Jourdain <herve.jourdain@neuf.fr>
To: 'Paul Barker' <paul@paulbarker.me.uk>, 'Jonathan Liu' <net147@gmail.com>
Cc: 'Yocto Project' <yocto@yoctoproject.org>
Subject: Re: gcc-6.1 and raspi
Date: Sun, 5 Jun 2016 14:14:29 +0200 [thread overview]
Message-ID: <013701d1bf23$d3fba520$7bf2ef60$@neuf.fr> (raw)
In-Reply-To: <20160605122132.2a8c70a1@nuc.betafive.co.uk>
Hi,
I'm using kernel 4.4, and it does build properly with gcc 6.1.
But the build does fail on other packages later on, so I ended up reverting
to 5.3 for now.
I also think we should make 4.4 the default kernel version for
meta-raspberrypi, to follow the raspberrypi repository. The fixes on 4.1 are
far from what can be seen on 4.4 now (on the part that I'm involved with,
vc4 on 4.1 is not functional, while it is on 4.4 and later). And it will
only grow worse.
Herve
-----Original Message-----
From: yocto-bounces@yoctoproject.org [mailto:yocto-bounces@yoctoproject.org]
On Behalf Of Paul Barker
Sent: dimanche 5 juin 2016 13:22
To: Jonathan Liu <net147@gmail.com>
Cc: Yocto Project <yocto@yoctoproject.org>
Subject: Re: [yocto] gcc-6.1 and raspi
On Sun, 5 Jun 2016 20:44:42 +1000
Jonathan Liu <net147@gmail.com> wrote:
> On 5 June 2016 at 09:00, Trevor Woerner <twoerner@gmail.com> wrote:
> > Has anyone tried building a raspi image lately from master?
> >
> > ERROR: linux-raspberrypi-1_4.1.21+gitAUTOINC+ff45bc0e89-r0
> > do_compile: Function failed: do_compile
> >
> > | In file included
> > from
> > /z/layerindex-master/raspi2/tmp/work-shared/raspberrypi2/kernel-sour
> > ce/include/linux/compiler.h:54:0,
> > |
> > from
> > /z/layerindex-master/raspi2/tmp/work-shared/raspberrypi2/kernel-sour
> > ce/include/uapi/linux/stddef.h:1,
> > |
> > from
> > /z/layerindex-master/raspi2/tmp/work-shared/raspberrypi2/kernel-sour
> > ce/include/linux/stddef.h:4,
> > |
> > from
> > /z/layerindex-master/raspi2/tmp/work-shared/raspberrypi2/kernel-sour
> > ce/include/uapi/linux/posix_types.h:4,
> > |
> > from
> > /z/layerindex-master/raspi2/tmp/work-shared/raspberrypi2/kernel-sour
> > ce/include/uapi/linux/types.h:13,
> > |
> > from
> > /z/layerindex-master/raspi2/tmp/work-shared/raspberrypi2/kernel-sour
> > ce/include/linux/types.h:5,
> > |
> > from
> > /z/layerindex-master/raspi2/tmp/work-shared/raspberrypi2/kernel-sour
> > ce/include/linux/mod_devicetable.h:11,
> > |
> > from
/z/layerindex-master/raspi2/tmp/work-shared/raspberrypi2/kernel-source/scrip
ts/mod/devicetable-offsets.c:2:
> > |
/z/layerindex-master/raspi2/tmp/work-shared/raspberrypi2/kernel-source/inclu
de/linux/compiler-gcc.h:121:30:
> > fatal error: linux/compiler-gcc6.h: No such file or directory
>
> I can confirm this issue.
>
> Regards,
> Jonathan
I can get a successful build with my kernel branch where I've merged the
latest 4.1.y upstream stable release into the Raspberry Pi 4.1.y branch
(https://gitlab.com/oryx/linux-oryx-rpi). I don't have the time to bisect
this right now but one commit stands out as an obvious candidate for being
the fix:
compiler-gcc: integrate the various compiler-gcc[345].h files
https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/
?h=linux-4.1.y&id=f320793e52aee78f0fbb8bcaf10e6614d2e67bfc
I can also get a successful build using the recipe for the 4.4.y branch in
meta-raspberrypi. The Raspberry Pi repository has moved over to the 4.4.y
branch as the default, we should probably do the same in meta-raspberrypi.
Thanks,
Paul Barker
--
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
next prev parent reply other threads:[~2016-06-05 12:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-04 23:00 gcc-6.1 and raspi Trevor Woerner
2016-06-05 10:44 ` Jonathan Liu
2016-06-05 11:21 ` Paul Barker
2016-06-05 12:14 ` Herve Jourdain [this message]
2016-06-05 12:58 ` Trevor Woerner
2016-06-05 14:55 ` ***SPAM*** " Herve Jourdain
2016-06-05 20:08 ` Trevor Woerner
2016-06-05 21:38 ` Herve Jourdain
2016-06-05 23:36 ` Trevor Woerner
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='013701d1bf23$d3fba520$7bf2ef60$@neuf.fr' \
--to=herve.jourdain@neuf.fr \
--cc=net147@gmail.com \
--cc=paul@paulbarker.me.uk \
--cc=yocto@yoctoproject.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.