Re: Building Screenshots and examples

Lonnie Cumberland <[email protected]> Tue, 5 Nov 2024 15:22:14 -0500
Newsgroups gmane.comp.micro-kernel.l4.devel
Message-ID <[email protected]>
Hello Phillip,

Thanks for getting back to me on these and I have been able to confirm 
that the  .elf32 bit versions do run in qemu which is a good step 
forward and the .efi (x64) version do not at this time as you mentioned.

regarding the "make qemu" I am able to bring up the list, but when I 
select one (actually all of them behave like this), I get an error:

---------------------------------------------------
Could not find
   'fiasco'

within paths

   /home/lonnie/build-amd64/assets
   /home/lonnie/build-amd64/bin/amd64_gen/l4f
   /home/lonnie/build-amd64/bin/amd64_gen/plain
   /home/lonnie/build-amd64/lib/amd64_gen/std/l4f
   /home/lonnie/build-amd64/lib/amd64_gen/std/plain
make[1]: *** [Makefile:693: qemu] Error 1
make[1]: Leaving directory '/home/lonnie/l4'
make: *** [Makefile:6: do-all-make-goals] Error 2

---------------------------------------------------

My fresh setup is via ham and as per the steps 
"https://github.com/kernkonzept/manifest/wiki/BUILDING"

I put ham in my ~/bin/ham and then added it to the PATH so that it is 
able to be used.

On a side question regarding ham, I did try to create a "~/l4re" 
directory and then did the ham init from within there thinking that it 
might put all of the L4Re related directories under that initial 
sub-directory, but it did not and put them under my base home 
directory.  Is there some cli switch or flag that I can use to have ham 
put everything in the l4re sub-directory and build in there instead. 
This is not critical, but mostly just to keep all of the l4re stuff 
together and in one sub-directory for good housekeeping, I guess?

Thanks again and have a great day,
Lonie

On 11/5/2024 7:40 AM, Philipp Eppelt wrote:
> Hi Lonnie,
>
> welcome to the L4Re learning curve. :-)
>
> Indeed, there seems to be a problem with .efi images. Thanks for 
> letting us know.
>
> I can boot the .elf32 image though:
>     l4image -i l4re_vm-basic-pci.elf32 launch
>
> It behaves like shown in the screencast:
> https://l4re.org/cast-vm-basic-pci-qemu-x86.html
>
> Since you already have the github version, you can run the examples 
> from the l4re build directory. `make qemu` executed in your l4re build 
> directory should show a list of example entries to run. These examples 
> are the same as the prebuild images.
>
> Cheers,
> Philipp
>
>
> Am 03.11.24 um 21:52 schrieb Lonnie Cumberland:
>> Hello All,
>>
>> I hope that your day is going well.
>> Recently, I have decided to explore L4Re as a microhypervisor and 
>> capabilities as a possible minimalist component-based microkernel OS.
>>
>> I have just set up Ubuntu 23.10 (x64) in an Intel NUC13 and would am 
>> reviewing as much documentation as I can find as well as am building 
>> the core L4Re according to the Github Wiki just to see how the 
>> process goes.
>>
>> https://github.com/kernkonzept/manifest/wiki/BUILDING
>>
>> As I am in the learning curve at the moment, I also would like to 
>> build some examples such as the "Screenshots" 
>> (https://l4re.org/screens.html) and demos from the Pre-Built section 
>> (https://l4re.org/download/snapshots/pre-built-images/amd64/). I did 
>> try to follow the direction on the pre-built sections and grabbed the 
>> "l4image" and all of the AMD64 EFI files to try and test, but when I 
>> launch them they just seem to hang and do nothing.  I do have qemu 
>> (x64) installed as well, but still nothing seems to boot.
>>
>> What I would like to ask the mailinglist members is where can I get 
>> the source code to the "screenshots" examples as well as the AMD64 
>> "pre-built" examples noted above so that I cam do a fresh compile to 
>> see them in action?
>>
>> Any help would be greatly appreciated.
>>
>> Thanks in advance and have a great day,
>> Lonnie
>>
>> _______________________________________________
>> l4-hackers mailing list -- [email protected]
>> To unsubscribe send an email to [email protected]
>

_______________________________________________
l4-hackers mailing list -- [email protected]
To unsubscribe send an email to [email protected]