For anyone having some similar issue with the linux-msm please notice https://source.codeaurora.org/quic/le/meta-qti-bsp/tree/recipes-kernel/linux-msm/linux-msm.inc?id=cbe4d954a9a37dd15e78e3dfdc823ffc6776d746
do_kernel_checkout[noexec] = "1" This will result in issues if you don't already have a .git directory in the kernel source code. To unset this add unset do_kernel_checkout[noexec] to your bbappend file. /Mans Den ons 29 jan. 2020 kl 08:27 skrev Måns Zigher <[email protected]>: > > Hi again, > > Looks like the kernel source code was not clean so I made sure it was > and created a new tar file and now it is building. I will try using > the tar file and if it works I will start moving to our own git repo. > > Thanks > > Den ons 29 jan. 2020 kl 08:05 skrev Måns Zigher <[email protected]>: > > > > Hi, > > > > Thanks for your help. You are probably right regarding the subject. > > The build system that we are using have a complex setup where we are > > downloading a large tar file and then running android repo tool when > > we have all the source code we need to merge these two together. To > > prevent downloading all of this from external source we naively > > decided to put all of this up in our local gerrit server. So the use > > of ${WORKSPACE} is used by by not just the kernel. For the long term > > we will likely have to rethink this but my goal was for the short term > > to try and set something up that we can use for the kernel. To test it > > it out would it make sense to try and use a local tar file containing > > the kernel source code? I am currently facing some issues when using a > > tar file or the externalsrc for that mater. I just don't want to setup > > the git repo and waist time on that if I can do quicker workaround for > > now but based on what I can see in kernel-yocto.bbclass and the > > documentation you pointing me to it looks like git is expected? > > > > ERROR: linux-msm-4.14-r0 do_compile: oe_runmake failed > > ERROR: linux-msm-4.14-r0 do_compile: Function failed: do_compile (log > > file is located at > > /home/ext/workspace/builds/board-debug/tmp-glibc/work/vt_64-oe-linux/linux-msm/4.14-r0/temp/log.do_compile.13840) > > ERROR: Logfile of failure stored in: > > /home/ext/workspace/builds/board-debug/tmp-glibc/work/vt_64-oe-linux/linux-msm/4.14-r0/temp/log.do_compile.13840 > > Log data follows: > > | DEBUG: Executing shell function do_compile > > | NOTE: make -j 8 RTIC_MPGEN=python > > /home/ext/workspace/gn/apps_proc/vendor/qcom/proprietary/qrsp/mpgen/mpgen.py > > INSTALL_MOD_STRIP=1 > > CC=/home/ext/workspace/builds/board-debug/tmp-glibc/work/vt_64-oe-linux/linux-msm/4.14-r0/recipe-sysroot-native/usr/bin/llvm-arm-toolchain/bin/clang > > -target aarch64-oe-linux -D__extern_always_inline=inline > > -no-integrated-as -Wno-error=unused-command-line-argument > > -Qunused-arguments -fstack-protector-strong -pie -fPIE > > -D_FORTIFY_SOURCE=2 -Wa,--noexecstack -Wformat -Wformat-security > > -Werror=format-security > > --sysroot=/home/ext/workspace/builds/board-debug/tmp-glibc/work/vt_64-oe-linux/linux-msm/4.14-r0/recipe-sysroot > > -fuse-ld=bfd > > --sysroot=/home/ext/workspace/builds/board-debug/tmp-glibc/work/vt_64-oe-linux/linux-msm/4.14-r0/recipe-sysroot > > LD=aarch64-oe-linux-ld.bfd > > --sysroot=/home/ext/workspace/builds/board-debug/tmp-glibc/work/vt_64-oe-linux/linux-msm/4.14-r0/recipe-sysroot > > O=/home/ext/workspace/builds/board-debug/tmp-glibc/work/vt_64-oe-linux/linux-msm/4.14-r0/build > > | CHK include/config/kernel.release > > | Error: kernelrelease not valid - run 'make prepare' to update it > > | UPD include/config/kernel.release > > | GEN ./Makefile > > | CHK include/generated/uapi/linux/version.h > > | UPD include/generated/uapi/linux/version.h > > | CHK include/generated/utsrelease.h > > | UPD include/generated/utsrelease.h > > | GEN ./Makefile > > | scripts/kconfig/conf --silentoldconfig Kconfig > > | Using > > /home/ext/workspace/builds/board-debug/tmp-glibc/work-shared/vt-64/kernel-source > > as source for kernel > > | > > /home/ext/workspace/builds/board-debug/tmp-glibc/work-shared/vt-64/kernel-source > > is not clean, please run 'make mrproper' > > | in the > > '/home/ext/workspace/builds/board-debug/tmp-glibc/work-shared/vt-64/kernel-source' > > directory. > > | > > /home/ext/workspace/builds/board-debug/tmp-glibc/work-shared/vt-64/kernel-source/Makefile:1149: > > recipe for target 'prepare3' failed > > | make[2]: *** [prepare3] Error 1 > > | Makefile:146: recipe for target 'sub-make' failed > > | make[1]: *** [sub-make] Error 2 > > | Makefile:24: recipe for target '__sub-make' failed > > | make: *** [__sub-make] Error 2 > > | ERROR: oe_runmake failed > > | WARNING: > > /home/ext/workspace/builds/board-debug/tmp-glibc/work/vt_64-oe-linux/linux-msm/4.14-r0/temp/run.do_compile.13840:1 > > exit 1 from 'exit 1' > > | ERROR: Function failed: do_compile (log file is located at > > /home/ext/workspace/builds/board-debug/tmp-glibc/work/vt_64-oe-linux/linux-msm/4.14-r0/temp/log.do_compile.13840) > > ERROR: Task > > (/home/ext/workspace/layers/meta-qti/meta-qti-bsp/recipes-kernel/linux-msm/linux-msm_4.14.bb:do_compile) > > failed with exit code '1' > > NOTE: Tasks Summary: Attempted 400 tasks of which 390 didn't need to > > be rerun and 1 failed. > > NOTE: Writing buildhistory > > > > Summary: 1 task failed: > > > > /home/ext/workspace/layers/meta-qti/meta-qti-bsp/recipes-kernel/linux-msm/linux-msm_4.14.bb:do_compile > > Summary: There were 16 WARNING messages shown. > > Summary: There were 2 ERROR messages shown, returning a non-zero exit code. > > > > Here is my current bbappend file > > > > 1 FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:" > > 2 > > 3 SRC_URI += "file://msm-${PV}.tar.gz;subdir=${WORKDIR}/${PN}" > > 4 > > 5 S = "${WORKDIR}/${PN}/msm-${PV}" > > > > The error "Error: kernelrelease not valid - run 'make prepare' to > > update it" is coming from scripts/setlocalversion in the kernel source > > > > if test -e include/config/auto.conf; then > > . include/config/auto.conf > > else > > echo "Error: kernelrelease not valid - run 'make prepare' to > > update it" >&2 > > exit 1 > > fi > > > > But when running bitbake -c devshell virtual/kernel and checking the > > source code the file is there. > > > > Thanks > > > > Den tis 28 jan. 2020 kl 15:37 skrev Mark Asselstine > > <[email protected]>: > > > > > > On Tuesday, January 28, 2020 7:37:28 A.M. EST Mans Zigher wrote: > > > > Hi, > > > > > > > > We have a build where the kernel is based on > > > > https://source.codeaurora.org/quic/le/meta-qti-bsp/tree/recipes-kernel/linux > > > > -msm/linux-msm_4.14.bb?id=cbe4d954a9a37dd15e78e3dfdc823ffc6776d746 > > > > > > > > We are facing some issues with this recipe because I don't think it is > > > > correctly setup. For > > > > example they are not using the externalsrc.bbclass even though the > > > > source code is an external src. The location for the source code is > > > > just defined by > > > > > > > > SRC_DIR = "${WORKSPACE}/kernel/msm-4.14" > > > > > > > > The WORKSPACE is then defined in the bblayers.conf file. The problem > > > > is that there are a lot of source code located in the WORKSPACE > > > > directory so we decided to put all of that in it's own repo and check > > > > it out before building. Because of that we had to remove the > > > > individual .git directories in the repos that included the .git under > > > > ${WORKSPACE}/kernel/msm-4.14. Any suggestions? Is it possible to build > > > > the kernel as an externalsrc even when it is missing the .git? And can > > > > we still apply patches when having it as an externalsrc? Or should we > > > > just change it so we are using a local tar file? > > > > > > I would be hesitant to just going along with the implied use of > > > ${WORKSPACE} > > > for the location of things such as the kernel source. > > > > > > ie. this bit from the linux-msm.inc file > > > --- > > > FILESPATH =+ "${WORKSPACE}:" > > > SRC_URI = "file://kernel \ > > > --- > > > > > > You most likely already have a custom layer created where you have other > > > customizations in the form of bbappends. If not I would set one up (use > > > bitbake-layers create-layer and bitbake-layers add-layer). I would then > > > create > > > a linux-msm_%.bbappend and use this to make things more manageable by > > > removing > > > the need to host things like the kernel source in ${WORKSPACE}. ie. in the > > > bbappend have 'FILESEXTRAPATHS_prepend := "${THISDIR}/files:"' and > > > 'SRC_URI > > > += "git://your.git.server/path/to/the/kernel"'. This way you can avoid > > > having > > > to check your kernel git repo into another repo. > > > > > > Note that the SRC_URI crime they have in linux-msm.inc will require you to > > > provide a file name 'kernel' still, you can do this by putting an empty > > > file > > > or a file with a line like 'satisfy SRC_URI' called kernel in your layer. > > > So > > > you will end up with > > > > > > <your-custom-layer>/recipes-kernel/linux-msm/linux-msm_%.bbappend > > > <your-custom-layer>/recipes-kernel/linux-msm/files/kernel > > > > > > If you need more inspiration review the kernel dev document > > > https://www.yoctoproject.org/docs/1.6/kernel-dev/kernel-dev.html#working-with-your-own-sources > > > > > > Overall I don't think the question here should be, how do you work with > > > kernels that don't have a .git. But rather how can you better configure > > > things > > > with a bbappend in a custom layer to allow you to work better than what is > > > being proposed in the meta-qti-bsp layer. > > > > > > Good luck, > > > Mark Asselstine > > > > > > > > > > > Thanks > > > > > > > > BR > > > > Mans Zigher > > > > > > > > > > > >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#48193): https://lists.yoctoproject.org/g/yocto/message/48193 Mute This Topic: https://lists.yoctoproject.org/mt/70216839/21656 Group Owner: [email protected] Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
