Re: Building L4Linux for ARM

2011-06-15 Thread Anna Fischer
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
l4-hackers@os.inf.tu-dresden.de
http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers


Re: Building L4Linux for ARM

2011-06-15 Thread Adam Lackorzynski
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 a...@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


Re: Building L4Linux for ARM

2011-06-15 Thread Anna Fischer
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
l4-hackers@os.inf.tu-dresden.de
http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers


Re: Building L4linux

2010-11-15 Thread Adam Lackorzynski

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 a...@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


Re: Building L4linux

2010-11-10 Thread Adam Lackorzynski

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 a...@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


Re: Building L4linux

2010-11-09 Thread Adam Lackorzynski

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 a...@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


Re: Building L4linux

2010-11-07 Thread Adam Lackorzynski
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 a...@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


Re: Building L4linux

2010-11-07 Thread Rahul Ramasubramanian
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 
a...@os.inf.tu-dresden.de 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 a...@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 mailing list
l4-hackers@os.inf.tu-dresden.de
http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers


Re: Building L4linux

2010-11-07 Thread Adam Lackorzynski

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 a...@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


Re: Building L4linux

2010-11-04 Thread Adam Lackorzynski
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 a...@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


Re: building l4linux

2007-07-15 Thread Adam Lackorzynski

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
l4-hackers@os.inf.tu-dresden.de
http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers


Re: building l4linux

2007-07-15 Thread kashin Lin

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
l4-hackers@os.inf.tu-dresden.de
http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers

___
l4-hackers mailing list
l4-hackers@os.inf.tu-dresden.de
http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers


Re: building l4linux

2007-07-15 Thread Adam Lackorzynski

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
l4-hackers@os.inf.tu-dresden.de
http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers


Re: building l4linux

2007-07-14 Thread kashin Lin

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
l4-hackers@os.inf.tu-dresden.de
http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers

___
l4-hackers mailing list
l4-hackers@os.inf.tu-dresden.de
http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers


Re: building l4linux

2007-07-13 Thread Adam Lackorzynski
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
l4-hackers@os.inf.tu-dresden.de
http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers


Re: Building L4Linux

2007-04-08 Thread Adam Lackorzynski

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 linux/types.h' 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
l4-hackers@os.inf.tu-dresden.de
http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers