From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 6FD98E01145; Fri, 11 May 2018 23:10:45 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1 X-Spam-HAM-Report: * 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider * (raj.khem[at]gmail.com) * -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no * trust * [209.85.192.196 listed in list.dnswl.org] * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's * domain * 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily * valid * -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature Received: from mail-pf0-f196.google.com (mail-pf0-f196.google.com [209.85.192.196]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 58DBCE00EBE for ; Fri, 11 May 2018 23:10:43 -0700 (PDT) Received: by mail-pf0-f196.google.com with SMTP id j20-v6so3657466pff.10 for ; Fri, 11 May 2018 23:10:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=wkOvjJsXvUru0y3NURklI+CUij60gAYevyKik3A1nZw=; b=FKVKEiYyu/1ug9a3UKdySJPgJ3iRrSTy+N8b+qQuJ8Z+VRBig1bt4Nhmk1Mij0WZkL IO3Lo6mgq5F7hYw4zzM+3thUtTf6ZATXo7M9Jbgs8E+NnlBLjammHQOSmReXEhAAK5lb 7Ke8zQWctigYTua6M7TkV4stT85GnDj8To9r/WJCI5nJrkQYnOkdIUfqoZTSp+T7RwX4 Gt9TtnXfzdAHk6WOu7zCm+CefkN64rQUj2CJh4opQPkPP8p+cdc+bWb2/X7+HQQNGew5 J1GPrNDYbjkFLpgt+DbWulDuA0rwXBUaSq0rMUl7ZmZTSXHE1clAVFH7UNVDEwW6bUOV 2B6Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=wkOvjJsXvUru0y3NURklI+CUij60gAYevyKik3A1nZw=; b=VFNrYK0XJp93QLLBus/Eq8hVvRSK3k2ViQAmt/KSz1f3x9Ie+u5wNRU+08zPs7Vlcu EcKnc4UwL+rxFeOuOaS7qxKnt5DJyslNznjo13+Lhf7ucOkIfKklMNtKFRH8CC3jTw8C 9xTY2cmizMa0iNpKdgj8cH5Uu8EqbmpORCkdjtJlPSWFYc8AEzmFP3irOqnj8ZlT8eWH n0mv5YbE/NWH1uegkgatJNG46H2/qbKJ+CsXXtz8bZeBLyY3HLe740TaWemk2SQev7yT AGYKjkjY3eWvPAWy1amKlggSG+HWdPxzdmZdQePDYtEdSuDjZPnjlSBjNIczwDxeLs06 dPkA== X-Gm-Message-State: ALKqPwfssSLjxU35m9C5kUbq6oxX4cI28xbPAYKvsbc7WVnAmXCmR1zs rMKgSXt4tODQuglxYgdZtwY6B1XPV5LR0LtiuI0= X-Google-Smtp-Source: AB8JxZosAKcmjYqw8Dlz2KumPk1vSp895bvrHqzORvuIo+f4tyBRF8gbC3bJVfjeqkAGGxor0J7NnZlboq+NDlAU7B4= X-Received: by 2002:a62:828c:: with SMTP id w134-v6mr1861816pfd.138.1526105443079; Fri, 11 May 2018 23:10:43 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a17:90a:8b91:0:0:0:0 with HTTP; Fri, 11 May 2018 23:10:12 -0700 (PDT) In-Reply-To: References: From: Khem Raj Date: Fri, 11 May 2018 23:10:12 -0700 Message-ID: To: "Burton, Ross" Cc: Yocto Project , openembeded-devel , Patches and discussions about the oe-core layer Subject: Re: [OE-core] [RFT] GCC 8.1 X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto Project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 May 2018 06:10:45 -0000 Content-Type: text/plain; charset="UTF-8" Hi Ross Thanks for testing I looked at failures and one of them is RESULTS - kernelmodule.KernelModuleTest.test_kernel_module - Testcase 1541: FAILED and this is the compile error. pager.c: In function 'pager_preexec': pager.c:36:12: error: passing argument 2 to restrict-qualified parameter aliases with argument 4 [-Werror=restrict] select(1, &in, NULL, &in, NULL); ^~~ ~~~ cc1: all warnings being treated as errors mv: cannot stat '/usr/src/kernel/tools/objtool/.pager.o.tmp': No such file or directory Firstly I must say that I am impressed with autotest, We are building on-device toolchain and then downloading a kernel and building it to test i.. bravo Problem here is that poky pins linux-yocto to 4.14, with gcc8 we need to use 4.15.x eventually 4.14 will get fixed but until then use 4.15, the test subject component that is being compiled is not ported to gcc-8, not sure how we can improve it. Is it compiling linux-yocto kmods ? or external kmod ? We need to patch the test before building, I think the mesa error is new with mesa-18 I havent seen this on my end. Its showing up when we enable llvmpipe which is not general default so it might not happen in general. selftest is failing like this | Copying files into the device: __populate_fs: Could not allocate block in ext2 filesystem while writing file "ldconfig" | mkfs.ext4: Could not allocate block in ext2 filesystem while populating file system | WARNING: /tmp/eSDKQAfqaczn6s/tmp/work/qemux86_64-poky-linux/core-image-minimal/1.0-r0/temp/run.do_image_ext4.15615:1 exit 1 from 'mkfs.$fstype -F $extra_imagecmd /tmp/eSDKQAfqaczn6s/tmp/work/qemux86_64-poky-linux/core-image-minimal/1.0-r0/deploy-core-image-minimal-image-complete/core-image-minimal-qemux86-64-20180511212710.rootfs.$fstype -d /tmp/eSDKQAfqaczn6s/tmp/work/qemux86_64-poky-linux/core-image-minimal/1.0-r0/rootfs' not sure if I understand it fully but it sems system ran out of disk space. On Fri, May 11, 2018 at 3:05 PM, Burton, Ross wrote: > I threw the branch at the Yocto Project autobuilder today, produced a > number of failures: > > http://errors.yoctoproject.org/Errors/Latest//?filter=b23dba19607412c8cc7d267d95354d65f5631088&type=commit > > Ross > > On 5 May 2018 at 01:26, Khem Raj wrote: >> Hi All >> >> As you might have noticed that gcc 8.1 was released this week, I am >> calling out for some testing help on testing branch so we can weed out >> issues you might see in your setups. so if you have your >> builders idling over weekend, then you know what they can do this weekend :) >> >> Highlighted changes are >> >> https://gcc.gnu.org/gcc-8/changes.html >> >> and porting doc is >> >> https://gcc.gnu.org/gcc-8/porting_to.html >> >> The branch is here >> >> http://git.openembedded.org/openembedded-core-contrib/log/?h=kraj/gcc-8 >> >> Its uptodate on top of current master oe-core >> >> May fourth be with you !! >> >> Cheers! >> >> -Khem >> -- >> _______________________________________________ >> Openembedded-core mailing list >> Openembedded-core@lists.openembedded.org >> http://lists.openembedded.org/mailman/listinfo/openembedded-core From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pf0-f193.google.com (mail-pf0-f193.google.com [209.85.192.193]) by mail.openembedded.org (Postfix) with ESMTP id CBCE87890E; Sat, 12 May 2018 06:10:42 +0000 (UTC) Received: by mail-pf0-f193.google.com with SMTP id p12-v6so3655751pff.13; Fri, 11 May 2018 23:10:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=wkOvjJsXvUru0y3NURklI+CUij60gAYevyKik3A1nZw=; b=FKVKEiYyu/1ug9a3UKdySJPgJ3iRrSTy+N8b+qQuJ8Z+VRBig1bt4Nhmk1Mij0WZkL IO3Lo6mgq5F7hYw4zzM+3thUtTf6ZATXo7M9Jbgs8E+NnlBLjammHQOSmReXEhAAK5lb 7Ke8zQWctigYTua6M7TkV4stT85GnDj8To9r/WJCI5nJrkQYnOkdIUfqoZTSp+T7RwX4 Gt9TtnXfzdAHk6WOu7zCm+CefkN64rQUj2CJh4opQPkPP8p+cdc+bWb2/X7+HQQNGew5 J1GPrNDYbjkFLpgt+DbWulDuA0rwXBUaSq0rMUl7ZmZTSXHE1clAVFH7UNVDEwW6bUOV 2B6Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=wkOvjJsXvUru0y3NURklI+CUij60gAYevyKik3A1nZw=; b=n1MZ6XcX4RhHPs1QmaiF6g9e8yojcVr5clj0MmMJqNsHbS3gc+v/P2DF0a4fwXZB7R DnWPhpqJBpaHlCzBwueMNvKGvMSuZgOWfDcRVWe09BFjJkLSFj0XPBc7pXETeDKxle3R zrWDqHW3cL6WZw84hBudaHJqJcgKBdw1rKb1c4jMl2sf35sphsMPZFMJbrofRbzbIZf+ MSUJ/DDvoNjZkihBqoFGimW11L7Smo+O8i2ypfvzfHiQp7JR6W+alcB2/lI8f9Kgw7vC uSGRd0APqjdbFexLigS6tXVGT6zmDyZ1jwPVh4r6LvUpdX/2md8SL355rPsXqWC7cJOi FKyQ== X-Gm-Message-State: ALKqPwezpPQEz+dNbzUgVF1ZTyP1gx5SOZu2S7k6j0zu/PXCiDttuD5D zPVs3fIjW9JarlDJ6BIAo6DsMxHD6zqfyjVQUKA= X-Google-Smtp-Source: AB8JxZosAKcmjYqw8Dlz2KumPk1vSp895bvrHqzORvuIo+f4tyBRF8gbC3bJVfjeqkAGGxor0J7NnZlboq+NDlAU7B4= X-Received: by 2002:a62:828c:: with SMTP id w134-v6mr1861816pfd.138.1526105443079; Fri, 11 May 2018 23:10:43 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a17:90a:8b91:0:0:0:0 with HTTP; Fri, 11 May 2018 23:10:12 -0700 (PDT) In-Reply-To: References: From: Khem Raj Date: Fri, 11 May 2018 23:10:12 -0700 Message-ID: To: "Burton, Ross" Cc: Yocto Project , openembeded-devel , Patches and discussions about the oe-core layer Subject: Re: [RFT] GCC 8.1 X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 May 2018 06:10:43 -0000 Content-Type: text/plain; charset="UTF-8" Hi Ross Thanks for testing I looked at failures and one of them is RESULTS - kernelmodule.KernelModuleTest.test_kernel_module - Testcase 1541: FAILED and this is the compile error. pager.c: In function 'pager_preexec': pager.c:36:12: error: passing argument 2 to restrict-qualified parameter aliases with argument 4 [-Werror=restrict] select(1, &in, NULL, &in, NULL); ^~~ ~~~ cc1: all warnings being treated as errors mv: cannot stat '/usr/src/kernel/tools/objtool/.pager.o.tmp': No such file or directory Firstly I must say that I am impressed with autotest, We are building on-device toolchain and then downloading a kernel and building it to test i.. bravo Problem here is that poky pins linux-yocto to 4.14, with gcc8 we need to use 4.15.x eventually 4.14 will get fixed but until then use 4.15, the test subject component that is being compiled is not ported to gcc-8, not sure how we can improve it. Is it compiling linux-yocto kmods ? or external kmod ? We need to patch the test before building, I think the mesa error is new with mesa-18 I havent seen this on my end. Its showing up when we enable llvmpipe which is not general default so it might not happen in general. selftest is failing like this | Copying files into the device: __populate_fs: Could not allocate block in ext2 filesystem while writing file "ldconfig" | mkfs.ext4: Could not allocate block in ext2 filesystem while populating file system | WARNING: /tmp/eSDKQAfqaczn6s/tmp/work/qemux86_64-poky-linux/core-image-minimal/1.0-r0/temp/run.do_image_ext4.15615:1 exit 1 from 'mkfs.$fstype -F $extra_imagecmd /tmp/eSDKQAfqaczn6s/tmp/work/qemux86_64-poky-linux/core-image-minimal/1.0-r0/deploy-core-image-minimal-image-complete/core-image-minimal-qemux86-64-20180511212710.rootfs.$fstype -d /tmp/eSDKQAfqaczn6s/tmp/work/qemux86_64-poky-linux/core-image-minimal/1.0-r0/rootfs' not sure if I understand it fully but it sems system ran out of disk space. On Fri, May 11, 2018 at 3:05 PM, Burton, Ross wrote: > I threw the branch at the Yocto Project autobuilder today, produced a > number of failures: > > http://errors.yoctoproject.org/Errors/Latest//?filter=b23dba19607412c8cc7d267d95354d65f5631088&type=commit > > Ross > > On 5 May 2018 at 01:26, Khem Raj wrote: >> Hi All >> >> As you might have noticed that gcc 8.1 was released this week, I am >> calling out for some testing help on testing branch so we can weed out >> issues you might see in your setups. so if you have your >> builders idling over weekend, then you know what they can do this weekend :) >> >> Highlighted changes are >> >> https://gcc.gnu.org/gcc-8/changes.html >> >> and porting doc is >> >> https://gcc.gnu.org/gcc-8/porting_to.html >> >> The branch is here >> >> http://git.openembedded.org/openembedded-core-contrib/log/?h=kraj/gcc-8 >> >> Its uptodate on top of current master oe-core >> >> May fourth be with you !! >> >> Cheers! >> >> -Khem >> -- >> _______________________________________________ >> Openembedded-core mailing list >> Openembedded-core@lists.openembedded.org >> http://lists.openembedded.org/mailman/listinfo/openembedded-core