From: Martin Jansa <martin.jansa@gmail.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: Yocto Project <yocto@yoctoproject.org>,
openembeded-devel <Openembedded-devel@lists.openembedded.org>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [RFT] GCC 8.1
Date: Thu, 17 May 2018 12:46:40 +0200 [thread overview]
Message-ID: <20180517104640.GA1398@jama> (raw)
In-Reply-To: <20180510191145.GA1954@jama>
[-- Attachment #1: Type: text/plain, Size: 6643 bytes --]
On Thu, May 10, 2018 at 09:11:45PM +0200, Martin Jansa wrote:
> > > 5) nativesdk-libxcrypt fails to build (not sure which change caused
> > > this, it build OK with sumo since the -std=gnu99 addition.
> > > ../git/crypt-sunmd5.c:189:13: error: 'snprintf' output may be truncated
> > > before the last format character [-Werror=format-truncation=]
> > > "$" CRYPT_ALGNAME "," ROUNDS "%u$%s$",
> > > ^~~
> > >
> >
> > something new, I will look into reproducing this.
The fix from you worked for me, thanks!
> > > I didn't get very far in testing, because our old kernel fails to build
> > > with gcc8 and there are some other issues caused by other master
> > > changes. But it doesn't look too bad (in my small test, lets see what
> > > bitbake world will show), thanks a lot for new gcc.
> > >
> >
> > yes, older kernel needs fixes, especially to disable new warnings.
> > the mips/ppc fixes that I put out there might be helpful to cook up
> > fixes for older kernels if running into same issues.
>
> In this case it fails with Error: .err encountered for many drivers. It's not the same case as in:
> http://lists.infradead.org/pipermail/linux-arm-kernel/2015-February/325615.html
> nor arm version of this change, both are already applied in our
> 4.4.3 based kernel.
>
> I've tried to reproduce with vanilla 4.4.143 and it doesn't fail like this, vanilla 4.4.3 doesn't
> fail, so it's caused by one of our 10000 commits on top of 4.4.3 or the config, need to dig a bit more.
Just FYI if someone needs similar fix, backporting this:
https://patchwork.kernel.org/patch/9170055/
fixed the issue for me, now I have successful kernel build.
The failing code was always in put_user calls, e.g. kernel/exit.s was showing:
@ 1581 "kernel-source/kernel/exit.c" 1
.ifnc r0,r0; .ifnc r0r0,fpr11; .ifnc r0r0,r11fp; .ifnc r0r0,ipr12; .ifnc r0r0,r12ip; .err; .endif; .endif; .endif; .endif; .endif
.ifnc r5,r2; .ifnc r5r2,fpr11; .ifnc r5r2,r11fp; .ifnc r5r2,ipr12; .ifnc r5r2,r12ip; .err; .endif; .endif; .endif; .endif; .endif
.ifnc r1,r1; .ifnc r1r1,fpr11; .ifnc r1r1,r11fp; .ifnc r1r1,ipr12; .ifnc r1r1,r12ip; .err; .endif; .endif; .endif; .endif; .endif
bl __put_user_4
@ 0 "" 2
with the error triggered on the middle line.
/tmp/ccHq8ugv.s: Assembler messages:
/tmp/ccHq8ugv.s:1179: Error: .err encountered
/tmp/ccHq8ugv.s:1331: Error: .err encountered
/tmp/ccHq8ugv.s:4617: Error: .err encountered
/tmp/ccHq8ugv.s:6222: Error: .err encountered
/tmp/ccHq8ugv.s:8705: Error: .err encountered
/tmp/ccHq8ugv.s:14486: Error: .err encountered
/tmp/ccHq8ugv.s:14646: Error: .err encountered
/tmp/ccHq8ugv.s:14806: Error: .err encountered
/tmp/ccHq8ugv.s:14966: Error: .err encountered
/tmp/ccHq8ugv.s:15126: Error: .err encountered
/tmp/ccHq8ugv.s:15286: Error: .err encountered
That leaves only few issues in our internal components and strange failure with perf which fails to include various header files:
perf/1.0-r9/perf-1.0/tools/perf/util/include/asm/byteorder.h:2:10: fatal error: ../../../../include/uapi/linux/swab.h: No such file or directory
perf/1.0-r9/perf-1.0/tools/perf/util/include/asm/byteorder.h:2:10: fatal error: ../../../../include/uapi/linux/swab.h: No such file or directory
perf/1.0-r9/perf-1.0/tools/perf/util/include/asm/byteorder.h:2:10: fatal error: ../../../../include/uapi/linux/swab.h: No such file or directory
perf/1.0-r9/perf-1.0/tools/perf/util/include/../../../include/linux/list.h:1:28: error: #include nested too deeply
perf/1.0-r9/perf-1.0/tools/perf/util/include/../../../include/linux/list.h:2:26: error: #include nested too deeply
perf/1.0-r9/perf-1.0/tools/perf/util/include/../../../include/linux/list.h:3:25: error: #include nested too deeply
perf/1.0-r9/perf-1.0/tools/perf/util/include/../../../include/linux/list.h:5:41: error: #include nested too deeply
perf/1.0-r9/perf-1.0/tools/perf/util/include/asm/byteorder.h:2:10: fatal error: ../../../../include/uapi/linux/swab.h: No such file or directory
perf/1.0-r9/perf-1.0/tools/perf/util/include/asm/byteorder.h:2:10: fatal error: ../../../../include/uapi/linux/swab.h: No such file or directory
perf/1.0-r9/perf-1.0/tools/perf/util/include/../../../include/linux/list.h:1:28: error: #include nested too deeply
perf/1.0-r9/perf-1.0/tools/perf/util/include/../../../include/linux/list.h:2:26: error: #include nested too deeply
perf/1.0-r9/perf-1.0/tools/perf/util/include/../../../include/linux/list.h:3:25: error: #include nested too deeply
perf/1.0-r9/perf-1.0/tools/perf/util/include/../../../include/linux/list.h:5:41: error: #include nested too deeply
perf/1.0-r9/perf-1.0/tools/perf/util/include/../../../include/linux/list.h:1:28: error: #include nested too deeply
perf/1.0-r9/perf-1.0/tools/perf/util/include/../../../include/linux/list.h:2:26: error: #include nested too deeply
perf/1.0-r9/perf-1.0/tools/perf/util/include/../../../include/linux/list.h:3:25: error: #include nested too deeply
perf/1.0-r9/perf-1.0/tools/perf/util/include/../../../include/linux/list.h:5:41: error: #include nested too deeply
perf/1.0-r9/perf-1.0/tools/perf/util/include/asm/byteorder.h:2:10: fatal error: ../../../../include/uapi/linux/swab.h: No such file or directory
perf/1.0-r9/perf-1.0/tools/perf/util/include/asm/byteorder.h:2:10: fatal error: ../../../../include/uapi/linux/swab.h: No such file or directory
perf/1.0-r9/perf-1.0/tools/perf/util/include/asm/byteorder.h:2:10: fatal error: ../../../../include/uapi/linux/swab.h: No such file or directory
perf/1.0-r9/perf-1.0/tools/perf/util/include/asm/byteorder.h:2:10: fatal error: ../../../../include/uapi/linux/swab.h: No such file or directory
perf/1.0-r9/perf-1.0/tools/perf/util/include/../../../include/linux/list.h:1:28: error: #include nested too deeply
perf/1.0-r9/perf-1.0/tools/perf/util/include/../../../include/linux/list.h:2:26: error: #include nested too deeply
perf/1.0-r9/perf-1.0/tools/perf/util/include/../../../include/linux/list.h:3:25: error: #include nested too deeply
perf/1.0-r9/perf-1.0/tools/perf/util/include/../../../include/linux/list.h:5:41: error: #include nested too deeply
perf/1.0-r9/perf-1.0/tools/perf/util/include/asm/byteorder.h:2:10: fatal error: ../../../../include/uapi/linux/swab.h: No such file or directory
perf/1.0-r9/perf-1.0/tools/perf/arch/arm/include/../../../../include/asm-generic/bitops/fls.h:1:56: error: #include nested too deeply
perf/1.0-r9/perf-1.0/tools/perf/arch/arm/include/../../../../include/asm-generic/bitops/fls.h:1:56: error: #include nested too deeply
...
Cheers,
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 201 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Martin Jansa <martin.jansa@gmail.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: Yocto Project <yocto@yoctoproject.org>,
openembeded-devel <Openembedded-devel@lists.openembedded.org>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [RFT] GCC 8.1
Date: Thu, 17 May 2018 12:46:40 +0200 [thread overview]
Message-ID: <20180517104640.GA1398@jama> (raw)
In-Reply-To: <20180510191145.GA1954@jama>
[-- Attachment #1: Type: text/plain, Size: 6643 bytes --]
On Thu, May 10, 2018 at 09:11:45PM +0200, Martin Jansa wrote:
> > > 5) nativesdk-libxcrypt fails to build (not sure which change caused
> > > this, it build OK with sumo since the -std=gnu99 addition.
> > > ../git/crypt-sunmd5.c:189:13: error: 'snprintf' output may be truncated
> > > before the last format character [-Werror=format-truncation=]
> > > "$" CRYPT_ALGNAME "," ROUNDS "%u$%s$",
> > > ^~~
> > >
> >
> > something new, I will look into reproducing this.
The fix from you worked for me, thanks!
> > > I didn't get very far in testing, because our old kernel fails to build
> > > with gcc8 and there are some other issues caused by other master
> > > changes. But it doesn't look too bad (in my small test, lets see what
> > > bitbake world will show), thanks a lot for new gcc.
> > >
> >
> > yes, older kernel needs fixes, especially to disable new warnings.
> > the mips/ppc fixes that I put out there might be helpful to cook up
> > fixes for older kernels if running into same issues.
>
> In this case it fails with Error: .err encountered for many drivers. It's not the same case as in:
> http://lists.infradead.org/pipermail/linux-arm-kernel/2015-February/325615.html
> nor arm version of this change, both are already applied in our
> 4.4.3 based kernel.
>
> I've tried to reproduce with vanilla 4.4.143 and it doesn't fail like this, vanilla 4.4.3 doesn't
> fail, so it's caused by one of our 10000 commits on top of 4.4.3 or the config, need to dig a bit more.
Just FYI if someone needs similar fix, backporting this:
https://patchwork.kernel.org/patch/9170055/
fixed the issue for me, now I have successful kernel build.
The failing code was always in put_user calls, e.g. kernel/exit.s was showing:
@ 1581 "kernel-source/kernel/exit.c" 1
.ifnc r0,r0; .ifnc r0r0,fpr11; .ifnc r0r0,r11fp; .ifnc r0r0,ipr12; .ifnc r0r0,r12ip; .err; .endif; .endif; .endif; .endif; .endif
.ifnc r5,r2; .ifnc r5r2,fpr11; .ifnc r5r2,r11fp; .ifnc r5r2,ipr12; .ifnc r5r2,r12ip; .err; .endif; .endif; .endif; .endif; .endif
.ifnc r1,r1; .ifnc r1r1,fpr11; .ifnc r1r1,r11fp; .ifnc r1r1,ipr12; .ifnc r1r1,r12ip; .err; .endif; .endif; .endif; .endif; .endif
bl __put_user_4
@ 0 "" 2
with the error triggered on the middle line.
/tmp/ccHq8ugv.s: Assembler messages:
/tmp/ccHq8ugv.s:1179: Error: .err encountered
/tmp/ccHq8ugv.s:1331: Error: .err encountered
/tmp/ccHq8ugv.s:4617: Error: .err encountered
/tmp/ccHq8ugv.s:6222: Error: .err encountered
/tmp/ccHq8ugv.s:8705: Error: .err encountered
/tmp/ccHq8ugv.s:14486: Error: .err encountered
/tmp/ccHq8ugv.s:14646: Error: .err encountered
/tmp/ccHq8ugv.s:14806: Error: .err encountered
/tmp/ccHq8ugv.s:14966: Error: .err encountered
/tmp/ccHq8ugv.s:15126: Error: .err encountered
/tmp/ccHq8ugv.s:15286: Error: .err encountered
That leaves only few issues in our internal components and strange failure with perf which fails to include various header files:
perf/1.0-r9/perf-1.0/tools/perf/util/include/asm/byteorder.h:2:10: fatal error: ../../../../include/uapi/linux/swab.h: No such file or directory
perf/1.0-r9/perf-1.0/tools/perf/util/include/asm/byteorder.h:2:10: fatal error: ../../../../include/uapi/linux/swab.h: No such file or directory
perf/1.0-r9/perf-1.0/tools/perf/util/include/asm/byteorder.h:2:10: fatal error: ../../../../include/uapi/linux/swab.h: No such file or directory
perf/1.0-r9/perf-1.0/tools/perf/util/include/../../../include/linux/list.h:1:28: error: #include nested too deeply
perf/1.0-r9/perf-1.0/tools/perf/util/include/../../../include/linux/list.h:2:26: error: #include nested too deeply
perf/1.0-r9/perf-1.0/tools/perf/util/include/../../../include/linux/list.h:3:25: error: #include nested too deeply
perf/1.0-r9/perf-1.0/tools/perf/util/include/../../../include/linux/list.h:5:41: error: #include nested too deeply
perf/1.0-r9/perf-1.0/tools/perf/util/include/asm/byteorder.h:2:10: fatal error: ../../../../include/uapi/linux/swab.h: No such file or directory
perf/1.0-r9/perf-1.0/tools/perf/util/include/asm/byteorder.h:2:10: fatal error: ../../../../include/uapi/linux/swab.h: No such file or directory
perf/1.0-r9/perf-1.0/tools/perf/util/include/../../../include/linux/list.h:1:28: error: #include nested too deeply
perf/1.0-r9/perf-1.0/tools/perf/util/include/../../../include/linux/list.h:2:26: error: #include nested too deeply
perf/1.0-r9/perf-1.0/tools/perf/util/include/../../../include/linux/list.h:3:25: error: #include nested too deeply
perf/1.0-r9/perf-1.0/tools/perf/util/include/../../../include/linux/list.h:5:41: error: #include nested too deeply
perf/1.0-r9/perf-1.0/tools/perf/util/include/../../../include/linux/list.h:1:28: error: #include nested too deeply
perf/1.0-r9/perf-1.0/tools/perf/util/include/../../../include/linux/list.h:2:26: error: #include nested too deeply
perf/1.0-r9/perf-1.0/tools/perf/util/include/../../../include/linux/list.h:3:25: error: #include nested too deeply
perf/1.0-r9/perf-1.0/tools/perf/util/include/../../../include/linux/list.h:5:41: error: #include nested too deeply
perf/1.0-r9/perf-1.0/tools/perf/util/include/asm/byteorder.h:2:10: fatal error: ../../../../include/uapi/linux/swab.h: No such file or directory
perf/1.0-r9/perf-1.0/tools/perf/util/include/asm/byteorder.h:2:10: fatal error: ../../../../include/uapi/linux/swab.h: No such file or directory
perf/1.0-r9/perf-1.0/tools/perf/util/include/asm/byteorder.h:2:10: fatal error: ../../../../include/uapi/linux/swab.h: No such file or directory
perf/1.0-r9/perf-1.0/tools/perf/util/include/asm/byteorder.h:2:10: fatal error: ../../../../include/uapi/linux/swab.h: No such file or directory
perf/1.0-r9/perf-1.0/tools/perf/util/include/../../../include/linux/list.h:1:28: error: #include nested too deeply
perf/1.0-r9/perf-1.0/tools/perf/util/include/../../../include/linux/list.h:2:26: error: #include nested too deeply
perf/1.0-r9/perf-1.0/tools/perf/util/include/../../../include/linux/list.h:3:25: error: #include nested too deeply
perf/1.0-r9/perf-1.0/tools/perf/util/include/../../../include/linux/list.h:5:41: error: #include nested too deeply
perf/1.0-r9/perf-1.0/tools/perf/util/include/asm/byteorder.h:2:10: fatal error: ../../../../include/uapi/linux/swab.h: No such file or directory
perf/1.0-r9/perf-1.0/tools/perf/arch/arm/include/../../../../include/asm-generic/bitops/fls.h:1:56: error: #include nested too deeply
perf/1.0-r9/perf-1.0/tools/perf/arch/arm/include/../../../../include/asm-generic/bitops/fls.h:1:56: error: #include nested too deeply
...
Cheers,
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 201 bytes --]
next prev parent reply other threads:[~2018-05-17 10:46 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-05 0:26 [RFT] GCC 8.1 Khem Raj
2018-05-05 7:31 ` Zoran Stojsavljevic
2018-05-10 19:21 ` [yocto] " Khem Raj
2018-05-10 19:21 ` Khem Raj
2018-05-09 9:38 ` [OE-core] " Martin Jansa
2018-05-09 9:38 ` Martin Jansa
2018-05-09 9:38 ` Martin Jansa
2018-05-10 12:20 ` [PATCH] busybox: Enable FEATURE_MOUNT_NFS and use libtirpc Martin Jansa
2018-05-10 13:01 ` Burton, Ross
2018-05-10 18:21 ` Khem Raj
2018-05-10 18:24 ` Khem Raj
2018-05-10 19:16 ` Martin Jansa
2018-05-10 19:26 ` Khem Raj
2018-05-30 17:39 ` Andre McCurdy
2018-06-10 11:05 ` Martin Jansa
2018-05-10 18:50 ` [OE-core] [RFT] GCC 8.1 Khem Raj
2018-05-10 18:50 ` Khem Raj
2018-05-10 19:11 ` [OE-core] " Martin Jansa
2018-05-10 19:11 ` Martin Jansa
2018-05-10 19:27 ` [OE-core] " Andre McCurdy
2018-05-10 19:27 ` Andre McCurdy
2018-05-10 21:43 ` [OE-core] " Martin Jansa
2018-05-10 21:43 ` Martin Jansa
2018-05-10 22:07 ` [OE-core] " Martin Jansa
2018-05-10 22:07 ` Martin Jansa
2018-05-10 22:35 ` [OE-core] " Khem Raj
2018-05-10 22:35 ` Khem Raj
2018-05-10 22:38 ` [OE-core] " Andre McCurdy
2018-05-10 22:38 ` Andre McCurdy
2018-05-10 22:38 ` [OE-core] " Martin Jansa
2018-05-10 22:38 ` Martin Jansa
2018-05-10 22:38 ` Martin Jansa
2018-05-10 22:40 ` [OE-core] " Andre McCurdy
2018-05-10 22:40 ` Andre McCurdy
2018-05-10 22:50 ` [OE-core] " Martin Jansa
2018-05-10 22:50 ` Martin Jansa
2018-05-10 23:11 ` [OE-core] " Andre McCurdy
2018-05-10 23:11 ` Andre McCurdy
2018-05-10 23:32 ` [OE-core] " Martin Jansa
2018-05-10 23:32 ` Martin Jansa
2018-05-10 23:41 ` [OE-core] " Andre McCurdy
2018-05-10 23:41 ` Andre McCurdy
2018-05-11 0:55 ` [OE-core] " Khem Raj
2018-05-11 0:55 ` Khem Raj
2018-05-11 1:00 ` [OE-core] " Andre McCurdy
2018-05-11 1:00 ` Andre McCurdy
2018-05-11 1:06 ` [OE-core] " Khem Raj
2018-05-11 1:06 ` Khem Raj
2018-05-11 1:11 ` [OE-core] " Andre McCurdy
2018-05-11 1:11 ` Andre McCurdy
2018-05-11 1:16 ` [OE-core] " Khem Raj
2018-05-11 1:16 ` Khem Raj
2018-05-11 1:21 ` [OE-core] " Andre McCurdy
2018-05-11 1:21 ` Andre McCurdy
2018-05-17 10:46 ` Martin Jansa [this message]
2018-05-17 10:46 ` Martin Jansa
2018-05-18 5:54 ` [OE-core] " Khem Raj
2018-05-18 5:54 ` Khem Raj
2018-05-24 15:08 ` [OE-core] " Martin Jansa
2018-05-24 15:08 ` Martin Jansa
2018-05-10 14:34 ` [OE-core] " Dan McGregor
2018-05-10 14:34 ` Dan McGregor
2018-05-10 18:53 ` [OE-core] " Khem Raj
2018-05-10 18:53 ` Khem Raj
2018-05-14 16:33 ` [OE-core] " Dan McGregor
2018-05-14 16:33 ` Dan McGregor
2018-05-14 17:09 ` [OE-core] " Martin Jansa
2018-05-14 17:09 ` Martin Jansa
2018-05-11 22:05 ` [OE-core] " Burton, Ross
2018-05-11 22:05 ` Burton, Ross
2018-05-12 6:10 ` [OE-core] " Khem Raj
2018-05-12 6:10 ` Khem Raj
2018-05-13 23:35 ` [OE-core] " Khem Raj
2018-05-13 23:35 ` Khem Raj
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=20180517104640.GA1398@jama \
--to=martin.jansa@gmail.com \
--cc=Openembedded-devel@lists.openembedded.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
--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.