Re: Trouble building l4linux
On Sun Jun 08, 2014 at 10:44:32 +0200, Sören Jonsson wrote: > I have successfully built L4Fiasco and L4Re, and tested it by running the > hello test program under quemu. After that I attempted to build L4linux, > using instructions from this site: http://wiki.tudos.org/L4Linux/build . > > Unfortunately, when I came to the stage of "make O=/home/osj/l4linux_bld/" I > get an error message "make[2]: *** > [/home/osj/l4/l4linux_bld/Makeconf.l4conf] Error 1 > > make[1]: *** No rule for creating the target > "/home/osj/l4/l4linux_bld/Makeconf.l4conf" Is there a .config file in /home/osj/l4/l4linux_bld? That would be generated by a preceding make O=... ...config run. Adam -- Adam [email protected] Lackorzynski http://os.inf.tu-dresden.de/~adam/ ___ l4-hackers mailing list [email protected] http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
Trouble building l4linux
Hello, I have successfully built L4Fiasco and L4Re, and tested it by running the hello test program under quemu. After that I attempted to build L4linux, using instructions from this site: http://wiki.tudos.org/L4Linux/build . Unfortunately, when I came to the stage of "make O=/home/osj/l4linux_bld/" I get an error message "make[2]: *** [/home/osj/l4/l4linux_bld/Makeconf.l4conf] Error 1 make[1]: *** No rule for creating the target "/home/osj/l4/l4linux_bld/Makeconf.l4conf" Is there another web page I should get my instructions from, or is there anything I have missed in my attempt to build l4linux? Best regards, Sören Jonsson Sweden ___ l4-hackers mailing list [email protected] http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
Re: Building L4Linux for ARM
On Wed Jun 15, 2011 at 16:25:37 +0100, Anna Fischer wrote: > I have built (and successfully run) fiasco and L4Re for a Cortex-A9 > (ARMv7), RealView PBX platform. When building L4Linux now, the > menuconfig automatically selects L4Linux as the system type, but then it > only offers ARMv5 or ARMv6 as build type. Does that mean there is no > support for ARMv7 in L4Linux yet? Just take ARMv6, it does not really matter for L4Linux. For example it would be also possible to run the v5 version in this setup (MP excluded). Adam -- Adam [email protected] Lackorzynski http://os.inf.tu-dresden.de/~adam/ ___ l4-hackers mailing list [email protected] http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
Re: Building L4Linux for ARM
On Wed, 2011-06-15 at 13:22 +, Adam Lackorzynski wrote: > Hi, > > On Wed Jun 15, 2011 at 13:24:44 +0100, Anna Fischer wrote: > > On Wed, 2011-06-15 at 11:44 +, Fischer, Anna wrote: > > > I am trying to compile/build L4Linux for an ARM-based platform. > > > > > > When I execute make then I get an error saying Makeconf.l4conf cannot be > > > found. > > > > > > These are the steps I have followed to build L4Linux. > > > > > > # cd /root/l4linux > > > # svn co http://svn.tudos.org/repos/oc/l4linux/trunk l4linux > > > # cd l4linux/ > > > # mkdir build > > > # cp arch/l4/configs/arm-mp_defconfig build/.config > > > # make O=build/ oldconfig > > > # make O=build/ menuconfig > > > (set L4 tree build directory to '/root/l4linux/l4linux/build') > > > (de-configure PCI etc) > > > # make O=build/ > > > > > > L4 source directory: /root/l4linux/l4linux > > > PWD=/root/l4linux/l4linux make -C /root/l4linux/l4linux > > > -f /root/l4linux/l4linux/arch/l4/Makefile.l4conf > > > O=/root/l4linux/l4linux/build L4X_LOOP_CHECK=1 > > > OUTPUT=/root/l4linux/l4linux/build/Makeconf.l4conf > > > make[3]: *** No rule to make target `/.config.all', needed by > > > `/root/l4linux/l4linux/build/Makeconf.l4conf'. Stop. > > > make[2]: *** [/root/l4linux/l4linux/build/Makeconf.l4conf] Error 2 > > > GEN /root/l4linux/l4linux/build/Makefile > > > scripts/kconfig/conf --silentoldconfig Kconfig > > > make[2]: *** No rule to make target `/.config.all', needed by > > > `/root/l4linux/l4linux/build/Makeconf.l4conf'. Stop. > > > Creating asm-l4/api-l4env -> asm/api symlink > > > Creating asm-l4/l4lxapi/impl symlink > > > Creating asm-l4/l4x-arm -> asm/l4x symlink > > > Creating asm-l4/l4-arch/asm symlink > > > Creating asm-l4/arm-arch/mach symlink > > > Creating asm-l4/orig-arch symlink > > > make[1]: *** No rule to make target > > > `/root/l4linux/l4linux/build/Makeconf.l4conf', needed by `archprepare'. > > > Stop. > > > make: *** [sub-make] Error 2 > > > > > > > I figured that this was because I did not point to the L4Re build > > directory. Now I have changed that appropriately, and the build runs a > > bit further. Now I am getting the following error: > > > > # make O=build/ > > Package libio-io was not found in the pkg-config search path. > > Perhaps you should add the directory containing `libio-io.pc' > > to the PKG_CONFIG_PATH environment variable > > Package 'libio-io', required by 'libio', not found > > Getting required compilation flags failed. > > L4OBJ: /root/l4re-core-2011042112/src/l4/testbuild > > L4_REQUIRED_MODS: stdlibs log l4re_c-util libio shmc > > /root/l4linux/l4linux/arch/l4/Makefile:306: *** Aborting.. Stop. > > make: *** [sub-make] Error 2 > > To build L4Linux, you need the packages that are summarized with the > 'l4linux_requiremnts' keyword at the repomgr. > > To build a Linux for ARM, the build command looks as follows: > > $ make O=... L4ARCH=arm CROSS_COMPILER=arm-linux- arm_defconfig > > Change path to corresponding l4re-objdir: > $ make O=... L4ARCH=arm CROSS_COMPILER=arm-linux- menuconfig > > Build: > $ make O=... L4ARCH=arm CROSS_COMPILER=arm-linux- -j2 > > Which should result in a vmlinuz file in the Linux build root directory. > > > I've updated http://wiki.tudos.org/Quickstart to include a section on > building L4Linux on ARM. OK, thanks, that works better now. I have built (and successfully run) fiasco and L4Re for a Cortex-A9 (ARMv7), RealView PBX platform. When building L4Linux now, the menuconfig automatically selects L4Linux as the system type, but then it only offers ARMv5 or ARMv6 as build type. Does that mean there is no support for ARMv7 in L4Linux yet? Thanks again, Anna ___ l4-hackers mailing list [email protected] http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
Re: Building L4Linux for ARM
Hi, On Wed Jun 15, 2011 at 13:24:44 +0100, Anna Fischer wrote: > On Wed, 2011-06-15 at 11:44 +, Fischer, Anna wrote: > > I am trying to compile/build L4Linux for an ARM-based platform. > > > > When I execute make then I get an error saying Makeconf.l4conf cannot be > > found. > > > > These are the steps I have followed to build L4Linux. > > > > # cd /root/l4linux > > # svn co http://svn.tudos.org/repos/oc/l4linux/trunk l4linux > > # cd l4linux/ > > # mkdir build > > # cp arch/l4/configs/arm-mp_defconfig build/.config > > # make O=build/ oldconfig > > # make O=build/ menuconfig > > (set L4 tree build directory to '/root/l4linux/l4linux/build') > > (de-configure PCI etc) > > # make O=build/ > > > > L4 source directory: /root/l4linux/l4linux > > PWD=/root/l4linux/l4linux make -C /root/l4linux/l4linux > > -f /root/l4linux/l4linux/arch/l4/Makefile.l4conf > > O=/root/l4linux/l4linux/build L4X_LOOP_CHECK=1 > > OUTPUT=/root/l4linux/l4linux/build/Makeconf.l4conf > > make[3]: *** No rule to make target `/.config.all', needed by > > `/root/l4linux/l4linux/build/Makeconf.l4conf'. Stop. > > make[2]: *** [/root/l4linux/l4linux/build/Makeconf.l4conf] Error 2 > > GEN /root/l4linux/l4linux/build/Makefile > > scripts/kconfig/conf --silentoldconfig Kconfig > > make[2]: *** No rule to make target `/.config.all', needed by > > `/root/l4linux/l4linux/build/Makeconf.l4conf'. Stop. > > Creating asm-l4/api-l4env -> asm/api symlink > > Creating asm-l4/l4lxapi/impl symlink > > Creating asm-l4/l4x-arm -> asm/l4x symlink > > Creating asm-l4/l4-arch/asm symlink > > Creating asm-l4/arm-arch/mach symlink > > Creating asm-l4/orig-arch symlink > > make[1]: *** No rule to make target > > `/root/l4linux/l4linux/build/Makeconf.l4conf', needed by `archprepare'. > > Stop. > > make: *** [sub-make] Error 2 > > > > I figured that this was because I did not point to the L4Re build > directory. Now I have changed that appropriately, and the build runs a > bit further. Now I am getting the following error: > > # make O=build/ > Package libio-io was not found in the pkg-config search path. > Perhaps you should add the directory containing `libio-io.pc' > to the PKG_CONFIG_PATH environment variable > Package 'libio-io', required by 'libio', not found > Getting required compilation flags failed. > L4OBJ: /root/l4re-core-2011042112/src/l4/testbuild > L4_REQUIRED_MODS: stdlibs log l4re_c-util libio shmc > /root/l4linux/l4linux/arch/l4/Makefile:306: *** Aborting.. Stop. > make: *** [sub-make] Error 2 To build L4Linux, you need the packages that are summarized with the 'l4linux_requiremnts' keyword at the repomgr. To build a Linux for ARM, the build command looks as follows: $ make O=... L4ARCH=arm CROSS_COMPILER=arm-linux- arm_defconfig Change path to corresponding l4re-objdir: $ make O=... L4ARCH=arm CROSS_COMPILER=arm-linux- menuconfig Build: $ make O=... L4ARCH=arm CROSS_COMPILER=arm-linux- -j2 Which should result in a vmlinuz file in the Linux build root directory. I've updated http://wiki.tudos.org/Quickstart to include a section on building L4Linux on ARM. Adam -- Adam [email protected] Lackorzynski http://os.inf.tu-dresden.de/~adam/ ___ l4-hackers mailing list [email protected] http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
Re: Building L4Linux for ARM
On Wed, 2011-06-15 at 11:44 +, Fischer, Anna wrote: > Hi, > > I am trying to compile/build L4Linux for an ARM-based platform. > > When I execute make then I get an error saying Makeconf.l4conf cannot be > found. > > These are the steps I have followed to build L4Linux. > > # cd /root/l4linux > # svn co http://svn.tudos.org/repos/oc/l4linux/trunk l4linux > # cd l4linux/ > # mkdir build > # cp arch/l4/configs/arm-mp_defconfig build/.config > # make O=build/ oldconfig > # make O=build/ menuconfig > (set L4 tree build directory to '/root/l4linux/l4linux/build') > (de-configure PCI etc) > # make O=build/ > > L4 source directory: /root/l4linux/l4linux > PWD=/root/l4linux/l4linux make -C /root/l4linux/l4linux > -f /root/l4linux/l4linux/arch/l4/Makefile.l4conf > O=/root/l4linux/l4linux/build L4X_LOOP_CHECK=1 > OUTPUT=/root/l4linux/l4linux/build/Makeconf.l4conf > make[3]: *** No rule to make target `/.config.all', needed by > `/root/l4linux/l4linux/build/Makeconf.l4conf'. Stop. > make[2]: *** [/root/l4linux/l4linux/build/Makeconf.l4conf] Error 2 > GEN /root/l4linux/l4linux/build/Makefile > scripts/kconfig/conf --silentoldconfig Kconfig > make[2]: *** No rule to make target `/.config.all', needed by > `/root/l4linux/l4linux/build/Makeconf.l4conf'. Stop. > Creating asm-l4/api-l4env -> asm/api symlink > Creating asm-l4/l4lxapi/impl symlink > Creating asm-l4/l4x-arm -> asm/l4x symlink > Creating asm-l4/l4-arch/asm symlink > Creating asm-l4/arm-arch/mach symlink > Creating asm-l4/orig-arch symlink > make[1]: *** No rule to make target > `/root/l4linux/l4linux/build/Makeconf.l4conf', needed by `archprepare'. > Stop. > make: *** [sub-make] Error 2 > I figured that this was because I did not point to the L4Re build directory. Now I have changed that appropriately, and the build runs a bit further. Now I am getting the following error: # make O=build/ Package libio-io was not found in the pkg-config search path. Perhaps you should add the directory containing `libio-io.pc' to the PKG_CONFIG_PATH environment variable Package 'libio-io', required by 'libio', not found Getting required compilation flags failed. L4OBJ: /root/l4re-core-2011042112/src/l4/testbuild L4_REQUIRED_MODS: stdlibs log l4re_c-util libio shmc /root/l4linux/l4linux/arch/l4/Makefile:306: *** Aborting.. Stop. make: *** [sub-make] Error 2 Looking into my L4Re build directory, I thought the modules are all there: # ls -l /root/l4re-core-2011042112/src/l4/testbuild/pkg/cxx_libc_io/lib/src/OBJ-arm_armv7a-l4f/ total 116 -rw-r--r-- 1 root root 1310 Jun 15 09:26 Makefile -rw-r--r-- 1 root root 828 Jun 15 09:26 Makefile.inc -rw-r--r-- 1 root root71 Jun 14 12:18 io_backend.cxxflags lrwxrwxrwx 1 root root71 Jun 14 12:18 io_backend.e.cc -> /root/l4re-core-2011042112/src/l4/pkg/cxx_libc_io/lib/src/io_backend.cc -rw-r--r-- 1 root root34 Jun 14 12:18 io_backend.e.cxxflags -rw-r--r-- 1 root root 18148 Jun 15 09:26 io_backend.e.o -rw-r--r-- 1 root root 17308 Jun 15 09:26 io_backend.o drwxr-xr-x 2 root root 4096 Jun 14 12:18 libcxx_libc_io -rw-r--r-- 1 root root 17852 Jun 15 09:26 libcxx_libc_io.a drwxr-xr-x 2 root root 4096 Jun 14 12:18 libcxx_libc_io_e -rw-r--r-- 1 root root 18796 Jun 15 09:26 libcxx_libc_io_e.a drwxr-xr-x 2 root root 4096 Jun 14 12:18 noexc drwxr-xr-x 2 root root 4096 Jun 14 12:18 r Any idea what the problem here is? Thanks, Anna ___ l4-hackers mailing list [email protected] http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
Building L4Linux for ARM
Hi, I am trying to compile/build L4Linux for an ARM-based platform. When I execute make then I get an error saying Makeconf.l4conf cannot be found. These are the steps I have followed to build L4Linux. # cd /root/l4linux # svn co http://svn.tudos.org/repos/oc/l4linux/trunk l4linux # cd l4linux/ # mkdir build # cp arch/l4/configs/arm-mp_defconfig build/.config # make O=build/ oldconfig # make O=build/ menuconfig (set L4 tree build directory to '/root/l4linux/l4linux/build') (de-configure PCI etc) # make O=build/ L4 source directory: /root/l4linux/l4linux PWD=/root/l4linux/l4linux make -C /root/l4linux/l4linux -f /root/l4linux/l4linux/arch/l4/Makefile.l4conf O=/root/l4linux/l4linux/build L4X_LOOP_CHECK=1 OUTPUT=/root/l4linux/l4linux/build/Makeconf.l4conf make[3]: *** No rule to make target `/.config.all', needed by `/root/l4linux/l4linux/build/Makeconf.l4conf'. Stop. make[2]: *** [/root/l4linux/l4linux/build/Makeconf.l4conf] Error 2 GEN /root/l4linux/l4linux/build/Makefile scripts/kconfig/conf --silentoldconfig Kconfig make[2]: *** No rule to make target `/.config.all', needed by `/root/l4linux/l4linux/build/Makeconf.l4conf'. Stop. Creating asm-l4/api-l4env -> asm/api symlink Creating asm-l4/l4lxapi/impl symlink Creating asm-l4/l4x-arm -> asm/l4x symlink Creating asm-l4/l4-arch/asm symlink Creating asm-l4/arm-arch/mach symlink Creating asm-l4/orig-arch symlink make[1]: *** No rule to make target `/root/l4linux/l4linux/build/Makeconf.l4conf', needed by `archprepare'. Stop. make: *** [sub-make] Error 2 My cross-compiler is arm-none-linux-gnueabi-gcc (Sourcery G++ Lite 2011.03-41) 4.5.2. I have successfully used it to also build fiasco + L4Re. Thanks for your help. Anna ___ l4-hackers mailing list [email protected] http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
Re: problem building L4Linux, comments welcome
On Tue Jan 18, 2011 at 21:58:26 -0600, eric van tassell wrote: > that seemed to work but why is that manual step needed? It's not when doing make in the proper directory (l4 root dir) and that runs to a successful end. Did you do something different? Adam -- Adam [email protected] Lackorzynski http://os.inf.tu-dresden.de/~adam/ ___ l4-hackers mailing list [email protected] http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
Re: problem building L4Linux, comments welcome
that seemed to work but why is that manual step needed? Thanks. -evt On Sun, Jan 16, 2011 at 6:09 PM, Adam Lackorzynski < [email protected]> wrote: > > On Sun Jan 16, 2011 at 17:57:04 -0600, eric van tassell wrote: > > another way of asking my question would be "how does this makefile stanza > > work"? > > > L4_EXT_CFLAGS := $(call L4_BID_PKG_CONFIG_CALL,$(L4OBJ),--cflags > > --define-variable=libc_variant=libc,$(L4_REQUIRED_MODS)) > > > ifneq ($(call L4_BID_PKG_CONFIG_FAILED,$(L4_EXT_CFLAGS)),) > > > $(info Getting required compilation flags failed.) > > > $(info L4OBJ: $(L4OBJ)) > > > $(info L4_REQUIRED_MODS: $(L4_REQUIRED_MODS)) > > > $(error Aborting.) > > > endif > > > > grepping the tree I dont see where L4_BID_PKG_CONFIG_CALL > > or L4_BID_PKG_CONFIG_FAILED are defined/modified. > > Thanks > > My guess would be that in the l4-objdir that isn't a file called > l4defs.mk.inc. A 'make' in the l4-objdir root-directory should generate > that. > > > > Adam > -- > Adam [email protected] > Lackorzynski http://os.inf.tu-dresden.de/~adam/ > > ___ > l4-hackers mailing list > [email protected] > http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers > -- - evt (Eric van Tassell) twitter: evt_texelsoft linked-in: linkedin.com/in/evttxl ___ l4-hackers mailing list [email protected] http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
Re: problem building L4Linux, comments welcome
On Sun Jan 16, 2011 at 17:57:04 -0600, eric van tassell wrote: > another way of asking my question would be "how does this makefile stanza > work"? > > L4_EXT_CFLAGS := $(call L4_BID_PKG_CONFIG_CALL,$(L4OBJ),--cflags > --define-variable=libc_variant=libc,$(L4_REQUIRED_MODS)) > > ifneq ($(call L4_BID_PKG_CONFIG_FAILED,$(L4_EXT_CFLAGS)),) > > $(info Getting required compilation flags failed.) > > $(info L4OBJ: $(L4OBJ)) > > $(info L4_REQUIRED_MODS: $(L4_REQUIRED_MODS)) > > $(error Aborting.) > > endif > > grepping the tree I dont see where L4_BID_PKG_CONFIG_CALL > or L4_BID_PKG_CONFIG_FAILED are defined/modified. > Thanks My guess would be that in the l4-objdir that isn't a file called l4defs.mk.inc. A 'make' in the l4-objdir root-directory should generate that. Adam -- Adam [email protected] Lackorzynski http://os.inf.tu-dresden.de/~adam/ ___ l4-hackers mailing list [email protected] http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
Re: problem building L4Linux, comments welcome
another way of asking my question would be "how does this makefile stanza work"? > L4_EXT_CFLAGS := $(call L4_BID_PKG_CONFIG_CALL,$(L4OBJ),--cflags --define-variable=libc_variant=libc,$(L4_REQUIRED_MODS)) > ifneq ($(call L4_BID_PKG_CONFIG_FAILED,$(L4_EXT_CFLAGS)),) > $(info Getting required compilation flags failed.) > $(info L4OBJ: $(L4OBJ)) > $(info L4_REQUIRED_MODS: $(L4_REQUIRED_MODS)) > $(error Aborting.) > endif grepping the tree I dont see where L4_BID_PKG_CONFIG_CALL or L4_BID_PKG_CONFIG_FAILED are defined/modified. Thanks On Sun, Jan 16, 2011 at 5:50 PM, eric van tassell wrote: > I was endeavoring to follow http://wiki.tudos.org/Quickstart. > Below's the tail of the build log. > Thanks for any suggestions. > > > L4 source directory: /home/evt/wrk/L4/TUD/forest1/src/l4 > PWD=/home/evt/wrk/L4/TUD/forest1/src/l4 make -C > /home/evt/wrk/L4/TUD/forest1/src/l4 -f > /home/evt/wrk/L4/TUD/forest1/src/l4linux/arch/l4/Makefile.l4conf > O=/home/evt/wrk/L4/TUD/forest1/src/l4/out L4X_LOOP_CHECK=1 > OUTPUT=/home/evt/wrk/L4/TUD/forest1/src/l4linux/out/Makeconf.l4conf > GEN /home/evt/wrk/L4/TUD/forest1/src/l4linux/out/Makeconf.l4conf > GEN /home/evt/wrk/L4/TUD/forest1/src/l4linux/out/Makefile > scripts/kconfig/conf --silentoldconfig arch/l4/Kconfig > Getting required compilation flags failed. > L4OBJ: /home/evt/wrk/L4/TUD/forest1/src/l4/out > L4_REQUIRED_MODS: stdlibs log l4re_c-util libio shmc rtc > /home/evt/wrk/L4/TUD/forest1/src/l4linux/arch/l4/Makefile:301: *** > Aborting.. > > > -- > - evt > (Eric van Tassell) > twitter: evt_texelsoft > linked-in: linkedin.com/in/evttxl > -- - evt (Eric van Tassell) twitter: evt_texelsoft linked-in: linkedin.com/in/evttxl ___ l4-hackers mailing list [email protected] http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
problem building L4Linux, comments welcome
I was endeavoring to follow http://wiki.tudos.org/Quickstart. Below's the tail of the build log. Thanks for any suggestions. L4 source directory: /home/evt/wrk/L4/TUD/forest1/src/l4 PWD=/home/evt/wrk/L4/TUD/forest1/src/l4 make -C /home/evt/wrk/L4/TUD/forest1/src/l4 -f /home/evt/wrk/L4/TUD/forest1/src/l4linux/arch/l4/Makefile.l4conf O=/home/evt/wrk/L4/TUD/forest1/src/l4/out L4X_LOOP_CHECK=1 OUTPUT=/home/evt/wrk/L4/TUD/forest1/src/l4linux/out/Makeconf.l4conf GEN /home/evt/wrk/L4/TUD/forest1/src/l4linux/out/Makeconf.l4conf GEN /home/evt/wrk/L4/TUD/forest1/src/l4linux/out/Makefile scripts/kconfig/conf --silentoldconfig arch/l4/Kconfig Getting required compilation flags failed. L4OBJ: /home/evt/wrk/L4/TUD/forest1/src/l4/out L4_REQUIRED_MODS: stdlibs log l4re_c-util libio shmc rtc /home/evt/wrk/L4/TUD/forest1/src/l4linux/arch/l4/Makefile:301: *** Aborting.. -- - evt (Eric van Tassell) twitter: evt_texelsoft linked-in: linkedin.com/in/evttxl ___ l4-hackers mailing list [email protected] http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
Re: Problem with building L4Linux
On Tue Dec 07, 2010 at 16:56:04 +0100, Nuno Santos wrote: > Thank you very much for your help. It's indeed a problem with > compiling ocaml. As you suggested, tagging it as 'broken' let's > compile go through. > > I traced the command that leads to this error (from directory > /local/ > l4re-snap/l4re-snapshot-2010111519/obj/l4/x86/pkg/ocaml/build/stdlib/ > OBJ-x86_586-l4f): > > $ ocamlopt -g -warn-error A -nostdlib -c -o stream.cmx > /local/l4re-snap/l4re-snapshot-2010111519/src/l4/pkg/ocaml/contrib/stdlib/stream.ml > /tmp/camlasm25fea1.s: Assembler messages: > /tmp/camlasm25fea1.s:580: Error: junk `lazy_force(%rip)' after > expression > /tmp/camlasm25fea1.s:580: Error: suffix or operands invalid for `lea' > /tmp/camlasm25fea1.s:785: Error: junk `lazy_force(%rip)' after > expression > /tmp/camlasm25fea1.s:785: Error: suffix or operands invalid for `lea' > Assembler error, input left in file /tmp/camlasm25fea1.s > > My version of ocamlopt is 3.10.2, and the distribution is Debian 5.0.6. Ok, that might be the difference, the version I have installed is 3.11.2. Thanks, Adam -- Adam [email protected] Lackorzynski http://os.inf.tu-dresden.de/~adam/ ___ l4-hackers mailing list [email protected] http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
Re: Problem with building L4Linux
Hi Adam
Thank you very much for your help. It's indeed a problem with
compiling ocaml. As you suggested, tagging it as 'broken' let's
compile go through.
I traced the command that leads to this error (from directory /local/
l4re-snap/l4re-snapshot-2010111519/obj/l4/x86/pkg/ocaml/build/stdlib/
OBJ-x86_586-l4f):
$ ocamlopt -g -warn-error A -nostdlib -c -o stream.cmx /local/l4re-
snap/l4re-snapshot-2010111519/src/l4/pkg/ocaml/contrib/stdlib/stream.ml
/tmp/camlasm25fea1.s: Assembler messages:
/tmp/camlasm25fea1.s:580: Error: junk `lazy_force(%rip)' after
expression
/tmp/camlasm25fea1.s:580: Error: suffix or operands invalid for `lea'
/tmp/camlasm25fea1.s:785: Error: junk `lazy_force(%rip)' after
expression
/tmp/camlasm25fea1.s:785: Error: suffix or operands invalid for `lea'
Assembler error, input left in file /tmp/camlasm25fea1.s
My version of ocamlopt is 3.10.2, and the distribution is Debian 5.0.6.
Thanks again,
--Nuno
On Dec 7, 2010, at 3:35 PM, Adam Lackorzynski wrote:
Hi,
On Tue Dec 07, 2010 at 09:24:52 +0100, Nuno Santos wrote:
I'm having trouble with building l4linux. First, I had the same
problem as reported in this [1] post; then I tried to build l4linux
from the latest snapshot as suggested in [2] by following the steps
in the readme file ('make setup' and 'make').
If I setup the target as x86-32, at some point the build process
fails with the following output (without further description of the
error):
"
make[6]: Leaving directory
`/local/l4re-snap/l4re-snapshot-2010111519/src/l4/pkg/valgrind/build'
make[5]: Leaving directory
`/local/l4re-snap/l4re-snapshot-2010111519/src/l4/pkg/valgrind'
make[4]: Leaving directory
`/local/l4re-snap/l4re-snapshot-2010111519/src/l4/pkg'
make[3]: *** [pkg] Error 2
make[3]: Leaving directory
`/local/l4re-snap/l4re-snapshot-2010111519/src/l4'
make[2]: *** [x] Error 2
make[2]: Leaving directory
`/local/l4re-snap/l4re-snapshot-2010111519/obj/l4/x86'
Error building the L4Re 'obj/l4/x86' variant.
"
Probably due to the parallel build the error message is (far) above
the
text you pasted. Can you give more text? Looks for '***' in the
output.
If I setup to the amd64 target, the build process fails with a
compilation error:
"
/tmp/camlasm564f4e.s: Assembler messages:
/tmp/camlasm564f4e.s:580: Error: junk `lazy_force(%rip)' after
expression
/tmp/camlasm564f4e.s:580: Error: suffix or operands invalid for `lea'
/tmp/camlasm564f4e.s:785: Error: junk `lazy_force(%rip)' after
expression
/tmp/camlasm564f4e.s:785: Error: suffix or operands invalid for `lea'
Assembler error, input left in file /tmp/camlasm564f4e.s
make[8]: *** [stream.cmx] Error 2
...
make[4]: Leaving directory
`/local/l4re-snap/l4re-snapshot-2010111519/src/l4/pkg'
make[3]: *** [pkg] Error 2
make[3]: Leaving directory
`/local/l4re-snap/l4re-snapshot-2010111519/src/l4'
make[2]: *** [x] Error 2
make[2]: Leaving directory
`/local/l4re-snap/l4re-snapshot-2010111519/obj/l4/amd64'
Error building the L4Re 'obj/l4/amd64' variant.
"
The problematic assembly instruction is:
leaq$25lazy_force(%rip), %rax
Hmm, this is ocaml stuff, where I basically can just say: Compiles for
me. A 'touch src/l4/pkg/ocaml/broken src/l4/pkg/ocaml_toys/broken'
might
help you to get through the compile.
BTW, there's no L4Linux for amd64.
I'm using the snapshot from Nov 15th, on a machine running linux
2.6.32, gcc 4.3.2.
Which Distro, btw?
Adam
--
Adam [email protected]
Lackorzynski http://os.inf.tu-dresden.de/~adam/
___
l4-hackers mailing list
[email protected]
http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
___
l4-hackers mailing list
[email protected]
http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
Re: Problem with building L4Linux
Hi,
On Tue Dec 07, 2010 at 09:24:52 +0100, Nuno Santos wrote:
> I'm having trouble with building l4linux. First, I had the same
> problem as reported in this [1] post; then I tried to build l4linux
> from the latest snapshot as suggested in [2] by following the steps
> in the readme file ('make setup' and 'make').
>
> If I setup the target as x86-32, at some point the build process
> fails with the following output (without further description of the
> error):
>
> "
> make[6]: Leaving directory
> `/local/l4re-snap/l4re-snapshot-2010111519/src/l4/pkg/valgrind/build'
> make[5]: Leaving directory
> `/local/l4re-snap/l4re-snapshot-2010111519/src/l4/pkg/valgrind'
> make[4]: Leaving directory
> `/local/l4re-snap/l4re-snapshot-2010111519/src/l4/pkg'
> make[3]: *** [pkg] Error 2
> make[3]: Leaving directory
> `/local/l4re-snap/l4re-snapshot-2010111519/src/l4'
> make[2]: *** [x] Error 2
> make[2]: Leaving directory
> `/local/l4re-snap/l4re-snapshot-2010111519/obj/l4/x86'
> Error building the L4Re 'obj/l4/x86' variant.
> "
Probably due to the parallel build the error message is (far) above the
text you pasted. Can you give more text? Looks for '***' in the output.
> If I setup to the amd64 target, the build process fails with a
> compilation error:
>
> "
> /tmp/camlasm564f4e.s: Assembler messages:
> /tmp/camlasm564f4e.s:580: Error: junk `lazy_force(%rip)' after expression
> /tmp/camlasm564f4e.s:580: Error: suffix or operands invalid for `lea'
> /tmp/camlasm564f4e.s:785: Error: junk `lazy_force(%rip)' after expression
> /tmp/camlasm564f4e.s:785: Error: suffix or operands invalid for `lea'
> Assembler error, input left in file /tmp/camlasm564f4e.s
> make[8]: *** [stream.cmx] Error 2
> ...
> make[4]: Leaving directory
> `/local/l4re-snap/l4re-snapshot-2010111519/src/l4/pkg'
> make[3]: *** [pkg] Error 2
> make[3]: Leaving directory
> `/local/l4re-snap/l4re-snapshot-2010111519/src/l4'
> make[2]: *** [x] Error 2
> make[2]: Leaving directory
> `/local/l4re-snap/l4re-snapshot-2010111519/obj/l4/amd64'
> Error building the L4Re 'obj/l4/amd64' variant.
> "
>
> The problematic assembly instruction is:
> leaq$25lazy_force(%rip), %rax
Hmm, this is ocaml stuff, where I basically can just say: Compiles for
me. A 'touch src/l4/pkg/ocaml/broken src/l4/pkg/ocaml_toys/broken' might
help you to get through the compile.
BTW, there's no L4Linux for amd64.
> I'm using the snapshot from Nov 15th, on a machine running linux
> 2.6.32, gcc 4.3.2.
Which Distro, btw?
Adam
--
Adam [email protected]
Lackorzynski http://os.inf.tu-dresden.de/~adam/
___
l4-hackers mailing list
[email protected]
http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
Problem with building L4Linux
Hi
I'm having trouble with building l4linux. First, I had the same problem
as reported in this [1] post; then I tried to build l4linux from the
latest snapshot as suggested in [2] by following the steps in the readme
file ('make setup' and 'make').
If I setup the target as x86-32, at some point the build process fails
with the following output (without further description of the error):
"
make[6]: Leaving directory
`/local/l4re-snap/l4re-snapshot-2010111519/src/l4/pkg/valgrind/build'
make[5]: Leaving directory
`/local/l4re-snap/l4re-snapshot-2010111519/src/l4/pkg/valgrind'
make[4]: Leaving directory
`/local/l4re-snap/l4re-snapshot-2010111519/src/l4/pkg'
make[3]: *** [pkg] Error 2
make[3]: Leaving directory
`/local/l4re-snap/l4re-snapshot-2010111519/src/l4'
make[2]: *** [x] Error 2
make[2]: Leaving directory
`/local/l4re-snap/l4re-snapshot-2010111519/obj/l4/x86'
Error building the L4Re 'obj/l4/x86' variant.
"
If I setup to the amd64 target, the build process fails with a
compilation error:
"
/tmp/camlasm564f4e.s: Assembler messages:
/tmp/camlasm564f4e.s:580: Error: junk `lazy_force(%rip)' after expression
/tmp/camlasm564f4e.s:580: Error: suffix or operands invalid for `lea'
/tmp/camlasm564f4e.s:785: Error: junk `lazy_force(%rip)' after expression
/tmp/camlasm564f4e.s:785: Error: suffix or operands invalid for `lea'
Assembler error, input left in file /tmp/camlasm564f4e.s
make[8]: *** [stream.cmx] Error 2
...
make[4]: Leaving directory
`/local/l4re-snap/l4re-snapshot-2010111519/src/l4/pkg'
make[3]: *** [pkg] Error 2
make[3]: Leaving directory
`/local/l4re-snap/l4re-snapshot-2010111519/src/l4'
make[2]: *** [x] Error 2
make[2]: Leaving directory
`/local/l4re-snap/l4re-snapshot-2010111519/obj/l4/amd64'
Error building the L4Re 'obj/l4/amd64' variant.
"
The problematic assembly instruction is:
leaq$25lazy_force(%rip), %rax
I'm using the snapshot from Nov 15th, on a machine running linux 2.6.32,
gcc 4.3.2.
Any ideas on how to fix it?
Thanks for your help!
--Nuno
[1]
http://www.mail-archive.com/[email protected]/msg04380.html
[2]
http://www.mail-archive.com/[email protected]/msg04383.html
___
l4-hackers mailing list
[email protected]
http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
Re: Building L4linux
On Wed Nov 10, 2010 at 22:01:32 +0100, Adam Lackorzynski wrote: > You boot your Linux installation from your disk. For that to work, > several things need to be done: > - L4Linux needs to have access to your disk, more precise, needs access >to the (SATA) disk controller. > - You need some graphics system so that L4Linux can start X so that the >xterm can run. > > For the first point I've added some description in the wiki > (http://wiki.tudos.org/L4Linux/configurations). The second point will > follow. The snapshot and the svn contain an appropriate example now which starts a Linux in graphics mode. The Linux has access to all the disk and network controllers in the system. To get X running, use the fbdev X driver. Adam -- Adam [email protected] Lackorzynski http://os.inf.tu-dresden.de/~adam/ ___ l4-hackers mailing list [email protected] http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
Re: Building L4linux
On Tue Nov 09, 2010 at 17:17:52 +0100, Maxime Lastera wrote: > Which modules I need to add to modules.list file to use xterm on l4linux? You boot your Linux installation from your disk. For that to work, several things need to be done: - L4Linux needs to have access to your disk, more precise, needs access to the (SATA) disk controller. - You need some graphics system so that L4Linux can start X so that the xterm can run. For the first point I've added some description in the wiki (http://wiki.tudos.org/L4Linux/configurations). The second point will follow. Adam -- Adam [email protected] Lackorzynski http://os.inf.tu-dresden.de/~adam/ ___ l4-hackers mailing list [email protected] http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
Building L4linux
Thank you for your help. The modules.list wasn't set correctly. So now l4linux is running. Which modules I need to add to modules.list file to use xterm on l4linux? -- Maxime LASTERA Phd Student Dependable Computing and Fault Tolerance group LAAS-CNRS 7 av Colonel Roche 31077 Toulouse E-mail: [email protected] Phone : +33561336979 ___ l4-hackers mailing list [email protected] http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
Re: Building L4linux
On Tue Nov 09, 2010 at 14:41:20 +0100, Maxime Lastera wrote: > I try without success to create .elf file with the command 'make > image E=l4linux' > > I have the following message : > > Building entry "l4linux" > Unknown entry "l4linux"! at > /home/Maxx/Downloads/l4re-snapshot/src/l4/tool/lib/L4/ModList.pm > line 168 > > > the modules.list file contains > entry l4linux x86 > modaddr 0x00200 > kernel fiasco -serial_esc > roottask moe rom/l4lx.cfg > module l4re > module ned > module l4lx.cfg > module vmlinuz > > > I think the moduless.list file isn't in the good directory but I try > l4re directory and l4linux without success neither. > > Any ideas ? Try: make image E="l4linux x86" Adam -- Adam [email protected] Lackorzynski http://os.inf.tu-dresden.de/~adam/ ___ l4-hackers mailing list [email protected] http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
Building L4linux
hi, I try without success to create .elf file with the command 'make image E=l4linux' I have the following message : Building entry "l4linux" Unknown entry "l4linux"! at /home/Maxx/Downloads/l4re-snapshot/src/l4/tool/lib/L4/ModList.pm line 168 the modules.list file contains entry l4linux x86 modaddr 0x00200 kernel fiasco -serial_esc roottask moe rom/l4lx.cfg module l4re module ned module l4lx.cfg module vmlinuz I think the moduless.list file isn't in the good directory but I try l4re directory and l4linux without success neither. Any ideas ? -- Maxime LASTERA Phd Student Dependable Computing and Fault Tolerance group LAAS-CNRS 7 av Colonel Roche 31077 Toulouse E-mail: [email protected] Phone : +33561336979 ___ l4-hackers mailing list [email protected] http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
Re: Building L4linux
On Sun Nov 07, 2010 at 15:08:25 -0500, Rahul Ramasubramanian wrote: > Now after the build , i have a bootstrap_L4Linux_ARM.elf file.Can i run this > on the realview board using the boot monitor command run or is there > anything else which needs to be done ? Yes, you can run the image using the boot monitor. Adam -- Adam [email protected] Lackorzynski http://os.inf.tu-dresden.de/~adam/ ___ l4-hackers mailing list [email protected] http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
Re: Building L4linux
hi adam thanks for the reply.. i resolved the issue... i had missed a option in menuconfig. Now after the build , i have a bootstrap_L4Linux_ARM.elf file.Can i run this on the realview board using the boot monitor command run or is there anything else which needs to be done ? thanks rahul On Sun, Nov 7, 2010 at 10:18 AM, Adam Lackorzynski < [email protected]> wrote: > Hi, > > On Fri Nov 05, 2010 at 16:52:34 +0100, Maxime Lastera wrote: > > I have built succefully L4linux. I have used the snapshot version. > > So now I want to run it, but I don't have tftboot directory in l4linux > tree. > > I can't follow the example because I don't have many modules like > > names l4io > > Admittedly the website documentation is not up to date for L4Re. Need to > fix that. > > > a vmlinuz file is in l4linux tree. > > > > what are the steps to boot on L4linux from harddrive ? > > First, try the setup in QEmu (or similar). This is much more convenient > than rebooting the host system, esp. if you do not have a separate > test-machine and a serial link. > The snapshot contains a L4Linux-setup, although for ARM. The config > script works for both architecture, just change to modules accordingly > in the modules.list file. For the io-config file, just remove it for the > beginning. Then, go the l4re build directory and do "make image E=l4linux". > So will generate you an ELF image in the images directory which you can > boot with "qemu -kernel bootstrap.elf -m 256 -serial stdio" and later on > also with e.g. GRUB. > > > > Adam > -- > Adam [email protected] > Lackorzynski http://os.inf.tu-dresden.de/~adam/ > > ___ > l4-hackers mailing list > [email protected] > http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers > ___ l4-hackers mailing list [email protected] http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
Re: Building L4linux
Hi, On Fri Nov 05, 2010 at 16:52:34 +0100, Maxime Lastera wrote: > I have built succefully L4linux. I have used the snapshot version. > So now I want to run it, but I don't have tftboot directory in l4linux tree. > I can't follow the example because I don't have many modules like > names l4io Admittedly the website documentation is not up to date for L4Re. Need to fix that. > a vmlinuz file is in l4linux tree. > > what are the steps to boot on L4linux from harddrive ? First, try the setup in QEmu (or similar). This is much more convenient than rebooting the host system, esp. if you do not have a separate test-machine and a serial link. The snapshot contains a L4Linux-setup, although for ARM. The config script works for both architecture, just change to modules accordingly in the modules.list file. For the io-config file, just remove it for the beginning. Then, go the l4re build directory and do "make image E=l4linux". So will generate you an ELF image in the images directory which you can boot with "qemu -kernel bootstrap.elf -m 256 -serial stdio" and later on also with e.g. GRUB. Adam -- Adam [email protected] Lackorzynski http://os.inf.tu-dresden.de/~adam/ ___ l4-hackers mailing list [email protected] http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
Building L4linux
Hi, I have built succefully L4linux. I have used the snapshot version. So now I want to run it, but I don't have tftboot directory in l4linux tree. I can't follow the example because I don't have many modules like names l4io a vmlinuz file is in l4linux tree. what are the steps to boot on L4linux from harddrive ? -- Maxime LASTERA Phd Student Dependable Computing and Fault Tolerance group LAAS-CNRS 7 av Colonel Roche 31077 Toulouse E-mail: [email protected] Phone : +33561336979 ___ l4-hackers mailing list [email protected] http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
Building L4linux
Hi, A 'make' in /home/Maxx/Downloads/l4re/src/l4/mybuild come with successful end. In the directory /home/Maxx/Downloads/l4re/src/l4/mybuild/pc/ there are stdlibs.pc libio.pc l4re_c-util.pc and many more. -- Maxime LASTERA Phd Student Dependable Computing and Fault Tolerance group LAAS-CNRS 7 av Colonel Roche 31077 Toulouse E-mail: [email protected] Phone : +33561336979 ___ l4-hackers mailing list [email protected] http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
Re: Building L4linux
Hi, On Thu Nov 04, 2010 at 11:32:20 +0100, Maxime Lastera wrote: > The result of make in l4linux directory is : > > Getting required compilation flags failed. > L4OBJ: /home/Maxx/Downloads/l4re/src/l4/mybuild > L4_REQUIRED_MODS: stdlibs log l4re_c-util libio shmc rtc > /home/Maxx/Downloads/l4linux/arch/l4/Makefile:287: *** Aborting.. Stop. > > I understand these packages are not found, but when I check manually > they are in L4tree directory, more precisely in > l4re/src/l4/mybuild/pkg Did a 'make' in /home/Maxx/Downloads/l4re/src/l4/mybuild come to a successful end? Are there files like /home/Maxx/Downloads/l4re/src/l4/mybuild/pc/stdlibs.pc etc? Adam -- Adam [email protected] Lackorzynski http://os.inf.tu-dresden.de/~adam/ ___ l4-hackers mailing list [email protected] http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
Building L4linux
Hi, The result of make in l4linux directory is : Getting required compilation flags failed. L4OBJ: /home/Maxx/Downloads/l4re/src/l4/mybuild L4_REQUIRED_MODS: stdlibs log l4re_c-util libio shmc rtc /home/Maxx/Downloads/l4linux/arch/l4/Makefile:287: *** Aborting.. Stop. I understand these packages are not found, but when I check manually they are in L4tree directory, more precisely in l4re/src/l4/mybuild/pkg -- Maxime LASTERA Phd Student Dependable Computing and Fault Tolerance group LAAS-CNRS 7 av Colonel Roche 31077 Toulouse E-mail: [email protected] Phone : +33561336979 ___ l4-hackers mailing list [email protected] http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
Re: Building L4linux
On Wed Nov 03, 2010 at 16:36:05 +0100, Maxime Lastera wrote: > When I set the L4 source directory to L4re build directory it's > works, but some required L4 modules are required Yes, the build directory is the right one. > stdlibs log l4re_c-util libio shmc rtc. > > > I have found this modules in the l4re-snapshot/src/l4/pkg but there > are not found by the program. > > > > I need to copy the modules in an other directory ? No. That is supposed to work automatically. Could you please copy'n'paste the error message? Adam -- Adam [email protected] Lackorzynski http://os.inf.tu-dresden.de/~adam/ ___ l4-hackers mailing list [email protected] http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
Building L4linux
When I set the L4 source directory to L4re build directory it's works, but some required L4 modules are required stdlibs log l4re_c-util libio shmc rtc. I have found this modules in the l4re-snapshot/src/l4/pkg but there are not found by the program. I need to copy the modules in an other directory ? -- Maxime LASTERA Phd Student Dependable Computing and Fault Tolerance group LAAS-CNRS 7 av Colonel Roche 31077 Toulouse E-mail: [email protected] Phone : +33561336979 ___ l4-hackers mailing list [email protected] http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
Building L4linux
Hi, I have compiled fiasco and L4re with success. The Hello World exemple is running using qemu. Now I want to try L4linux on top of fiasco. When I try to comiple L4linux the following error occur: "cannot determine L4 source directory" The L4 source directory is the directory where I have built L4re or is a reference to an other directory ? -- Maxime LASTERA Phd Student ___ l4-hackers mailing list [email protected] http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
Re: Problem with Building L4Linux-2.6
Hi Adam, On Thu Dec 04, 2008 at 14:34:57 +0800, Adam Chang wrote: >I'm trying to build L4Linux ,so I followed the tutorial on this > website http://os.inf.tu-dresden.de/L4/LinuxOnL4/build-2.6.shtml >but I have encountered some difficulties. > >First I got Fiasco, L4Env, L4Linux from SVN, and the following is > the steps that I tried to build L4Linux: >1. make -C l4 O=/my-user-build-dir oldconfig >2. make -C l4 O=/my-user-build-dir config >unset Compilers and Tools ---> Build doc directories >3. cd l4 >make O=/my-user-build-dir >4. Compile Fiasco >5. Go to the l4linux-2.6 directory >make menuconfig >set L4 tree build directory >unset some features like SMP, HPET, highmem, MTRR, MCE, > PARAVIRT, KEXEC, APM, HUGETLBFS >6. make >Then the following is a error message > >ERROR: CONFIG_VM86 must not be enabled. > > But I check the file in l4linux-2.6 directory ./arch/l4/Kconfig, > CONFIG_VM86 must be enabled, but the error message said that must be > enabled, so I was confused. Why does the Kconfig say it must be enabled? Its just enabled by default, please disable it. It's in the "Processor type and features" menu, and should be visible when the EMBEDDED option is on. If you take one of the default configs this should work atomatically, e.g. with make x86-native_defconfig. > > //pkg/uclibc++/lib/uclibc++/ARCH-all/include/associative_base:321: > error: declaration of 'typedef class > std::_associative_citer > std::_associative_iter Allocator>::_associative_citer' > > //pkg/uclibc++/lib/uclibc++/ARCH-all/include/associative_base:248: > error: changes meaning of '_associative_citer' from 'class > std::_associative_citer' > > I comment typedef _associative_citer Allocator> _associative_citer; at associative_base:321, and replace > _associative_citer by _associative_citer Allocator>. >I continued building, and there is some message: Yep, fixed. Adam -- Adam [EMAIL PROTECTED] Lackorzynski http://os.inf.tu-dresden.de/~adam/ ___ l4-hackers mailing list [email protected] http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
Problem with Building L4Linux-2.6
Dear all: I'm trying to build L4Linux ,so I followed the tutorial on this website http://os.inf.tu-dresden.de/L4/LinuxOnL4/build-2.6.shtml but I have encountered some difficulties. First I got Fiasco, L4Env, L4Linux from SVN, and the following is the steps that I tried to build L4Linux: 1. make -C l4 O=/my-user-build-dir oldconfig 2. make -C l4 O=/my-user-build-dir config unset Compilers and Tools ---> Build doc directories 3. cd l4 make O=/my-user-build-dir 4. Compile Fiasco 5. Go to the l4linux-2.6 directory make menuconfig set L4 tree build directory unset some features like SMP, HPET, highmem, MTRR, MCE, PARAVIRT, KEXEC, APM, HUGETLBFS 6. make Then the following is a error message ERROR: CONFIG_VM86 must not be enabled. But I check the file in l4linux-2.6 directory ./arch/l4/Kconfig, CONFIG_VM86 must be enabled, but the error message said that must be enabled, so I was confused. Then ,I got Fiasco, L4Env, L4Linux from snapshot , http://os.inf.tu-dresden.de/opentc/download.xml then I followed same steps to build, when I did "make O=/my-user-build-dir", there is a error message: //pkg/uclibc++/lib/uclibc++/ARCH-all/include/associative_base:321: error: declaration of 'typedef class std::_associative_citer std::_associative_iter::_associative_citer' //pkg/uclibc++/lib/uclibc++/ARCH-all/include/associative_base:248: error: changes meaning of '_associative_citer' from 'class std::_associative_citer' I comment typedef _associative_citer _associative_citer; at associative_base:321, and replace _associative_citer by _associative_citer. I continued building, and there is some message: Package dependencies missing: l4con, skipping. Package dependencies missing: dope, skippingg. Compiling L4Linux , unset SMP, HPET, highmem, MTRR, MCE, PARAVIRT, KEXEC, APM, HUGETLBFS , L4_FBDRIVER, but there is still a error message: make[1]: *** No rule to make target `arch/l4/power/arch-i386/../../../i386/power/suspend.o', needed by `arch/l4/power/arch-i386/suspend.o'. Stop. make: *** [arch/l4/power/arch-i386] Error I don't know how to solve these problem, can someone give me some advice about building L4Linux. Thanks!! Best Regards. Adam Chang -- Adam Hung-Hsiang Chang [EMAIL PROTECTED] +886-987-335398 Wireless Networking and Embedded Systems Lab Graduate Institute of Networking and Multimedia National Taiwan University ___ l4-hackers mailing list [email protected] http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
Re: building l4linux
On Sun Jul 15, 2007 at 19:32:47 +0800, kashin Lin wrote: > 2007/7/15, Adam Lackorzynski <[EMAIL PROTECTED]>: > > > > > >On Sat Jul 14, 2007 at 19:03:41 +0800, kashin Lin wrote: > >> 2007/7/14, Adam Lackorzynski <[EMAIL PROTECTED]>: > >> > > >> >Hi, > >> > > >> >On Sat Jul 14, 2007 at 01:17:36 +0800, kashin Lin wrote: > > > my building sequence is : > == > in l4_all/kernel/fiasco > 1. make BUILDDIR=../../build/fiasco > > in l4_all/build/fiasco > 2. make menuconfig > > in l4_all/l4 > 3. make config O=../build/l4env > 4. make O=../build/l4env > == This order is fine > > > >> >> > >> >> my questions : > >> >> 1. when i issue make in l4/ to build the L4 userland, does it > >automatic > >> >build fiasco subsequently¡H > >> >> > >> >> 2. if yes, is its default output path for fiasco > >> >l4_all/kernel/fiasco/build? > >> > > >> >Yes, a default configuration is built into kernel/fiasco/build upon > >make > >> >in the l4 directory if not configured otherwise (see the L4 > >> >configuration menu). > >> > > >> >> ( after the operations mentioned above, i find there are some new > >files > >> >in > >> >> l4_all/kernel/fiasco/build ) > >> >> but my configuration for fiasco is in l4_all/build/fiasco, is this > >auto > >> >> build operation based on my config? > >> > > >> >No, it's a default build. > >> > > >> >> or i should set BUILDDIR to l4_all/kernel/fiasco/build? > >> > > >> >No. The way you build the kernel is fine. > >> > >> > >> but the default build isn't base on my configuration (i enable 'Handle > >and > >> preserve segments'). > > > >No. > > > >> if i don't set BUILDDIR to l4_all/kernel/fiasco/build. how does default > >> build know > >> how i config fiasco? > > > >Not at all. The configuration used for the kernel/fiasco/build is just a > >plain default standard configuration. It has nothing to do with your > >specific configuration. > > > >last time, you mentioned that : > >> "Yes, a default configuration is built into kernel/fiasco/build upon > >make > >> in the l4 directory if not configured otherwise (see the L4 > >> configuration menu)." > >> but i can't find any option in L4 configuration menu which is about > >fiasco? > > > >It's the 'Do not build anything outside l4 directory' option in the > >'Advanced' menu. > > > according to my building sequence metioned above, > if i want to build fiasco in the place i assigned ( > BUILDDIR=../../build/fiasco ) and > based on my config, i should go to l4_all/build/fiasco, and issue "make" > again? Yes, this is ok. > if yes, does it also mean the order of build l4env and fiasco is at our own > choise? > (build l4env first and then fiasco or build fiasco first then l4env) Yes, the order does not matter. Adam -- Adam [EMAIL PROTECTED] Lackorzynski http://os.inf.tu-dresden.de/~adam/ ___ l4-hackers mailing list [email protected] http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
Re: building l4linux
2007/7/15, Adam Lackorzynski <[EMAIL PROTECTED]>: On Sat Jul 14, 2007 at 19:03:41 +0800, kashin Lin wrote: > 2007/7/14, Adam Lackorzynski <[EMAIL PROTECTED]>: > > > >Hi, > > > >On Sat Jul 14, 2007 at 01:17:36 +0800, kashin Lin wrote: my building sequence is : == in l4_all/kernel/fiasco 1. make BUILDDIR=../../build/fiasco in l4_all/build/fiasco 2. make menuconfig in l4_all/l4 3. make config O=../build/l4env 4. make O=../build/l4env == > >> > >> my questions : > >> 1. when i issue make in l4/ to build the L4 userland, does it automatic > >build fiasco subsequently¡H > >> > >> 2. if yes, is its default output path for fiasco > >l4_all/kernel/fiasco/build? > > > >Yes, a default configuration is built into kernel/fiasco/build upon make > >in the l4 directory if not configured otherwise (see the L4 > >configuration menu). > > > >> ( after the operations mentioned above, i find there are some new files > >in > >> l4_all/kernel/fiasco/build ) > >> but my configuration for fiasco is in l4_all/build/fiasco, is this auto > >> build operation based on my config? > > > >No, it's a default build. > > > >> or i should set BUILDDIR to l4_all/kernel/fiasco/build? > > > >No. The way you build the kernel is fine. > > > but the default build isn't base on my configuration (i enable 'Handle and > preserve segments'). No. > if i don't set BUILDDIR to l4_all/kernel/fiasco/build. how does default > build know > how i config fiasco? Not at all. The configuration used for the kernel/fiasco/build is just a plain default standard configuration. It has nothing to do with your specific configuration. last time, you mentioned that : > "Yes, a default configuration is built into kernel/fiasco/build upon make > in the l4 directory if not configured otherwise (see the L4 > configuration menu)." > but i can't find any option in L4 configuration menu which is about fiasco? It's the 'Do not build anything outside l4 directory' option in the 'Advanced' menu. according to my building sequence metioned above, if i want to build fiasco in the place i assigned ( BUILDDIR=../../build/fiasco ) and based on my config, i should go to l4_all/build/fiasco, and issue "make" again? if yes, does it also mean the order of build l4env and fiasco is at our own choise? (build l4env first and then fiasco or build fiasco first then l4env) thanks for answering. Adam -- Adam [EMAIL PROTECTED] Lackorzynski http://os.inf.tu-dresden.de/~adam/ ___ l4-hackers mailing list [email protected] http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers ___ l4-hackers mailing list [email protected] http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
Re: building l4linux
On Sat Jul 14, 2007 at 19:03:41 +0800, kashin Lin wrote: > 2007/7/14, Adam Lackorzynski <[EMAIL PROTECTED]>: > > > >Hi, > > > >On Sat Jul 14, 2007 at 01:17:36 +0800, kashin Lin wrote: > >> my building sequence is : > >> == > >> in l4_all/kernel/fiasco > >> 1. make BUILDDIR=../../build/fiasco > >> > >> in l4_all/build/fiasco > >> 2. make menuconfig > >> > >> in l4_all/l4 > >> 3. make config O=../build/l4env > >> 4. make O=../build/l4env > >> == > >> > >> my questions : > >> 1. when i issue make in l4/ to build the L4 userland, does it automatic > >build fiasco subsequently¡H > >> > >> 2. if yes, is its default output path for fiasco > >l4_all/kernel/fiasco/build? > > > >Yes, a default configuration is built into kernel/fiasco/build upon make > >in the l4 directory if not configured otherwise (see the L4 > >configuration menu). > > > >> ( after the operations mentioned above, i find there are some new files > >in > >> l4_all/kernel/fiasco/build ) > >> but my configuration for fiasco is in l4_all/build/fiasco, is this auto > >> build operation based on my config? > > > >No, it's a default build. > > > >> or i should set BUILDDIR to l4_all/kernel/fiasco/build? > > > >No. The way you build the kernel is fine. > > > but the default build isn't base on my configuration (i enable 'Handle and > preserve segments'). No. > if i don't set BUILDDIR to l4_all/kernel/fiasco/build. how does default > build know > how i config fiasco? Not at all. The configuration used for the kernel/fiasco/build is just a plain default standard configuration. It has nothing to do with your specific configuration. > last time, you mentioned that : > "Yes, a default configuration is built into kernel/fiasco/build upon make > in the l4 directory if not configured otherwise (see the L4 > configuration menu)." > but i can't find any option in L4 configuration menu which is about fiasco? It's the 'Do not build anything outside l4 directory' option in the 'Advanced' menu. Adam -- Adam [EMAIL PROTECTED] Lackorzynski http://os.inf.tu-dresden.de/~adam/ ___ l4-hackers mailing list [email protected] http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
Re: building l4linux
2007/7/14, Adam Lackorzynski <[EMAIL PROTECTED]>: Hi, On Sat Jul 14, 2007 at 01:17:36 +0800, kashin Lin wrote: > my building sequence is : > == > in l4_all/kernel/fiasco > 1. make BUILDDIR=../../build/fiasco > > in l4_all/build/fiasco > 2. make menuconfig > > in l4_all/l4 > 3. make config O=../build/l4env > 4. make O=../build/l4env > == > > my questions : > 1. when i issue make in l4/ to build the L4 userland, does it automatic build fiasco subsequently¡H > > 2. if yes, is its default output path for fiasco l4_all/kernel/fiasco/build? Yes, a default configuration is built into kernel/fiasco/build upon make in the l4 directory if not configured otherwise (see the L4 configuration menu). > ( after the operations mentioned above, i find there are some new files in > l4_all/kernel/fiasco/build ) > but my configuration for fiasco is in l4_all/build/fiasco, is this auto > build operation based on my config? No, it's a default build. > or i should set BUILDDIR to l4_all/kernel/fiasco/build? No. The way you build the kernel is fine. but the default build isn't base on my configuration (i enable 'Handle and preserve segments'). if i don't set BUILDDIR to l4_all/kernel/fiasco/build. how does default build know how i config fiasco? last time, you mentioned that : "Yes, a default configuration is built into kernel/fiasco/build upon make in the l4 directory if not configured otherwise (see the L4 configuration menu)." but i can't find any option in L4 configuration menu which is about fiasco? thanks for answering. when config l4linux: > according to http://os.inf.tu-dresden.de/L4/LinuxOnL4/build-2.6.shtml, > there are some options we shouldn't enable > ex: like ACPI, SMP, preemption, apic/ioapic, HPET, highmem, MTRR, MCE, > power management and similar. > > 1. does those options are default unable? or we should unable manually? > 2. what does "similar" mean? With this statement I'm trying to express that for L4Linux one should _not_ enable any option that is close to the hardware, such as ACPI, HPET, MTRR etc. Remember, L4Linux is a normal user program and as such has no business doing anything with timer hardware or interrupt controller or similar. On the other side, you can enable e.g. any filesystem you like. Adam -- Adam [EMAIL PROTECTED] Lackorzynski http://os.inf.tu-dresden.de/~adam/ ___ l4-hackers mailing list [email protected] http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers ___ l4-hackers mailing list [email protected] http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
Re: building l4linux
Hi, On Sat Jul 14, 2007 at 01:17:36 +0800, kashin Lin wrote: > my building sequence is : > == > in l4_all/kernel/fiasco > 1. make BUILDDIR=../../build/fiasco > > in l4_all/build/fiasco > 2. make menuconfig > > in l4_all/l4 > 3. make config O=../build/l4env > 4. make O=../build/l4env > == > > my questions : > 1. when i issue make in l4/ to build the L4 userland, does it automatic > build fiasco subsequently¡H > > 2. if yes, is its default output path for fiasco l4_all/kernel/fiasco/build? Yes, a default configuration is built into kernel/fiasco/build upon make in the l4 directory if not configured otherwise (see the L4 configuration menu). > ( after the operations mentioned above, i find there are some new files in > l4_all/kernel/fiasco/build ) > but my configuration for fiasco is in l4_all/build/fiasco, is this auto > build operation based on my config? No, it's a default build. > or i should set BUILDDIR to l4_all/kernel/fiasco/build? No. The way you build the kernel is fine. > when config l4linux: > according to http://os.inf.tu-dresden.de/L4/LinuxOnL4/build-2.6.shtml, > there are some options we shouldn't enable > ex: like ACPI, SMP, preemption, apic/ioapic, HPET, highmem, MTRR, MCE, > power management and similar. > > 1. does those options are default unable? or we should unable manually? > 2. what does "similar" mean? With this statement I'm trying to express that for L4Linux one should _not_ enable any option that is close to the hardware, such as ACPI, HPET, MTRR etc. Remember, L4Linux is a normal user program and as such has no business doing anything with timer hardware or interrupt controller or similar. On the other side, you can enable e.g. any filesystem you like. Adam -- Adam [EMAIL PROTECTED] Lackorzynski http://os.inf.tu-dresden.de/~adam/ ___ l4-hackers mailing list [email protected] http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
building l4linux
Hi~ i have some questions again. my building sequence is : == in l4_all/kernel/fiasco 1. make BUILDDIR=../../build/fiasco in l4_all/build/fiasco 2. make menuconfig in l4_all/l4 3. make config O=../build/l4env 4. make O=../build/l4env == my questions : 1. when i issue make in l4/ to build the L4 userland, does it automatic build fiasco subsequently？ 2. if yes, is its default output path for fiasco l4_all/kernel/fiasco/build? ( after the operations mentioned above, i find there are some new files in l4_all/kernel/fiasco/build ) but my configuration for fiasco is in l4_all/build/fiasco, is this auto build operation based on my config? or i should set BUILDDIR to l4_all/kernel/fiasco/build? when config l4linux: according to http://os.inf.tu-dresden.de/L4/LinuxOnL4/build-2.6.shtml, there are some options we shouldn't enable ex: like ACPI, SMP, preemption, apic/ioapic, HPET, highmem, MTRR, MCE, power management and similar. 1. does those options are default unable? or we should unable manually? 2. what does "similar" mean? thanks for answering. ___ l4-hackers mailing list [email protected] http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
Re: Building L4Linux
On Sun Apr 08, 2007 at 22:53:20 +0200, Eduard Benes wrote:
> I run into problem compiling l4linux. I've been able to compile it many
> times before. But after few weeks while I was not with l4linux stuff,
> I run into problem when building it. I'm pretty sure it will be some
> "stupid" mistake I've made, but since I need to quickly finish some
> testing, I would really appreciate any advise...
>
> Here is configuration I use:
> Debian {sarge, etch}; gcc version: 3.{3,4}, l4linux-2.6-17
> Everything is mainly based on chenggh's kickstart and tarball he provided.
> (http://os.inf.tu-dresden.de/pipermail/l4-hackers/2007/002732.html)
Could you also show the gcc call? (make V=1)
> < l4linux make log start >
> include/asm-l4/i386-arch/asm/alternative.h:7: error: syntax error before "u8"
> include/asm-l4/i386-arch/asm/alternative.h:7: warning: no semicolon at end of
> struct or union
> include/asm-l4/i386-arch/asm/alternative.h:8: warning: type defaults to `int'
> in declaration of `replacement'
> include/asm-l4/i386-arch/asm/alternative.h:8: warning: data definition has no
> type or storage class
I guess gcc doesn't like the u8 because it doesn't know what it means.
Does it help if you add '#include ' in the beginning of
irq_multi.c? If it doesn't go away now, please also show your .config.
Adam
--
Adam [EMAIL PROTECTED]
Lackorzynski http://os.inf.tu-dresden.de/~adam/
___
l4-hackers mailing list
[email protected]
http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
Building L4Linux
Hi,
I run into problem compiling l4linux. I've been able to compile it many
times before. But after few weeks while I was not with l4linux stuff,
I run into problem when building it. I'm pretty sure it will be some
"stupid" mistake I've made, but since I need to quickly finish some
testing, I would really appreciate any advise...
Here is configuration I use:
Debian {sarge, etch}; gcc version: 3.{3,4}, l4linux-2.6-17
Everything is mainly based on chenggh's kickstart and tarball he provided.
(http://os.inf.tu-dresden.de/pipermail/l4-hackers/2007/002732.html)
< l4linux make log start >
include/asm-l4/i386-arch/asm/alternative.h:7: error: syntax error before "u8"
include/asm-l4/i386-arch/asm/alternative.h:7: warning: no semicolon at end of
struct or union
include/asm-l4/i386-arch/asm/alternative.h:8: warning: type defaults to `int'
in declaration of `replacement'
include/asm-l4/i386-arch/asm/alternative.h:8: warning: data definition has no
type or storage class
include/asm-l4/i386-arch/asm/alternative.h:9: error: syntax error before "cpuid"
include/asm-l4/i386-arch/asm/alternative.h:9: warning: type defaults to `int'
in declaration of `cpuid'
include/asm-l4/i386-arch/asm/alternative.h:9: warning: data definition has no
type or storage class
include/asm-l4/i386-arch/asm/alternative.h:10: error: syntax error before
"instrlen"
include/asm-l4/i386-arch/asm/alternative.h:10: warning: type defaults to `int'
in declaration of `instrlen'
include/asm-l4/i386-arch/asm/alternative.h:10: warning: data definition has no
type or storage class
include/asm-l4/i386-arch/asm/alternative.h:11: error: syntax error before
"replacementlen"
include/asm-l4/i386-arch/asm/alternative.h:11: warning: type defaults to `int'
in declaration of `replacementlen'
include/asm-l4/i386-arch/asm/alternative.h:11: warning: data definition has no
type or storage class
include/asm-l4/i386-arch/asm/alternative.h:12: error: syntax error before "pad"
include/asm-l4/i386-arch/asm/alternative.h:12: warning: type defaults to `int'
in declaration of `pad'
include/asm-l4/i386-arch/asm/alternative.h:12: warning: data definition has no
type or storage class
In file included from include/asm-l4/i386-arch/asm/thread_info.h:17,
from include/linux/thread_info.h:21,
from include/linux/preempt.h:10,
from include/linux/interrupt.h:9,
from arch/l4/l4lxlib/l4env/irq_multi.c:12:
include/asm-l4/l4-arch/asm/processor.h:154: error: `cpuid' redeclared as
different kind of symbol
include/asm-l4/i386-arch/asm/alternative.h:9: error: previous declaration of
`cpuid'
include/asm-l4/l4-arch/asm/processor.h:154: warning: `cpuid' was declared
`extern' and later `static'
make[1]: *** [arch/l4/l4lxlib/l4env/irq_multi.o] Error 1
make: *** [arch/l4/l4lxlib/l4env] Error 2
< l4linux make log end >
Thank you,
Eduard Benes
___
l4-hackers mailing list
[email protected]
http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
Re: Error in building l4linux-2.6-env
On Tue Jul 12, 2005 at 10:56:48 -0600, Wang, Chip wrote: > I did not intentionally checkout dde. It just came with > l4linux-2.6-env. I think it was part of the module. If it is not > required to build l4linux-2.6 maybe you would want to separate it from > the module? I'm quite sure that dde is not part of the l4linux-2.6-env CVS module. > By the way, how can I receive CVS commit notifications via email, or > is it even possible? No, that's not possible. Adam -- Adam [EMAIL PROTECTED] Lackorzynski http://os.inf.tu-dresden.de/~adam/ ___ l4-hackers mailing list [email protected] http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
RE: Error in building l4linux-2.6-env
Hi Adam, I did not intentionally checkout dde. It just came with l4linux-2.6-env. I think it was part of the module. If it is not required to build l4linux-2.6 maybe you would want to separate it from the module? By the way, how can I receive CVS commit notifications via email, or is it even possible? I am looking forward to you publishing the fix soon. Thanks, Chip -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Adam Lackorzynski Sent: Tuesday, July 12, 2005 10:43 AM To: [email protected] Subject: Re: Error in building l4linux-2.6-env On Tue Jul 12, 2005 at 10:09:26 -0600, Wang, Chip wrote: > After skipped building fprov-l4 and kill-l4 in l4/pkg/loader/examples, > I managed to get a little further. > This time my make failed at l4/pkg/dde for conflicting function > prototypes. It appears the make was using Linux 2.4 header files while > building for 2.6 This is actually correct as dde_linux is for Linux2.4. The compiler error appears with more recent compiler versions, and I have now finally fixed it internally. Should be in our public CVS by tomorrow. On the other side, how did it come that you checked out dde? You don't need it to get L4Linux going. Adam -- Adam [EMAIL PROTECTED] Lackorzynski http://os.inf.tu-dresden.de/~adam/ ___ l4-hackers mailing list [email protected] http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers The information contained in this e-mail message is PRIVATE. It may contain confidential information and may be legally privileged. It is intended for the exclusive use of the addressee(s). If you are not the intended recipient, you are hereby notified that any dissemination, distribution or reproduction of this communication is strictly prohibited. If the intended recipient(s) cannot be reached or if a transmission problem has occurred, please notify the sender immediately by return e-mail and destroy all copies of this message. Thank you. ___ l4-hackers mailing list [email protected] http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
Re: Error in building l4linux-2.6-env
On Tue Jul 12, 2005 at 10:09:26 -0600, Wang, Chip wrote: > After skipped building fprov-l4 and kill-l4 in l4/pkg/loader/examples, > I managed to get a little further. > This time my make failed at l4/pkg/dde for conflicting function > prototypes. It appears the make was using Linux 2.4 header files while > building for 2.6 This is actually correct as dde_linux is for Linux2.4. The compiler error appears with more recent compiler versions, and I have now finally fixed it internally. Should be in our public CVS by tomorrow. On the other side, how did it come that you checked out dde? You don't need it to get L4Linux going. Adam -- Adam [EMAIL PROTECTED] Lackorzynski http://os.inf.tu-dresden.de/~adam/ ___ l4-hackers mailing list [email protected] http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
Error in building l4linux-2.6-env
Title: Error in building l4linux-2.6-env Hi, After skipped building fprov-l4 and kill-l4 in l4/pkg/loader/examples, I managed to get a little further. This time my make failed at l4/pkg/dde for conflicting function prototypes. It appears the make was using Linux 2.4 header files while building for 2.6 Does anybody have an idea of what went wrong? Chip make[5]: Entering directory `/home/drops/l4/pkg/dde_linux/lib/src/OBJ-x86_586-l4v2' ... Compiling mm.o LD_PRELOAD=/home/drops/l4/tool/gendep/libgendep.so GENDEP_TARGET=mm.o GENDEP_BINARY=cc1 gcc -c -D__KERNEL__ -DDDE_LINUX -DRAM_BASE=0x0 -DSYSTEM_x86_586_l4v2 -DARCH_x86 -DCPUTYPE_586 -DL4API_l4v2 -I../../../lib/include -I../../../../../include/x86/l4/dde_linux -I/home/drops/include/x86/l4/dde_linux -I../../../../../include/linux-24 -I/home/drops/include/linux-24 -I../../../idl/OBJ-x86-l4v2 -I../../../../../include/x86/l4v2 -I/home/drops/include/x86/l4v2 -I../../../../../include/l4v2 -I/home/drops/include/l4v2 -I../../../../../include/x86 -I/home/drops/include/x86 -I../../../../../include -I/home/drops/include -nostdinc -DOSKIT -I../../../../../../oskit10 -I../../../../../../oskit10/oskit/c -I/home/drops/include/oskit10 -I/home/drops/include/oskit10/oskit/c -I/usr/lib/gcc/i586-mandrake-linux-gnu/3.4.3/include -gstabs+ -g -O2 -fno-strict-aliasing -march=i586 -Wall -Wstrict-prototypes -fno-strict-aliasing /home/drops/l4/pkg/dde_linux/lib/src/mm.c -o mm.o In file included from ../../../../../include/linux-24/linux/bitops.h:69, from ../../../../../include/x86/l4/dde_linux/asm/system.h:10, from ../../../../../include/x86/l4/dde_linux/linux/spinlock.h:8, from ../../../../../include/linux-24/linux/wait.h:16, from ../../../../../include/linux-24/linux/fs.h:12, from ../../../../../include/linux-24/linux/capability.h:17, from ../../../../../include/linux-24/linux/binfmts.h:5, from ../../../../../include/x86/l4/dde_linux/linux/sched.h:11, from ../../../../../include/linux-24/linux/mm.h:4, from ../../../../../include/linux-24/linux/slab.h:14, from /home/drops/l4/pkg/dde_linux/lib/src/mm.c:50: ../../../../../include/linux-24/asm/bitops.h:343: warning: static declaration of 'ffs' follows non-static declaration In file included from ../../../../../include/x86/l4/dde_linux/linux/sched.h:25, from ../../../../../include/linux-24/linux/mm.h:4, from ../../../../../include/linux-24/linux/slab.h:14, from /home/drops/l4/pkg/dde_linux/lib/src/mm.c:50: ../../../../../include/linux-24/linux/smp.h:29: error: conflicting types for 'smp_send_reschedule' ../../../../../include/x86/l4/dde_linux/asm/smp.h:44: error: previous declaration of 'smp_send_reschedule' was here ../../../../../include/linux-24/linux/smp.h:29: error: conflicting types for 'smp_send_reschedule' ../../../../../include/x86/l4/dde_linux/asm/smp.h:44: error: previous declaration of 'smp_send_reschedule' was here make[5]: *** [mm.o] Error 1 make[5]: Leaving directory `/home/drops/l4/pkg/dde_linux/lib/src/OBJ-x86_586-l4v2' make[4]: *** [OBJ-x86_586-l4v2] Error 2 make[4]: Leaving directory `/home/drops/l4/pkg/dde_linux/lib/src' make[3]: *** [src] Error 2 make[3]: Leaving directory `/home/drops/l4/pkg/dde_linux/lib' make[2]: *** [lib] Error 2 make[2]: Leaving directory `/home/drops/l4/pkg/dde_linux' make[1]: *** [dde_linux.lib] Error 2 make[1]: Leaving directory `/home/drops/l4/pkg' make: *** [pkg] Error 2 The information contained in this e-mail message is PRIVATE. It may contain confidential information and may be legally privileged. It is intended for the exclusive use of the addressee(s). If you are not the intended recipient, you are hereby notified that any dissemination, distribution or reproduction of this communication is strictly prohibited. If the intended recipient(s) cannot be reached or if a transmission problem has occurred, please notify the sender immediately by return e-mail and destroy all copies of this message. Thank you. ___ l4-hackers mailing list [email protected] http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
Re: Problem building L4Linux
On Fri Oct 22, 2004 at 11:29:08 +0100, Tiago Jorge wrote: > Like i said in previous emails, im trying to boot the Fedora Core 1 that > i have in my disk with the L4 u-kernel. > I've done a classic config stuff... i went to get the Fedora kernel > config file and put it like.config in L4Linux kernel directory. I've > configured the l4 options i tried to built it. I'm trying to build the > 2.4.22 L4Linux kernel. The error that gave me it's here... > > -D__KERNEL__ -I/root/l4linux-2.4/include -Wall -Wstrict-prototypes > -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer -g > -DLINUX_ON_L4 -pipe -mpreferred-stack-boundary=2 -march=i686 -nostdinc > -iwithprefix include -DKBUILD_BASENAME=apm -c -o apm.o apm.c > apm.c: In function `apm_bios_call': > apm.c:626: warning: implicit declaration of function `loadsegment' > apm.c:626: error: `fs' undeclared (first use in this function) > apm.c:626: error: (Each undeclared identifier is reported only once > apm.c:626: error: for each function it appears in.) > apm.c:626: error: `gs' undeclared (first use in this function) > apm.c: In function `apm_bios_call_simple': > apm.c:679: error: `fs' undeclared (first use in this function) > apm.c:679: error: `gs' undeclared (first use in this function) > apm.c: In function `apm_init': > apm.c:1984: warning: implicit declaration of function `set_base' > apm.c:1984: error: `gdt' undeclared (first use in this function) > apm.c:1986: warning: implicit declaration of function `_set_limit' > make[1]: *** [apm.o] Error 1 > make[1]: Leaving directory `/root/l4linux-2.4/arch/l4/kernel' > make: *** [_dir_arch/l4/kernel] Error 2 It's simple, just do not use APM, ACPI and anything else of the low level stuff. (L4Linux is a user land application...) Adam -- Adam [EMAIL PROTECTED] Lackorzynski http://os.inf.tu-dresden.de/~adam/ ___ l4-hackers mailing list [EMAIL PROTECTED] http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
Problem building L4Linux
Like i said in previous emails, im trying to boot the Fedora Core 1 that i have in my disk with the L4 u-kernel. I've done a classic config stuff... i went to get the Fedora kernel config file and put it like.config in L4Linux kernel directory. I've configured the l4 options i tried to built it. I'm trying to build the 2.4.22 L4Linux kernel. The error that gave me it's here... -D__KERNEL__ -I/root/l4linux-2.4/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer -g -DLINUX_ON_L4 -pipe -mpreferred-stack-boundary=2 -march=i686 -nostdinc -iwithprefix include -DKBUILD_BASENAME=apm -c -o apm.o apm.c apm.c: In function `apm_bios_call': apm.c:626: warning: implicit declaration of function `loadsegment' apm.c:626: error: `fs' undeclared (first use in this function) apm.c:626: error: (Each undeclared identifier is reported only once apm.c:626: error: for each function it appears in.) apm.c:626: error: `gs' undeclared (first use in this function) apm.c: In function `apm_bios_call_simple': apm.c:679: error: `fs' undeclared (first use in this function) apm.c:679: error: `gs' undeclared (first use in this function) apm.c: In function `apm_init': apm.c:1984: warning: implicit declaration of function `set_base' apm.c:1984: error: `gdt' undeclared (first use in this function) apm.c:1986: warning: implicit declaration of function `_set_limit' make[1]: *** [apm.o] Error 1 make[1]: Leaving directory `/root/l4linux-2.4/arch/l4/kernel' make: *** [_dir_arch/l4/kernel] Error 2 Could somebody help me Thaks in advance Tiago ___ l4-hackers mailing list [EMAIL PROTECTED] http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
