I've downloaded the l4re-core-2010070715.tar.bz2 archive, and I've tried to build the project. I have no problem compiling the Fiasco.OC kernel, but the L4Re core build seems to be entering an infinite loop. After running for a few seconds, I get the following lines repeated forever:
All checked ok. scripts/kconfig/conf -s [l4dir]/mk/Kconfig scripts/kconfig/conf -s [l4dir]/mk/Kconfig make[11]: Nothing to be done for `all'.
I also noticed that I get this same infinite loop if I do make config (after the menu exits) or make oldconfig. Something about the post-config clean-up seems to be continuously forking new processes and looping. The comment at line 179 of the [l4dir]/Makefile indicates that make is called again for postprocessing, but I don't know make well enough to debug this problem. Any ideas what's causing the problem? I've included the output below for reference.
Thanks, Michael Kirkpatrick
$ tar xf l4re-core-2010070715.tar $ cd l4re-core-2010070715/src/l4 $ make B=builddir --no-print-directory All checked ok. Creating build directory "builddir"... HOSTCC scripts/basic/fixdep HOSTCC scripts/basic/docproc HOSTCC scripts/basic/hash HOSTCC scripts/kconfig/conf.o [l4dir]/tool/kconfig/scripts/kconfig/conf.c: In function 'conf_askvalue': [l4dir]/tool/kconfig/scripts/kconfig/conf.c:105: warning: ignoring return value of 'fgets', declared with attribute warn_unused_result [l4dir]/tool/kconfig/scripts/kconfig/conf.c: In function 'conf_choice': [l4dir]/tool/kconfig/scripts/kconfig/conf.c:307: warning: ignoring return value of 'fgets', declared with attribute warn_unused_result HOSTCC scripts/kconfig/kxgettext.o SHIPPED scripts/kconfig/zconf.tab.c SHIPPED scripts/kconfig/lex.zconf.c SHIPPED scripts/kconfig/zconf.hash.c HOSTCC scripts/kconfig/zconf.tab.o HOSTLD scripts/kconfig/conf scripts/kconfig/conf -o [l4dir]/mk/Kconfig # # configuration written to .kconfig # scripts/kconfig/conf -s [l4dir]/mk/Kconfig scripts/kconfig/conf -s [l4dir]/mk/Kconfig scripts/kconfig/conf -s [l4dir]/mk/Kconfig scripts/kconfig/conf -s [l4dir]/mk/Kconfig All checked ok. scripts/kconfig/conf -s [l4dir]/mk/Kconfig gcc -fPIC -Wall -pedantic -g -m32 -c [l4dir]/tool/gendep/deptrack.c -o [l4dir]/builddir/tool/gendep/deptrack.32.o gcc -fPIC -Wall -pedantic -g -m32 -c [l4dir]/tool/gendep/syscall.c -o [l4dir]/builddir/tool/gendep/syscall.32.o mkdir -p [l4dir]/builddir/tool/gendep/32 gcc -m32 -shared -Wl,-soname,[l4dir]/builddir/tool/gendep/32/libgendep.so -ldl -o [l4dir]/builddir/tool/gendep/32/libgendep.so [l4dir]/builddir/tool/gendep/deptrack.32.o [l4dir]/builddir/tool/gendep/syscall.32.o scripts/kconfig/conf -s [l4dir]/mk/Kconfig scripts/kconfig/conf -s [l4dir]/mk/Kconfig scripts/kconfig/conf -s [l4dir]/mk/Kconfig All checked ok. scripts/kconfig/conf -s [l4dir]/mk/Kconfig scripts/kconfig/conf -s [l4dir]/mk/Kconfig All checked ok. scripts/kconfig/conf -s [l4dir]/mk/Kconfig make[11]: Nothing to be done for `all'. scripts/kconfig/conf -s [l4dir]/mk/Kconfig scripts/kconfig/conf -s [l4dir]/mk/Kconfig All checked ok. scripts/kconfig/conf -s [l4dir]/mk/Kconfig ^Cmake[12]: *** Deleting file `[l4dir]/builddir/.config.all' make[15]: *** [silentoldconfig] Interrupt make[14]: *** [sub-make] Interrupt make[13]: *** [[l4dir]/builddir/.kconfig.auto] Interrupt make[12]: *** [[l4dir]/builddir/.config.all] Interrupt make[11]: *** [DROPSCONF_CONFIG_MK_POST_HOOK] Interrupt make[10]: *** [[l4dir]/builddir/.config.all] Interrupt make[9]: *** [DROPSCONF_CONFIG_MK_POST_HOOK] Interrupt make[8]: *** [[l4dir]/builddir/.config.all] Interrupt make[7]: *** [DROPSCONF_CONFIG_MK_POST_HOOK] Interrupt make[6]: *** [[l4dir]/builddir/.config.all] Interrupt make[5]: *** [[l4dir]/builddir/.config.all] Interrupt make[4]: *** [DROPSCONF_CONFIG_MK_POST_HOOK] Interrupt make[3]: *** [[l4dir]/builddir/.config.all] Interrupt make[2]: *** [[l4dir]/builddir/.config.all] Interrupt make[1]: *** [oldconfig] Interrupt make: *** [all] Interrupt
Are you using ecryptfs? This known to cause this infinite recursion. However as far as I know there is no fix yet but to build outside your ecryptfs directory.
Regards, Matthias.
Sent from my iPhone
On 03.08.2010, at 22:06, Michael Kirkpatrick mkirkpat@cs.purdue.edu wrote:
I've downloaded the l4re-core-2010070715.tar.bz2 archive, and I've tried to build the project. I have no problem compiling the Fiasco.OC kernel, but the L4Re core build seems to be entering an infinite loop. After running for a few seconds, I get the following lines repeated forever:
All checked ok. scripts/kconfig/conf -s [l4dir]/mk/Kconfig scripts/kconfig/conf -s [l4dir]/mk/Kconfig make[11]: Nothing to be done for `all'.
I also noticed that I get this same infinite loop if I do make config (after the menu exits) or make oldconfig. Something about the post-config clean-up seems to be continuously forking new processes and looping. The comment at line 179 of the [l4dir]/Makefile indicates that make is called again for postprocessing, but I don't know make well enough to debug this problem. Any ideas what's causing the problem? I've included the output below for reference.
Thanks, Michael Kirkpatrick
$ tar xf l4re-core-2010070715.tar $ cd l4re-core-2010070715/src/l4 $ make B=builddir --no-print-directory All checked ok. Creating build directory "builddir"... HOSTCC scripts/basic/fixdep HOSTCC scripts/basic/docproc HOSTCC scripts/basic/hash HOSTCC scripts/kconfig/conf.o [l4dir]/tool/kconfig/scripts/kconfig/conf.c: In function 'conf_askvalue': [l4dir]/tool/kconfig/scripts/kconfig/conf.c:105: warning: ignoring return value of 'fgets', declared with attribute warn_unused_result [l4dir]/tool/kconfig/scripts/kconfig/conf.c: In function 'conf_choice': [l4dir]/tool/kconfig/scripts/kconfig/conf.c:307: warning: ignoring return value of 'fgets', declared with attribute warn_unused_result HOSTCC scripts/kconfig/kxgettext.o SHIPPED scripts/kconfig/zconf.tab.c SHIPPED scripts/kconfig/lex.zconf.c SHIPPED scripts/kconfig/zconf.hash.c HOSTCC scripts/kconfig/zconf.tab.o HOSTLD scripts/kconfig/conf scripts/kconfig/conf -o [l4dir]/mk/Kconfig # # configuration written to .kconfig # scripts/kconfig/conf -s [l4dir]/mk/Kconfig scripts/kconfig/conf -s [l4dir]/mk/Kconfig scripts/kconfig/conf -s [l4dir]/mk/Kconfig scripts/kconfig/conf -s [l4dir]/mk/Kconfig All checked ok. scripts/kconfig/conf -s [l4dir]/mk/Kconfig gcc -fPIC -Wall -pedantic -g -m32 -c [l4dir]/tool/gendep/deptrack.c -o [l4dir]/builddir/tool/gendep/deptrack.32.o gcc -fPIC -Wall -pedantic -g -m32 -c [l4dir]/tool/gendep/syscall.c -o [l4dir]/builddir/tool/gendep/syscall.32.o mkdir -p [l4dir]/builddir/tool/gendep/32 gcc -m32 -shared -Wl,-soname,[l4dir]/builddir/tool/gendep/32/libgendep.so -ldl -o [l4dir]/builddir/tool/gendep/32/libgendep.so [l4dir]/builddir/tool/gendep/deptrack.32.o [l4dir]/builddir/tool/gendep/syscall.32.o scripts/kconfig/conf -s [l4dir]/mk/Kconfig scripts/kconfig/conf -s [l4dir]/mk/Kconfig scripts/kconfig/conf -s [l4dir]/mk/Kconfig All checked ok. scripts/kconfig/conf -s [l4dir]/mk/Kconfig scripts/kconfig/conf -s [l4dir]/mk/Kconfig All checked ok. scripts/kconfig/conf -s [l4dir]/mk/Kconfig make[11]: Nothing to be done for `all'. scripts/kconfig/conf -s [l4dir]/mk/Kconfig scripts/kconfig/conf -s [l4dir]/mk/Kconfig All checked ok. scripts/kconfig/conf -s [l4dir]/mk/Kconfig ^Cmake[12]: *** Deleting file `[l4dir]/builddir/.config.all' make[15]: *** [silentoldconfig] Interrupt make[14]: *** [sub-make] Interrupt make[13]: *** [[l4dir]/builddir/.kconfig.auto] Interrupt make[12]: *** [[l4dir]/builddir/.config.all] Interrupt make[11]: *** [DROPSCONF_CONFIG_MK_POST_HOOK] Interrupt make[10]: *** [[l4dir]/builddir/.config.all] Interrupt make[9]: *** [DROPSCONF_CONFIG_MK_POST_HOOK] Interrupt make[8]: *** [[l4dir]/builddir/.config.all] Interrupt make[7]: *** [DROPSCONF_CONFIG_MK_POST_HOOK] Interrupt make[6]: *** [[l4dir]/builddir/.config.all] Interrupt make[5]: *** [[l4dir]/builddir/.config.all] Interrupt make[4]: *** [DROPSCONF_CONFIG_MK_POST_HOOK] Interrupt make[3]: *** [[l4dir]/builddir/.config.all] Interrupt make[2]: *** [[l4dir]/builddir/.config.all] Interrupt make[1]: *** [oldconfig] Interrupt make: *** [all] Interrupt
l4-hackers mailing list l4-hackers@os.inf.tu-dresden.de http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
On Tue Aug 03, 2010 at 16:06:05 -0400, Michael Kirkpatrick wrote:
I've downloaded the l4re-core-2010070715.tar.bz2 archive, and I've tried to build the project. I have no problem compiling the Fiasco.OC kernel, but the L4Re core build seems to be entering an infinite loop. After running for a few seconds, I get the following lines repeated forever:
All checked ok. scripts/kconfig/conf -s [l4dir]/mk/Kconfig scripts/kconfig/conf -s [l4dir]/mk/Kconfig make[11]: Nothing to be done for `all'.
I also noticed that I get this same infinite loop if I do make config (after the menu exits) or make oldconfig. Something about the post-config clean-up seems to be continuously forking new processes and looping. The comment at line 179 of the [l4dir]/Makefile indicates that make is called again for postprocessing, but I don't know make well enough to debug this problem. Any ideas what's causing the problem? I've included the output below for reference.
On which file system is that? I've been told there are issue with ecryptfs and there have been with ext4 iirc.
Adam
It was in ecryptfs. I moved it over to an ext4 partition and had no problems there.
Thanks, Michael
On Tue, 3 Aug 2010, Adam Lackorzynski wrote:
On Tue Aug 03, 2010 at 16:06:05 -0400, Michael Kirkpatrick wrote:
I've downloaded the l4re-core-2010070715.tar.bz2 archive, and I've tried to build the project. I have no problem compiling the Fiasco.OC kernel, but the L4Re core build seems to be entering an infinite loop. After running for a few seconds, I get the following lines repeated forever:
All checked ok. scripts/kconfig/conf -s [l4dir]/mk/Kconfig scripts/kconfig/conf -s [l4dir]/mk/Kconfig make[11]: Nothing to be done for `all'.
I also noticed that I get this same infinite loop if I do make config (after the menu exits) or make oldconfig. Something about the post-config clean-up seems to be continuously forking new processes and looping. The comment at line 179 of the [l4dir]/Makefile indicates that make is called again for postprocessing, but I don't know make well enough to debug this problem. Any ideas what's causing the problem? I've included the output below for reference.
On which file system is that? I've been told there are issue with ecryptfs and there have been with ext4 iirc.
Adam
Adam adam@os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/
l4-hackers mailing list l4-hackers@os.inf.tu-dresden.de http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
l4-hackers@os.inf.tu-dresden.de