On 2018-03-01 9:22 AM, Burton, Ross wrote:
Swore I picked the v2 patch for the second run, I've fired a mini test build to see.

The other failures reported were valid and not addressed by v2. So only
32 bit ARM would have been fixed (packaging wise), the rest were ok.

I build and deployed kernel-devsrc for ARM multiple times, so if it does
actually fail again .. I'm *very* interested to hear.

Bruce


Ross

On 1 March 2018 at 13:59, Bruce Ashfield <bruce.ashfi...@windriver.com <mailto:bruce.ashfi...@windriver.com>> wrote:

    On 2018-03-01 5:58 AM, Maxin B. John wrote:


            Also fails on musl:

            ERROR: Nothing RPROVIDES 'glibc-utils' (but
            
/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-musl/build/meta/recipes-kernel/linux/kernel-devsrc.bb
            <http://kernel-devsrc.bb> RDEPENDS on or otherwise requires it)

            Ross

            On 1 March 2018 at 08:28, Maxin B. John
            <maxin.j...@intel.com <mailto:maxin.j...@intel.com>> wrote:


           >On Wed, Feb 28, 2018 at 02:20:45PM -0500, Bruce Ashfield wrote:
           >> The existing kernel-devsrc package starts with a full copy
        of the kernel
           >> source and then starts to strip out elements that are not
        required.
           >>
           >> This results in extra time (I/O) and extra space being
        taken up in the
           >> final package. The main purpose of the kernel-devsrc
        package has been to
           >> build modules against the running kernel, not to include a
        full copy of
           >> the source code for re-building the kernel. The end result
        was a
           >> 600M kernel-devsrc package.

           Other failures are listed below:
             arm64:
        
https://autobuilder.yocto.io/builders/nightly-arm64/builds/790/steps/Running%20Sanity%20Tests/logs/stdio
        
<https://autobuilder.yocto.io/builders/nightly-arm64/builds/790/steps/Running%20Sanity%20Tests/logs/stdio>

           RESULTS - kernelmodule.KernelModuleTest.test_kernel_module -
        Testcase 1541: FAILED

        HOSTCC  scripts/sortextable
           scripts/sortextable.c:31:10: fatal error:
        tools/be_byteshift.h: No such file or directory
        #include <tools/be_byteshift.h>
            ^~~~~~~~~~~~~~~~~~~~~~
        compilation terminated.
        make[1]: *** [scripts/Makefile.host:102: scripts/sortextable]
        Error 1
        make: *** [Makefile:557: scripts] Error 2
        ----------------------------------------------------------------------

        Similar on qemuarm - poky-lsb :

        
https://autobuilder.yocto.io/builders/nightly-arm-lsb/builds/812/steps/Running%20Sanity%20Tests/logs/stdio
        
<https://autobuilder.yocto.io/builders/nightly-arm-lsb/builds/812/steps/Running%20Sanity%20Tests/logs/stdio>

        HOSTCC  scripts/recordmcount
        HOSTCC  scripts/sortextable
        scripts/sortextable.c:31:10: fatal error: tools/be_byteshift.h:
        No such file or directory
              #include <tools/be_byteshift.h>
                        ^~~~~~~~~~~~~~~~~~~~~~
                        compilation terminated.
                        make[1]: *** [scripts/Makefile.host:102:
        scripts/sortextable] Error 1
                        make: *** [Makefile:557: scripts] Error 2
        
-------------------------------------------------------------------------

        Also on PowerPC:

        
https://autobuilder.yocto.io/builders/nightly-ppc-lsb/builds/814/steps/Running%20Sanity%20Tests/logs/stdio
        
<https://autobuilder.yocto.io/builders/nightly-ppc-lsb/builds/814/steps/Running%20Sanity%20Tests/logs/stdio>

        scripts/sortextable.c:31:10: fatal error: tools/be_byteshift.h:
        No such file or directory
           #include <tools/be_byteshift.h>
                     ^~~~~~~~~~~~~~~~~~~~~~
        compilation terminated.
        make[1]: *** [scripts/Makefile.host:102: scripts/sortextable]
        Error 1
        make: *** [Makefile:557: scripts] Error 2


    I have all these fixed now.

    Will have a look at musl next.

    Cheers,

    Bruce


        Best Regards,
        Maxin




--
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Reply via email to