Hi All,
I have been trying to work with the LDSO library and have been having some more package. I am running Genode on top of Pistachio.
I created a bootable image with the LDSO module, but when I start the disk, I get the following error message from LDSO:
[init -> ldso] Starting ldso ... [init -> ldso] realloc - not yet implemented 04804002 pf @ fffffffc, ip=00042ecd --- "KD# user touches kernel area" --- --------------------------------- (eip=f010c342, esp=f01163c7) ---
It's clear that realloc is not implemented, but is this provided in some other file? How do I work with the LDSO code?
-Sam Kerr
Hi Sam,
can you send me your Genode 'config' file? Furthermore, please set the 'DEBUG' variable in '<GENODE>/os/src/ldso/target.inc' to '1', recompile ldso, start your scenario, and attach the produced output as well.
-- Sebastian
On 03/17/2011 01:04 PM, Sam Kerr wrote:
Hi All,
I have been trying to work with the LDSO library and have been having some more package. I am running Genode on top of Pistachio.
I created a bootable image with the LDSO module, but when I start the disk, I get the following error message from LDSO:
[init -> ldso] Starting ldso ... [init -> ldso] realloc - not yet implemented 04804002 pf @ fffffffc, ip=00042ecd --- "KD# user touches kernel area" --- --------------------------------- (eip=f010c342, esp=f01163c7) ---
It's clear that realloc is not implemented, but is this provided in some other file? How do I work with the LDSO code?
-Sam Kerr
Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d _______________________________________________ Genode-main mailing list Genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main
I enabled debugging output for LDSO. The relevant output for my scenario is:
thread 'ldso' has id 0x01020002 (task = 0x2, thread = 0x8) thread 'ldso' has id 0x04804002 (task = 0x9, thread = 0x1) [init -> ldso] Starting ldso ... [init -> ldso] /libexec/ld-elf.so.1 is initialized, base address = 30000 [init -> ldso] RTLD dynamic = 57974 [init -> ldso] RTLD pltgot = 0 [init -> ldso] loading main program [init -> ldso] void* mmap(void*, size_t, int, int, int, off_t): addr: 30000 length: 3c000 flags: 20002 [init -> ldso] void* mmap(void*, size_t, int, int, int, off_t): fd: 0, prot: 5 offs: 1000 [init -> ldso] realloc - not yet implemented 04804002 pf @ fffffffc, ip=000432ad --- "KD# user touches kernel area" --- --------------------------------- (eip=f010c342, esp=f01163c7) --- > go no RM attachment (READ pf_addr=fffffffc pf_ip=432ad from 1201 (raw 04804002)) invalid signal-context capability
I wasn't really sure what to do as far as config files went. I found the following through a google search:
<config> <parent-provides> <service name="ROM"/> <service name="RAM"/> <service name="IRQ"/> <service name="IO_MEM"/> <service name="IO_PORT"/> <service name="CAP"/> <service name="PD"/> <service name="RM"/> <service name="CPU"/> <service name="LOG"/> </parent-provides>
<default-route> <any-service> <parent/> <any-child/> </any-service> </default-route> <start name="ps2_drv"> <resource name="RAM" quantum="1M"/> <provides><service name="Input"/></provides> </start> <start name="pci_drv"> <resource name="RAM" quantum="1M"/> <provides><service name="PCI"/></provides> </start> <start name="timer"> <resource name="RAM" quantum="1M"/> <provides><service name="Timer"/></provides> </start> <start name="nitpicker"> <resource name="RAM" quantum="1M"/> <provides><service name="Nitpicker"/></provides> </start> <start name="vesa_drv"> <resource name="RAM" quantum="1M"/> <provides><service name="Framebuffer"/></provides> </start> <start name="launchpad"> <resource name="RAM" quantum="32M"/> </start> <start name="ldso"> <resource name="RAM" quantum="32M"/> </start> <start name="sharedlib"> <resource name="RAM" quantum="10M"/> </start> <memsection name="ldso" file="ldso" direct="true" /> </config>
Thanks for any help!
-Sam Kerr
On Mar 17, 2011, at 9:35 AM, Sebastian Sumpf wrote:
Hi Sam,
can you send me your Genode 'config' file? Furthermore, please set the 'DEBUG' variable in '<GENODE>/os/src/ldso/target.inc' to '1', recompile ldso, start your scenario, and attach the produced output as well.
-- Sebastian
On 03/17/2011 01:04 PM, Sam Kerr wrote:
Hi All,
I have been trying to work with the LDSO library and have been having some more package. I am running Genode on top of Pistachio.
I created a bootable image with the LDSO module, but when I start the disk, I get the following error message from LDSO:
[init -> ldso] Starting ldso ... [init -> ldso] realloc - not yet implemented 04804002 pf @ fffffffc, ip=00042ecd --- "KD# user touches kernel area" --- --------------------------------- (eip=f010c342, esp=f01163c7) ---
It's clear that realloc is not implemented, but is this provided in some other file? How do I work with the LDSO code?
-Sam Kerr
Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d _______________________________________________ Genode-main mailing list Genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main
Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d _______________________________________________ Genode-main mailing list Genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main
Hi,
<config> <parent-provides> <service name="ROM"/> <service name="RAM"/> <service name="IRQ"/> <service name="IO_MEM"/> <service name="IO_PORT"/> <service name="CAP"/> <service name="PD"/> <service name="RM"/> <service name="CPU"/> <service name="LOG"/> </parent-provides> <default-route> <any-service> <parent/> <any-child/> </any-service> </default-route> <start name="ps2_drv"> <resource name="RAM" quantum="1M"/> <provides><service name="Input"/></provides> </start> <start name="pci_drv"> <resource name="RAM" quantum="1M"/> <provides><service name="PCI"/></provides> </start> <start name="timer"> <resource name="RAM" quantum="1M"/> <provides><service name="Timer"/></provides> </start> <start name="nitpicker"> <resource name="RAM" quantum="1M"/> <provides><service name="Nitpicker"/></provides> </start> <start name="vesa_drv"> <resource name="RAM" quantum="1M"/> <provides><service name="Framebuffer"/></provides> </start> <start name="launchpad"> <resource name="RAM" quantum="32M"/> </start> <start name="ldso"> <resource name="RAM" quantum="32M"/> </start> <start name="sharedlib"> <resource name="RAM" quantum="10M"/> </start> <memsection name="ldso" file="ldso" direct="true" /> </config>
As I mentioned before, *never* start ldso in your Genode config file. All <start> tags are programs that will be launched by Genode, if during this process a binary is encountered that is linked against shared libraries, Genode will *automatically* invoke ldso in order to load the program and the needed shared libs.
To give you a small example (please run make run/ldso from your Genode build directory). This will build an application called 'test-ldso'.
If you run 'objdump -p test-ldso you will see:
bin/test-ldso: file format elf32-i386
Program Header: PHDR off 0x00000034 vaddr 0x00001034 paddr 0x00000000 align 2**2 filesz 0x000000c0 memsz 0x000000c0 flags r-- INTERP off 0x000190b5 vaddr 0x003180b5 paddr 0x003180b5 align 2**0 filesz 0x00000007 memsz 0x00000007 flags r-- LOAD off 0x00001000 vaddr 0x00300000 paddr 0x00300000 align 2**12 filesz 0x0002499c memsz 0x0002499c flags r-x LOAD off 0x00026000 vaddr 0x00325000 paddr 0x00325000 align 2**12 filesz 0x00008037 memsz 0x0001b070 flags rwx DYNAMIC off 0x0002b4ec vaddr 0x0032a4ec paddr 0x0032a4ec align 2**12 filesz 0x00002b4b memsz 0x00015293 flags rwx EH_FRAME off 0x00024cc8 vaddr 0x00323cc8 paddr 0x00323cc8 align 2**2 filesz 0x00000cd4 memsz 0x00000cd4 flags r--
Dynamic Section: NEEDED /build/genode_rtld_elf/var/libcache/libc/libc.lib.so NEEDED /build/genode_rtld_elf/var/libcache/libm/libm.lib.so NEEDED /build/genode_rtld_elf/var/libcache/test-ldso/test-ldso.lib.so HASH 0x003180bc STRTAB 0x0031bc00 SYMTAB 0x00319320 STRSZ 0x0000564f SYMENT 0x00000010 DEBUG 0x00000000 PLTGOT 0x0032a59c PLTRELSZ 0x00000018 PLTREL 0x00000011 JMPREL 0x00321510 REL 0x00321250 RELSZ 0x000002c0 RELENT 0x00000008
The 'NEEDED' shows you that test-ldso depends on libc.lib.so, lbm.lib.so, and test-ldso.lib.so. In order to start the application in Genode a config file would look like this:
<config> <parent-provides> <service name="ROM"/> <service name="LOG"/> </parent-provides> <default-route> <any-service> <parent/> </any-service> </default-route> <start name="test-ldso"> <resource name="RAM" quantum="1M"/> </start> </config>
You only need to start 'test-ldso', but the boot loader file would look like this:
title Genode on L4ka::Pistachio kernel /pistachio/kickstart module /pistachio/x86-kernel module /pistachio/sigma0 module /genode/core module /genode/config module /genode/init module /genode/ldso module /genode/test-ldso module /genode/test-ldso.lib.so module /genode/libc.lib.so module /genode/libm.lib.so
Here you load the shared libaries and ldso so Genode can find them when starting test-ldso. You can find the whole example under <GENODE_BUILDDIR>/var/run/ldso.
So, assuming that 'sharedlib' is a program and *not* a library:
Remove this part from your config file:
<start name="ldso"> <resource name="RAM" quantum="32M"/> </start>
If 'sharedlib' is a library remove this start tag a well and substitute it with the actual program using the library.
Remove:
<memsection name="ldso" file="ldso" direct="true" />
This looks like it was taken from an elfweaver config file which is OKL4 specific and has nothing to do with Genode configuration altogether.
Good luck,
-- Sebastian
Hi Sebastian,
Thanks for the suggestions. You pointing out several mistakes will be help me out in the future.
However, I am not able to build the LDSO application using 'make run/ldso'. Instead, it says :
Error: No run script for ldso make: *** [run/ldso] Error 255
Any suggestions?
-Sam Kerr
On Mar 17, 2011, at 10:50 AM, Sebastian Sumpf wrote:
Hi,
<config> <parent-provides> <service name="ROM"/> <service name="RAM"/> <service name="IRQ"/> <service name="IO_MEM"/> <service name="IO_PORT"/> <service name="CAP"/> <service name="PD"/> <service name="RM"/> <service name="CPU"/> <service name="LOG"/> </parent-provides>
<default-route> <any-service> <parent/> <any-child/> </any-service> </default-route> <start name="ps2_drv"> <resource name="RAM" quantum="1M"/> <provides><service name="Input"/></provides> </start> <start name="pci_drv"> <resource name="RAM" quantum="1M"/> <provides><service name="PCI"/></provides> </start> <start name="timer"> <resource name="RAM" quantum="1M"/> <provides><service name="Timer"/></provides> </start> <start name="nitpicker"> <resource name="RAM" quantum="1M"/> <provides><service name="Nitpicker"/></provides> </start> <start name="vesa_drv"> <resource name="RAM" quantum="1M"/> <provides><service name="Framebuffer"/></provides> </start> <start name="launchpad"> <resource name="RAM" quantum="32M"/> </start> <start name="ldso"> <resource name="RAM" quantum="32M"/> </start> <start name="sharedlib"> <resource name="RAM" quantum="10M"/> </start> <memsection name="ldso" file="ldso" direct="true" />
</config>
As I mentioned before, *never* start ldso in your Genode config file. All <start> tags are programs that will be launched by Genode, if during this process a binary is encountered that is linked against shared libraries, Genode will *automatically* invoke ldso in order to load the program and the needed shared libs.
To give you a small example (please run make run/ldso from your Genode build directory). This will build an application called 'test-ldso'.
If you run 'objdump -p test-ldso you will see:
bin/test-ldso: file format elf32-i386
Program Header: PHDR off 0x00000034 vaddr 0x00001034 paddr 0x00000000 align 2**2 filesz 0x000000c0 memsz 0x000000c0 flags r-- INTERP off 0x000190b5 vaddr 0x003180b5 paddr 0x003180b5 align 2**0 filesz 0x00000007 memsz 0x00000007 flags r-- LOAD off 0x00001000 vaddr 0x00300000 paddr 0x00300000 align 2**12 filesz 0x0002499c memsz 0x0002499c flags r-x LOAD off 0x00026000 vaddr 0x00325000 paddr 0x00325000 align 2**12 filesz 0x00008037 memsz 0x0001b070 flags rwx DYNAMIC off 0x0002b4ec vaddr 0x0032a4ec paddr 0x0032a4ec align 2**12 filesz 0x00002b4b memsz 0x00015293 flags rwx EH_FRAME off 0x00024cc8 vaddr 0x00323cc8 paddr 0x00323cc8 align 2**2 filesz 0x00000cd4 memsz 0x00000cd4 flags r--
Dynamic Section: NEEDED /build/genode_rtld_elf/var/libcache/libc/libc.lib.so NEEDED /build/genode_rtld_elf/var/libcache/libm/libm.lib.so NEEDED /build/genode_rtld_elf/var/libcache/test-ldso/test-ldso.lib.so HASH 0x003180bc STRTAB 0x0031bc00 SYMTAB 0x00319320 STRSZ 0x0000564f SYMENT 0x00000010 DEBUG 0x00000000 PLTGOT 0x0032a59c PLTRELSZ 0x00000018 PLTREL 0x00000011 JMPREL 0x00321510 REL 0x00321250 RELSZ 0x000002c0 RELENT 0x00000008
The 'NEEDED' shows you that test-ldso depends on libc.lib.so, lbm.lib.so, and test-ldso.lib.so. In order to start the application in Genode a config file would look like this:
<config> <parent-provides> <service name="ROM"/> <service name="LOG"/> </parent-provides> <default-route> <any-service> <parent/> </any-service> </default-route> <start name="test-ldso"> <resource name="RAM" quantum="1M"/> </start> </config>
You only need to start 'test-ldso', but the boot loader file would look like this:
title Genode on L4ka::Pistachio kernel /pistachio/kickstart module /pistachio/x86-kernel module /pistachio/sigma0 module /genode/core module /genode/config module /genode/init module /genode/ldso module /genode/test-ldso module /genode/test-ldso.lib.so module /genode/libc.lib.so module /genode/libm.lib.so
Here you load the shared libaries and ldso so Genode can find them when starting test-ldso. You can find the whole example under <GENODE_BUILDDIR>/var/run/ldso.
So, assuming that 'sharedlib' is a program and *not* a library:
Remove this part from your config file:
<start name="ldso"> <resource name="RAM" quantum="32M"/> </start>
If 'sharedlib' is a library remove this start tag a well and substitute it with the actual program using the library.
Remove:
<memsection name="ldso" file="ldso" direct="true" />
This looks like it was taken from an elfweaver config file which is OKL4 specific and has nothing to do with Genode configuration altogether.
Good luck,
-- Sebastian
Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d _______________________________________________ Genode-main mailing list Genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main
Hello Sam,
which version of Genode are you using? I ask because the ldso run script ('os/run/ldso.run') was just introduced with the release 11.02.
If an update to the current version does not solve your problem, could you please post your '<build-dir>/etc/build.conf' file?
Norman
On 03/18/2011 09:14 PM, Sam Kerr wrote:
Hi Sebastian,
Thanks for the suggestions. You pointing out several mistakes will be help me out in the future.
However, I am not able to build the LDSO application using 'make run/ldso'. Instead, it says :
Error: No run script for ldso make: *** [run/ldso] Error 255
Any suggestions?
-Sam Kerr
Hi Sam,
On 03/18/2011 09:14 PM, Sam Kerr wrote:
Hi Sebastian,
Thanks for the suggestions. You pointing out several mistakes will be help me out in the future.
However, I am not able to build the LDSO application using 'make run/ldso'. Instead, it says :
Error: No run script for ldso make: *** [run/ldso] Error 255
Any suggestions?
That's strange. Please check if the file <Genode source directory>/os/run/ldso.run is present, if not please update your Genode version to the current SVN head. If it is still not there let me know.
Greetings,
Sebastian
Well now I feel silly. I have been using 10.11. I'll try using 11.02 and let you know if I have any problems.
-Sam Kerr
On Mar 19, 2011, at 6:58 AM, Norman Feske wrote:
Hello Sam,
which version of Genode are you using? I ask because the ldso run script ('os/run/ldso.run') was just introduced with the release 11.02.
If an update to the current version does not solve your problem, could you please post your '<build-dir>/etc/build.conf' file?
Norman
On 03/18/2011 09:14 PM, Sam Kerr wrote:
Hi Sebastian,
Thanks for the suggestions. You pointing out several mistakes will be help me out in the future.
However, I am not able to build the LDSO application using 'make run/ldso'. Instead, it says :
Error: No run script for ldso make: *** [run/ldso] Error 255
Any suggestions?
-Sam Kerr
-- Dr.-Ing. Norman Feske Genode Labs
http://www.genode-labs.com · http://genode.org
Genode Labs GmbH · Amtsgericht Dresden · HRB 28424 · Sitz Dresden Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth
Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d _______________________________________________ Genode-main mailing list Genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main
Hi Sebastian,
I have been working on updating to Genode 11.02 and have make run/ldso giving me output, but this does not build the test-ldso file some reason...
It looks like the run script is being found and executing, but the test/ldso target is not there for some reason... I confirmed this by trying 'make test/ldso' and got a non-existing error.
I am getting the following output:
genode@...67...:/media/sf_Public/genode-11.02/build-pistachio$ make run/ldso using run script /media/sf_Public/genode-11.02/base-pistachio/run/env using run script /media/sf_Public/genode-11.02/os/run/ldso.run building targets: core init ldso test/ldso spawn make core init ldso test/ldso make[1]: Entering directory `/media/sf_Public/genode-11.02/build-pistachio' checking library dependencies for core... checking library dependencies for init... checking library dependencies for ldso... Skip target ldso/arm because it requires arm Skip target ldso/x86_64 because it requires 64bit checking library dependencies for test/ldso... Error: non-existing target test/ldso Library ipc Library slab Library avl_tree Library allocator_avl Library heap Library console Library log_console Library lock Library env Library cxx Library thread Library server Library elf Library process Library startup Program init/init Library ldso-arch Program ldso/x86_32/ldso Library core_printf Library pager Library raw_signal Library raw_server Library kip Library hexdump Program core/x86/core make[1]: Leaving directory `/media/sf_Public/genode-11.02/build-pistachio' genode build completed cp: cannot stat `bin/test-ldso': No such file or directory while executing "exec cp bin/$binary [run_dir]/genode" (procedure "build_boot_image" line 7) invoked from within "build_boot_image "core init ldso test-ldso test-ldso.lib.so libc.lib.so libm.lib.so"" (file "/media/sf_Public/genode-11.02/os/run/ldso.run" line 20) 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 "/media/sf_Public/genode-11.02/tool/run" line 258) make: *** [run/ldso] Error 1
Any thoughts?
-Sam Kerr
On Mar 19, 2011, at 2:11 PM, Sebastian Sumpf wrote:
Hi Sam,
On 03/18/2011 09:14 PM, Sam Kerr wrote:
Hi Sebastian,
Thanks for the suggestions. You pointing out several mistakes will be help me out in the future.
However, I am not able to build the LDSO application using 'make run/ldso'. Instead, it says :
Error: No run script for ldso make: *** [run/ldso] Error 255
Any suggestions?
That's strange. Please check if the file <Genode source directory>/os/run/ldso.run is present, if not please update your Genode version to the current SVN head. If it is still not there let me know.
Greetings,
Sebastian
Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d _______________________________________________ Genode-main mailing list Genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main
Hello Sam,
you need to enable the libc repository in your build environment. Please make sure the following line in your 'etc/build.conf' isn't commented out:
REPOSITORIES += $(GENODE_DIR)/libc
Regards Stefan
On 03/23/2011 04:37 PM, Sam Kerr wrote:
Hi Sebastian,
I have been working on updating to Genode 11.02 and have make run/ldso giving me output, but this does not build the test-ldso file some reason...
It looks like the run script is being found and executing, but the test/ldso target is not there for some reason... I confirmed this by trying 'make test/ldso' and got a non-existing error.
I am getting the following output:
genode@...67...:/media/sf_Public/genode-11.02/build-pistachio$ make run/ldso using run script /media/sf_Public/genode-11.02/base-pistachio/run/env using run script /media/sf_Public/genode-11.02/os/run/ldso.run building targets: core init ldso test/ldso spawn make core init ldso test/ldso make[1]: Entering directory `/media/sf_Public/genode-11.02/build-pistachio' checking library dependencies for core... checking library dependencies for init... checking library dependencies for ldso... Skip target ldso/arm because it requires arm Skip target ldso/x86_64 because it requires 64bit checking library dependencies for test/ldso... Error: non-existing target test/ldso Library ipc Library slab Library avl_tree Library allocator_avl Library heap Library console Library log_console Library lock Library env Library cxx Library thread Library server Library elf Library process Library startup Program init/init Library ldso-arch Program ldso/x86_32/ldso Library core_printf Library pager Library raw_signal Library raw_server Library kip Library hexdump Program core/x86/core make[1]: Leaving directory `/media/sf_Public/genode-11.02/build-pistachio' genode build completed cp: cannot stat `bin/test-ldso': No such file or directory while executing "exec cp bin/$binary [run_dir]/genode" (procedure "build_boot_image" line 7) invoked from within "build_boot_image "core init ldso test-ldso test-ldso.lib.so libc.lib.so libm.lib.so"" (file "/media/sf_Public/genode-11.02/os/run/ldso.run" line 20) 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 "/media/sf_Public/genode-11.02/tool/run" line 258) make: *** [run/ldso] Error 1
Any thoughts?
-Sam Kerr
On Mar 19, 2011, at 2:11 PM, Sebastian Sumpf wrote:
Hi Sam,
On 03/18/2011 09:14 PM, Sam Kerr wrote:
Hi Sebastian,
Thanks for the suggestions. You pointing out several mistakes will be help me out in the future.
However, I am not able to build the LDSO application using 'make run/ldso'. Instead, it says :
Error: No run script for ldso make: *** [run/ldso] Error 255
Any suggestions?
That's strange. Please check if the file <Genode source directory>/os/run/ldso.run is present, if not please update your Genode version to the current SVN head. If it is still not there let me know.
Greetings,
Sebastian
Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d _______________________________________________ Genode-main mailing list Genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main
Enable your software for Intel(R) Active Management Technology to meet the growing manageability and security demands of your customers. Businesses are taking advantage of Intel(R) vPro (TM) technology - will your software be a part of the solution? Download the Intel(R) Manageability Checker today! http://p.sf.net/sfu/intel-dev2devmar _______________________________________________ Genode-main mailing list Genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main
Hallo Sam,
the ldso test program is contained in the libc repository (at 'libc/src/test/ldso'). You have to enable this repository in your '<build-dir>/etc/build.conf' file:
REPOSITORIES += $(GENODE_DIR)/libc
Cheers Norman
Hi Stefan,
I have that included in my build.conf file. My file looks like:
1 REPOSITORIES = ../base-pistachio ../base \ 2 ../libc ../os ../demo
-Sam Kerr
On Mar 23, 2011, at 11:52 AM, Stefan Kalkowski wrote:
Hello Sam,
you need to enable the libc repository in your build environment. Please make sure the following line in your 'etc/build.conf' isn't commented out:
REPOSITORIES += $(GENODE_DIR)/libc
Regards Stefan
On 03/23/2011 04:37 PM, Sam Kerr wrote:
Hi Sebastian,
I have been working on updating to Genode 11.02 and have make run/ldso giving me output, but this does not build the test-ldso file some reason...
It looks like the run script is being found and executing, but the test/ldso target is not there for some reason... I confirmed this by trying 'make test/ldso' and got a non-existing error.
I am getting the following output:
genode@...67...:/media/sf_Public/genode-11.02/build-pistachio$ make run/ldso using run script /media/sf_Public/genode-11.02/base-pistachio/run/env using run script /media/sf_Public/genode-11.02/os/run/ldso.run building targets: core init ldso test/ldso spawn make core init ldso test/ldso make[1]: Entering directory `/media/sf_Public/genode-11.02/build-pistachio' checking library dependencies for core... checking library dependencies for init... checking library dependencies for ldso... Skip target ldso/arm because it requires arm Skip target ldso/x86_64 because it requires 64bit checking library dependencies for test/ldso... Error: non-existing target test/ldso Library ipc Library slab Library avl_tree Library allocator_avl Library heap Library console Library log_console Library lock Library env Library cxx Library thread Library server Library elf Library process Library startup Program init/init Library ldso-arch Program ldso/x86_32/ldso Library core_printf Library pager Library raw_signal Library raw_server Library kip Library hexdump Program core/x86/core make[1]: Leaving directory `/media/sf_Public/genode-11.02/build-pistachio' genode build completed cp: cannot stat `bin/test-ldso': No such file or directory while executing "exec cp bin/$binary [run_dir]/genode" (procedure "build_boot_image" line 7) invoked from within "build_boot_image "core init ldso test-ldso test-ldso.lib.so libc.lib.so libm.lib.so"" (file "/media/sf_Public/genode-11.02/os/run/ldso.run" line 20) 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 "/media/sf_Public/genode-11.02/tool/run" line 258) make: *** [run/ldso] Error 1
Any thoughts?
-Sam Kerr
On Mar 19, 2011, at 2:11 PM, Sebastian Sumpf wrote:
Hi Sam,
On 03/18/2011 09:14 PM, Sam Kerr wrote:
Hi Sebastian,
Thanks for the suggestions. You pointing out several mistakes will be help me out in the future.
However, I am not able to build the LDSO application using 'make run/ldso'. Instead, it says :
Error: No run script for ldso make: *** [run/ldso] Error 255
Any suggestions?
That's strange. Please check if the file <Genode source directory>/os/run/ldso.run is present, if not please update your Genode version to the current SVN head. If it is still not there let me know.
Greetings,
Sebastian
Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d _______________________________________________ Genode-main mailing list Genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main
Enable your software for Intel(R) Active Management Technology to meet the growing manageability and security demands of your customers. Businesses are taking advantage of Intel(R) vPro (TM) technology - will your software be a part of the solution? Download the Intel(R) Manageability Checker today! http://p.sf.net/sfu/intel-dev2devmar _______________________________________________ Genode-main mailing list Genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main
-- Stefan Kalkowski Genode Labs
http://www.genode-labs.com/ · http://genode.org/
Genode Labs GmbH · Amtsgericht Dresden · HRB 28424 · Sitz Dresden Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth
Enable your software for Intel(R) Active Management Technology to meet the growing manageability and security demands of your customers. Businesses are taking advantage of Intel(R) vPro (TM) technology - will your software be a part of the solution? Download the Intel(R) Manageability Checker today! http://p.sf.net/sfu/intel-dev2devmar _______________________________________________ Genode-main mailing list Genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main
Hello Sam,
apparently, the ldso test program was missing in the SVN. I have just added it now.
Sorry for the inconvenience. Now I'm feeling a bit silly ,-)
Norman
That might account for some issues! I'll give things another shot and let you know if I run into more problems.
-Sam Kerr
On Mar 23, 2011, at 12:15 PM, Norman Feske wrote:
Hello Sam,
apparently, the ldso test program was missing in the SVN. I have just added it now.
Sorry for the inconvenience. Now I'm feeling a bit silly ,-)
Norman
Enable your software for Intel(R) Active Management Technology to meet the growing manageability and security demands of your customers. Businesses are taking advantage of Intel(R) vPro (TM) technology - will your software be a part of the solution? Download the Intel(R) Manageability Checker today! http://p.sf.net/sfu/intel-dev2devmar _______________________________________________ Genode-main mailing list Genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main
Alright, well after all that, I managed to get the test-ldso loaded onto a disk and running successfully. Thanks for all your help!
-Sam Kerr
On Mar 23, 2011, at 12:15 PM, Norman Feske wrote:
Hello Sam,
apparently, the ldso test program was missing in the SVN. I have just added it now.
Sorry for the inconvenience. Now I'm feeling a bit silly ,-)
Norman
Enable your software for Intel(R) Active Management Technology to meet the growing manageability and security demands of your customers. Businesses are taking advantage of Intel(R) vPro (TM) technology - will your software be a part of the solution? Download the Intel(R) Manageability Checker today! http://p.sf.net/sfu/intel-dev2devmar _______________________________________________ Genode-main mailing list Genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main