users

users@lists.genode.org

2357 discussions

Bionic Porting Errors
by Paramesh Oddepally 27 Jan '15

27 Jan '15

Hello, I am trying to port Bionic Libc on to Genode. At time,I'm struck with the following error that comes when i compiled the library. /home/paramesh/genode-14.08/mybuild/var/libcache/bionic_libc_x86/bionic_libc_x86.lib.a(syscall.o): relocation R_X86_64_PC32 against undefined symbol `__set_errno' can not be used when making a shared object; recompile with -fPIC >From the above compilation error, I understood that *bionic_libc_x86.lib.a* is not compiled with* -fPIC* flag enabled(which is needed for Position Independent code generation by compiler and that is what essentially needed in Shared LIb buiding(*bionic_libstdc++.lib.so*) that uses the above static library). So, i assigned *-fPIC* flag to compiler variable *CC_OPT* to resolve it, but it is not showing the effect. So, can any one tell me how can I resolve it. Correct me if I'm wrong somewhere. -- Thanks and Regards, Paramesh.O M.Tech. Department of Computer Science and Engineering I.I.T. Madras, Chennai, India

2 1

How to build L4android with genode
by ChenZhen 27 Jan '15

27 Jan '15

Hi all, I want to build L4android. I can’t find ‘l4android.run’ in latest release of genode, which is metioned in genode/repos/ports-foc/readme. I got l4android.run from genode 12.08, but failed to build it. Where can I get the right run script of l4android ? Best, Zachary

2 1

Additional Required Packages
by Jeroen "Slim" van Gelderen 26 Jan '15

26 Jan '15

Hi, Running Ubuntu 14.04 LTS Desktop (x64). In addition to the packages mentioned at http://genode.org/documentation/developer-resources/getting_started I also had to apt-get install the following packages to build certain ports and/or kernels: autoconf2.64 autogen bison flex g++ git gperf libxml2-utils subversion xsltproc -- Jeroen "Slim" van Gelderen

2 1

Associating Threads with Process Rm's
by Bob Stewart 26 Jan '15

26 Jan '15

Hi, I'm being spectacularly unsuccessful in getting a process thread to be associated with an RM Pager object. I have an application whose main function creates an object instance based on a Thread. That instance creates another object instance whose main purpose is to read and write to an ffat file system through the libc plug-in for that purpose. As soon as this object attempts to access the file system a error message complaining about no pager object implemented ("/void Genode::Pager_object::unresolved_page_fault_occurred(): not implemented/") occurs. On re-reading the Architecture documentation about RM in the Core, it *very* briefly explains that a thread capability for a pager needs to be created for the thread, using an add_client function call. I assumed this would be done in the thread entry() member function and added the following line of code at the the beginning of that function: Thread_capability ap = Thread::cap(); Pager_capability pc = env()->rm_session()->add_client(ap); env()->cpu_session()->set_pager(ap, pc); This did not work and I got he same error message about no pager object. In looking through the threading code, I noticed that Thread_base::start() creates the thread and sets up a pager. Adding a void start() function to my thread with a call to the Thread_base::start function resulted in the same error. I finally got a pager to be associated with the thread and access the file system by creating my own thread object in my thread start() function, binding it to the PD, and setting up the pager with the snippet shown above the same as was done in the Thread_base::start() function. I'm obviously confused about what's going with a process's region manager handling of threads. Could someone please enlighten me? Thanks in advance, Bob Stewart Bob Stewart

3 7

genode-manual make error
by Bob Stewart 23 Jan '15

23 Jan '15

Hi, I tried to execute make in the manual directory after getting gosh and the texlive stuff and got an error on a chapter_tag: bob@...297...:/Work/genode-manual/manual$ make gosh --style manual.gosh manual.txt > misc.tmp.tex can't read "chapter_tag": no such variable while executing "printline "\\$chapter_tag[section_env_latex $title]"" (procedure "process_chapter_latex" line 9) invoked from within "process_chapter_latex {{20 Introduction} {21 ############} {22 {}} {23 {}} {24 {Universal truths}} {25 ================} {26 {}} {27 {| TODO}} {28 {}}..." ("eval" body line 1) invoked from within "eval "$spec_function [list $content]"" (procedure "handle_txtblock" line 18) invoked from within "handle_txtblock documentmain $txtcontent" (file "/usr/bin/gosh" line 1177) make: *** [manual.pdf] Error 1 Thanks for any help.

3 2

SMC in tz_vmm
by chirag garg 23 Jan '15

23 Jan '15

Hi all, I have some doubts in Genode Flow, ARM provides the smc instruction to enter in the monitor-mode which performs the world switch between normal world and secure world. As tz_vmm script is also successfully achieving the above objective of world switch from the secure world to the normal world. But i am not able to figure out flow which will which execute a call of smc instruction in the run of tz_vmm script. Can anyone explain me the flow ? Thanks in advance. Regards Chirag Garg IIT Madras , Rise Lab

3 3

1st Microkernel Stammtisch 2015
by Julian Stecklina 23 Jan '15

23 Jan '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Dear Microkernel Hackers in and around Dresden, let's meet for a drink and trade stories! Where: Campus, HÃ¼bnerstr. 13, Dresden, Germany When: Thursday, Jan 29th, 2015 @ 20:00 CET Please leave an entry in this doodle, if you plan to join, so we can reserve a sufficiently large table: http://doodle.com/ktv4nrn5wutg569w Feel free to forward this mail, Julian -----BEGIN PGP SIGNATURE----- Version: OpenKeychain v3.1.2 iGcEAREIACcgHEp1bGlhbiBTdGVja2xpbmEgPGpzQGFsaWVuOC5kZT4FAlTCHuIA CgkQ2EtjUdW3H9kobACfSvmrOIxq/sOggHb78yVTzuKbGi4AoOxiBKy7UUBP/WbY XP3xTD4Trk3q =4V+q -----END PGP SIGNATURE-----

1 0

make run/rump_ext2 fails
by Adrian 22 Jan '15

22 Jan '15

Hello, I am trying to explore the rump_fs facilities. I followed the repos/dde_rump/README and failed when executing make run/rump_ext2. Following is a pasted-in terminal output. Any help would be appreciated. adrian@...295...:~/genode-14.11/build/build.fs$ make run/rump_ext2 using run script /home/adrian/genode-14.11/repos/base-nova/run/env using run script /home/adrian/genode-14.11/repos/dde_rump/run/rump_ext2.run building targets: core init drivers/timer server/ram_blk server/rump_fs test/libc_vfs spawn make core init drivers/timer server/ram_blk server/rump_fs test/libc_vfs make[1]: Betrete Verzeichnis '/home/adrian/genode-14.11/build/build.fs' Error: target 'test/libc_vfs' does not exist make[1]: *** [error_missing_targets] Fehler 1 make[1]: Verlasse Verzeichnis '/home/adrian/genode-14.11/build/build.fs' Error: Genode build failed make: *** [run/rump_ext2] Fehler 252 adrian@...295...:~/genode-14.11/build/build.fs$ Regards, Adrian Schuur

3 2

[HEADS UP] Refactored run tool on staging
by Josef Söntgen 22 Jan '15

22 Jan '15

Hello, tl;dr we merged the modularized version of our run tool to the staging branch. This version requires changes in the build directory, e.g., changes to 'etc/build.conf' and it is therefore advised to remake all used build directories if one uses the current staging branch. There is also 'tool/run/README', which explains the usage and the architecture in more detail. In addition you can take a look at the corresponding issue [1]. The run tool served us well over the years and by continously extending its functionality it met our daily requirements. The way it was extended up to now, however, was in an ad-hoc fashion that made future changes and maintaining more time-consuming. We addressed these problems by refactoring the run tool: * Modularizing the run tool: each step (building/loading components, execution scenarios and so) is now implemented by a module. All of the common use cases, that were handled by the old run tool, are now covered by combining these modules. This makes the actual run tool more managable and makes future extensions easier. * Unifying the argument handling of the run tool: each module is configured explicitly in the same fashion. That makes configuration failures more visible. To just give an example on how the interface of the run tool changed, here is a comparison of the old way and the new way to handle a common use case: In this case, we want to reset the target system and caputure the LOG output via AMT. The target system loads all files it needs to execute the scenario via TFTP: * Old (changes in nova_x86_64/etc/build.conf): RUN_OPT = --target amt --tftp-absolute export AMT_TEST_MACHINE_IP = 10.23.42.51 export AMT_TEST_MACHINE_PWD = secret export PXE_TFTP_DIR_BASE = /var/lib/tftpboot export PXE_TFTP_DIR_OFFSET = /x86 * New (changes in nova_x86_64/etc/build.conf): RUN_OPT = --include boot_dir/nova AMT_HOST = 10.23.42.51 AMT_PASSWORD = secret RUN_OPT += --include power_on/amt \ --power-on-amt-host $(AMT_HOST) \ --power-on-amt-password $(AMT_PASSWORD) RUN_OPT += --include log/amt \ --log-amt-host $(AMT_HOST) \ --log-amt-password $(AMT_PASSWORD) RUN_OPT += --include load/tftp \ --load-tftp-base-dir /var/lib/tftpboot \ --load-tftp-offset-dir /x86 --load-tftp-absolute The new way is arguably more verbose but also makes the configuration more clear, which is more important in our opinion. In addition, it is possible to capture the LOG output, i.e., via an USB-serial adapter by replacing 'log/amt' with 'log/serial'. That is something, that was more difficult to achieve with the old tool. When creating a new build dir, a default RUN_OPT configuration is added to the generated 'build.conf'. In most cases this means creating an ISO image and starting the scenario in Qemu like the old tool did in the default configuration. As I have said before, there is a README file, that hopefully provides all information that is needed to get you started with the new tool. If you think there is something that is missing from this documentation, please drop a note either via E-Mail or github. Cheers Josef [1] https://github.com/genodelabs/genode/issues/1355

1 0

Run script issue
by chirag garg 20 Jan '15

20 Jan '15

Hi all, I created one run script "switch" which gives me the following error at compilation at the last stage. make[1]: Leaving directory `/home/chirag/genode-ns/build6' cp: cannot stat `bin/switch': No such file or directory while executing "exec cp bin/$binary [run_dir]/genode" (procedure "copy_and_strip_genode_binaries_to_run_dir" line 4) invoked from within "copy_and_strip_genode_binaries_to_run_dir $binaries" (procedure "build_boot_image" line 16) invoked from within "build_boot_image "core init switch"" (file "/home/chirag/genode-ns/repos/os/run/switch.run" line 37) invoked from within "source $include_name" ("foreach" body line 3) invoked from within "foreach include_name [get_cmd_arg --include ""] { puts "using run script $include_name" source $include_name }" (file "/home/chirag/genode-ns/tool/run" line 1004) make: *** [run/switch] Error 1 Like error message says that it is not able to copy switch file from the bin folder because it is not there. WHY this script is failed to create the bin/switch file ? Please let me know the all possible reason behind it. I am attaching switch.run script in the mail. Thanks in advance. Regards Chirag Garg IIT Madras , Rise Lab

3 4

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users