From: Christian Ege <k4230r6@gmail.com>
To: Yocto list discussion <yocto@yoctoproject.org>,
"meta-freescale@yoctoproject.org"
<meta-freescale@yoctoproject.org>
Subject: Re: Kernel build gets stuck in a endless loop
Date: Wed, 27 Jan 2016 20:40:31 +0100 [thread overview]
Message-ID: <56A91D2F.6080800@gmail.com> (raw)
In-Reply-To: <CAJTF2nT-hOXiuUa8ta=cPVXPejg2ck=AzA+3xJNuszVkuBu+CQ@mail.gmail.com>
Hi,
Thanks to Guiseppe Pagano, there is a solution for this issue. It is
more a hot fix than a real solution but this is maybe for someone else
helpful.
> Hi Crhistian,
> It is not a clean patch, but it works for me.
>
> File: kernel_imx_3.14/Makefile
>
> - $(Q)$(MAKE) -f $(srctree)/Makefile silentoldconfig
> + if [[ ! -e include/config/auto.conf ]]; then $(MAKE) -f
> $(srctree)/Makefile silentoldconfig ; fi
>
> In this way:
>
>
> # If .config is newer than include/config/auto.conf, someone tinkered
> # with it and forgot to run make oldconfig.
> # if auto.conf.cmd is missing then we are probably in a cleaned tree so
> # we execute the config step to be sure to catch updated Kconfig files
> include/config/%.conf: $(KCONFIG_CONFIG) include/config/auto.conf.cmd
> if [[ ! -e include/config/auto.conf ]]; then $(MAKE) -f
> $(srctree)/Makefile silentoldconfig ; fi
> # $(Q)$(MAKE) -f $(srctree)/Makefile silentoldconfig
> else
> # external modules needs include/generated/autoconf.h and
> include/config/auto.conf
> # but do not care if they are up-to-date. Use auto.conf to trigger the test
> PHONY += include/config/auto.conf
>
> I had a similar problem during Android 5.0 build process, ad this patch
> solves. Hope it will the same for you.
>
> If it works I'll pass the patch to udooneo Team.
I've added this to my UDOO layer in a slightly modified version:
https://github.com/graugans/meta-udoo/blob/jethro/recipes-kernel/linux/linux-udooboard/0003-avoid-endless-loop.patch
Regards,
Christian
>
> Bye
> Giuseppe
>
>
>
> 2016-01-03 19:14 GMT+01:00 Christian Ege <k4230r6@gmail.com
> <mailto:k4230r6@gmail.com>>:
>
> Hi Giuseppe,
>
> Am 03.01.2016 7:08 nachm. schrieb "Giuseppe Pagano"
> >
> > Did you solved ?
> I did a little investigation but did not finally succeeded.
> > Maybe I have a patch for you.
> >
> This would be awesome.
>
> Regards,
> Christian
>
>
> >
> >
> > Christian Ege k4230r6 at gmail.com <http://gmail.com>
> > Sun Nov 29 12:24:50 PST 2015
> >
> > Previous message: [yocto] [meta-security][PATCH] nmap: package
> update to 7.0
> > Next message: [yocto] [Recipe reporting system] Upgradable recipe
> name list
> > Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
> > ________________________________
> >
> > Hi,
> >
> > can anyone give me some advice how to debug an endless loop during
> > kernel and module recipes with my UDOO Neo support layer?
> >
> > https://github.com/graugans/meta-fsl-arm-extra/tree/master-udooneo
> >
> > When I build the kernel for the UDOO Neo kernel or a module with
> bitbake
> > the bitbake process hangs in an endless loop:
> >
> >
> > bitbake -v kernel-module-imx-gpu-viv
> >
> > + cd
> >
> /data/FSL/fsl-community-bsp-master/build/tmp/work/udooneo-poky-linux-gnueabi/kernel-module-imx-gpu-viv/5.0.11.p7.1+fslc+gitAUTOINC+eeeb23c0fb-r0/git
> > + do_make_scripts
> > + unset CFLAGS CPPFLAGS CXXFLAGS LDFLAGS
> > + make CC=arm-poky-linux-gnueabi-gcc -mno-thumb-interwork -marm
> > -fuse-ld=bfd LD=arm-poky-linux-gnueabi-ld.bfd
> > AR=arm-poky-linux-gnueabi-ar -C
> >
> /data/FSL/fsl-community-bsp-master/build/tmp/work-shared/udooneo/kernel-source
> >
> O=/data/FSL/fsl-community-bsp-master/build/tmp/work-shared/udooneo/kernel-build-artifacts
> > scripts
> >
> > make: Entering directory
> >
> '/data/FSL/fsl-community-bsp-master/build/tmp/work-shared/udooneo/kernel-source'
> >
> > GEN
> >
> /data/FSL/fsl-community-bsp-master/build/tmp/work-shared/udooneo/kernel-build-artifacts/Makefile
> >
> > scripts/kconfig/conf --silentoldconfig Kconfig
> >
> > GEN
> >
> /data/FSL/fsl-community-bsp-master/build/tmp/work-shared/udooneo/kernel-build-artifacts/Makefile
> >
> > scripts/kconfig/conf --silentoldconfig Kconfig
> >
> > GEN /data/FSL/fsl-community-bsp-master/build/tmp/work-shared
> >
> > For the kernel I can workaround this by adding the following line
> to the
> > recipe:
> >
> > B = "${S}"
> >
> > But this does not work for kernel module recipes like the
> > "kernel-module-imx-gpu-viv"
>
>
WARNING: multiple messages have this Message-ID (diff)
From: Christian Ege <k4230r6@gmail.com>
To: Yocto list discussion <yocto@yoctoproject.org>,
"meta-freescale@yoctoproject.org"
<meta-freescale@yoctoproject.org>
Subject: Re: [yocto] Kernel build gets stuck in a endless loop
Date: Wed, 27 Jan 2016 20:40:31 +0100 [thread overview]
Message-ID: <56A91D2F.6080800@gmail.com> (raw)
In-Reply-To: <CAJTF2nT-hOXiuUa8ta=cPVXPejg2ck=AzA+3xJNuszVkuBu+CQ@mail.gmail.com>
Hi,
Thanks to Guiseppe Pagano, there is a solution for this issue. It is
more a hot fix than a real solution but this is maybe for someone else
helpful.
> Hi Crhistian,
> It is not a clean patch, but it works for me.
>
> File: kernel_imx_3.14/Makefile
>
> - $(Q)$(MAKE) -f $(srctree)/Makefile silentoldconfig
> + if [[ ! -e include/config/auto.conf ]]; then $(MAKE) -f
> $(srctree)/Makefile silentoldconfig ; fi
>
> In this way:
>
>
> # If .config is newer than include/config/auto.conf, someone tinkered
> # with it and forgot to run make oldconfig.
> # if auto.conf.cmd is missing then we are probably in a cleaned tree so
> # we execute the config step to be sure to catch updated Kconfig files
> include/config/%.conf: $(KCONFIG_CONFIG) include/config/auto.conf.cmd
> if [[ ! -e include/config/auto.conf ]]; then $(MAKE) -f
> $(srctree)/Makefile silentoldconfig ; fi
> # $(Q)$(MAKE) -f $(srctree)/Makefile silentoldconfig
> else
> # external modules needs include/generated/autoconf.h and
> include/config/auto.conf
> # but do not care if they are up-to-date. Use auto.conf to trigger the test
> PHONY += include/config/auto.conf
>
> I had a similar problem during Android 5.0 build process, ad this patch
> solves. Hope it will the same for you.
>
> If it works I'll pass the patch to udooneo Team.
I've added this to my UDOO layer in a slightly modified version:
https://github.com/graugans/meta-udoo/blob/jethro/recipes-kernel/linux/linux-udooboard/0003-avoid-endless-loop.patch
Regards,
Christian
>
> Bye
> Giuseppe
>
>
>
> 2016-01-03 19:14 GMT+01:00 Christian Ege <k4230r6@gmail.com
> <mailto:k4230r6@gmail.com>>:
>
> Hi Giuseppe,
>
> Am 03.01.2016 7:08 nachm. schrieb "Giuseppe Pagano"
> >
> > Did you solved ?
> I did a little investigation but did not finally succeeded.
> > Maybe I have a patch for you.
> >
> This would be awesome.
>
> Regards,
> Christian
>
>
> >
> >
> > Christian Ege k4230r6 at gmail.com <http://gmail.com>
> > Sun Nov 29 12:24:50 PST 2015
> >
> > Previous message: [yocto] [meta-security][PATCH] nmap: package
> update to 7.0
> > Next message: [yocto] [Recipe reporting system] Upgradable recipe
> name list
> > Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
> > ________________________________
> >
> > Hi,
> >
> > can anyone give me some advice how to debug an endless loop during
> > kernel and module recipes with my UDOO Neo support layer?
> >
> > https://github.com/graugans/meta-fsl-arm-extra/tree/master-udooneo
> >
> > When I build the kernel for the UDOO Neo kernel or a module with
> bitbake
> > the bitbake process hangs in an endless loop:
> >
> >
> > bitbake -v kernel-module-imx-gpu-viv
> >
> > + cd
> >
> /data/FSL/fsl-community-bsp-master/build/tmp/work/udooneo-poky-linux-gnueabi/kernel-module-imx-gpu-viv/5.0.11.p7.1+fslc+gitAUTOINC+eeeb23c0fb-r0/git
> > + do_make_scripts
> > + unset CFLAGS CPPFLAGS CXXFLAGS LDFLAGS
> > + make CC=arm-poky-linux-gnueabi-gcc -mno-thumb-interwork -marm
> > -fuse-ld=bfd LD=arm-poky-linux-gnueabi-ld.bfd
> > AR=arm-poky-linux-gnueabi-ar -C
> >
> /data/FSL/fsl-community-bsp-master/build/tmp/work-shared/udooneo/kernel-source
> >
> O=/data/FSL/fsl-community-bsp-master/build/tmp/work-shared/udooneo/kernel-build-artifacts
> > scripts
> >
> > make: Entering directory
> >
> '/data/FSL/fsl-community-bsp-master/build/tmp/work-shared/udooneo/kernel-source'
> >
> > GEN
> >
> /data/FSL/fsl-community-bsp-master/build/tmp/work-shared/udooneo/kernel-build-artifacts/Makefile
> >
> > scripts/kconfig/conf --silentoldconfig Kconfig
> >
> > GEN
> >
> /data/FSL/fsl-community-bsp-master/build/tmp/work-shared/udooneo/kernel-build-artifacts/Makefile
> >
> > scripts/kconfig/conf --silentoldconfig Kconfig
> >
> > GEN /data/FSL/fsl-community-bsp-master/build/tmp/work-shared
> >
> > For the kernel I can workaround this by adding the following line
> to the
> > recipe:
> >
> > B = "${S}"
> >
> > But this does not work for kernel module recipes like the
> > "kernel-module-imx-gpu-viv"
>
>
next parent reply other threads:[~2016-01-27 19:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAJTF2nSAzJvaqSsm4GZeTJbc2=L-Fw-mbP+OXnbfaBxN0NU8rw@mail.gmail.com>
[not found] ` <CAALGJZb0LgOF_FVEeiUH=FYTzA7-_G4xS28XpNXyc14XTBG6uQ@mail.gmail.com>
[not found] ` <CAJTF2nT-hOXiuUa8ta=cPVXPejg2ck=AzA+3xJNuszVkuBu+CQ@mail.gmail.com>
2016-01-27 19:40 ` Christian Ege [this message]
2016-01-27 19:40 ` [yocto] Kernel build gets stuck in a endless loop Christian Ege
2015-11-29 20:24 Christian Ege
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=56A91D2F.6080800@gmail.com \
--to=k4230r6@gmail.com \
--cc=meta-freescale@yoctoproject.org \
--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.