Could you please post the content of your `<build-dir>/etc/build.conf` file? It looks like the base-nova repository. is missing from the `REPOSITORIES` declaration.
Have you made sure that the directory you specified as argument to create_builddir did not exist beforehand? The create_builddir tool may get confused to the BUILD_DIR argument points to an already existing directory.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yes, it existed. I deleted it and after removing "make kernel" worked. But there is other problem I faced with. When I try to run "make run/demo" The message below appears.
/bin/bash: /home/mm1/Downloads/genodelabs-genode-7e0a1cc/tool/run: /usr/bin/expect: bad interpreter: No such file or directory
make: *** Error 126
What could it be?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It seems that the only microhypervisor were made. I`ve looked into the built directory and could not find any files of genode that were listed in doc files (in the part where were described the setting process of bootloader). But binary file of hypervisor were made.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks, you are right. And the last question. How to run genode-nova by using GRUB 0.97 directly on the hardware. I am interested in how to set settings of the grub.conf file. When I set i like you were written in the doc file it doesn`t work. GRUB writes me that it can not find a file. Then I decide to denote it directly path to the binary file and it writes me that file system is incorrect. Bellow you can see my grub.conf file. Please check it.
As a general remark, I would recommend you to direct your questions to the Genode mailing list. This forum is pretty deserted. The mailing list is the place to be. ;-)
Regarding your GRUB-related questions, it is hard to pinpoint the problem from remote. I have the following hints though:
* Maybe your partition 2 is formatted with the file system not supported by GRUB? (i.e., raiserfs)
* You can use the GRUB command line to interactively explore the access to files on your disk.
* When booting the system on real hardware, I'd suggest to let GRUB fetch the modules over tftp rather than from disk. This way, you won't need to reboot your test machine into Linux to update the binaries for each test run.
The second point is probably to most important. It is worthwhile to make yourself familiar with GRUB.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
After making build_dir. I try to run "make kernel" in bash in built folder, but the following message appears.
Error: target 'kernel' does not exist
make: *** Error 1
All files of NOVA hypervisor were downloaded. I saw it myself in /contrib directory.
Could you please post the content of your `<build-dir>/etc/build.conf` file? It looks like the base-nova repository. is missing from the `REPOSITORIES` declaration.
Have you made sure that the directory you specified as argument to create_builddir did not exist beforehand? The create_builddir tool may get confused to the BUILD_DIR argument points to an already existing directory.
Yes, it existed. I deleted it and after removing "make kernel" worked. But there is other problem I faced with. When I try to run "make run/demo" The message below appears.
/bin/bash: /home/mm1/Downloads/genodelabs-genode-7e0a1cc/tool/run: /usr/bin/expect: bad interpreter: No such file or directory
make: *** Error 126
What could it be?
It seems that the only microhypervisor were made. I`ve looked into the built directory and could not find any files of genode that were listed in doc files (in the part where were described the setting process of bootloader). But binary file of hypervisor were made.
ouhh and the messages ahead were written by me I forgot to log in. Waiting for your replies.
> tool/run: /usr/bin/expect: bad interpreter: No such file or directory
This message actually tells you what is wrong. ;-) The expect interpreter is missing from your system. Please install the 'expect' package.
To see the packages that Genode expects to be installed on your Linux host system, please refer to the documentation at doc/getting_started.txt. (alternatively, you can find it at http://genode.org/documentation/developer-resources/getting_started
Thanks, you are right. And the last question. How to run genode-nova by using GRUB 0.97 directly on the hardware. I am interested in how to set settings of the grub.conf file. When I set i like you were written in the doc file it doesn`t work. GRUB writes me that it can not find a file. Then I decide to denote it directly path to the binary file and it writes me that file system is incorrect. Bellow you can see my grub.conf file. Please check it.
#Version 1
title genode-nova
root (hd0,2)
kernel /gen-nova/kernel/hypervisor noapic
module /gen-nova/bin/core
module /gen-nova/bin/c/init
module /os/config/demo
module /gen-nova/bin/timer
module /gen-nova/bin/ps2_drv
module /gen-nova/bin/pci_drv
module /gen-nova/bin/vesa_drv
module /gen-nova/bin/launchpad
module /gen-nova/bin/nitpicker
module /gen-nova/bin/liquid_fb
module /gen-nova/bin/nitlog
module /gen-nova/bin/testnit
module /gen-nova/bin/scout
#Version2
title genode-nova
root (hd0,2)
kernel /gen-nova/kernel/hypervisor noapic
module /gen-nova/core/core
module /gen-nova/init/init
module /os/config/demo
module /gen-nova/drivers/timer/nova/timer
module /gen-nova/drivers/inputps2/x86/ps2_drv
module /gen-nova/drivers/pci/x86/pci_drv
module /gen-nova/drivers/framebuffer/vesa/versa_drv
module /gen-nova/app/launchpad/launchpad
module /gen-nova/server/nitpicker/genode/nitpicker
module /gen-nova/server/liquid_framebuffer/liquid_fb
module /gen-nova/server/nitlod/nitlog
module /gen-nova/test/nitpicker/testnit
module /gen-nova/app/scout/genode/scout
As a general remark, I would recommend you to direct your questions to the Genode mailing list. This forum is pretty deserted. The mailing list is the place to be. ;-)
You can subscribe the mailing list here: http://genode.org/community/mailing-lists
Regarding your GRUB-related questions, it is hard to pinpoint the problem from remote. I have the following hints though:
* Maybe your partition 2 is formatted with the file system not supported by GRUB? (i.e., raiserfs)
* You can use the GRUB command line to interactively explore the access to files on your disk.
* When booting the system on real hardware, I'd suggest to let GRUB fetch the modules over tftp rather than from disk. This way, you won't need to reboot your test machine into Linux to update the binaries for each test run.
The second point is probably to most important. It is worthwhile to make yourself familiar with GRUB.