Hi Paul,
welcome to the list and thanks for the valuable feedback!
if your Ubuntu GCC version is 4.7.x, you need to apply the patch from this bugtracker issue: https://github.com/genodelabs/genode/issues/550
Yep, manually applying the patch make the launchpad window to work. Thanks!
That said, I was using the Genode toolchain which is gcc 4.7.2 from: genode-toolchain-12.11-x86_64.tar.bz2 by using "$ export PATH=/usr/local/genode-gcc/bin:$PATH" after extracting it in /
And I was merely following the doc: README suggesting to read doc/getting_started.txt which was suggesting to: ! cd <genode-dir> ! ./tool/create_builddir linux_x86 BUILD_DIR=build.lx
The new build directory is called 'build.lx' and configured for the 'linux_x86' platform. To give Genode a try, build and execute a simple demo scenario via:
! cd build.lx ! make run/demo
I believed that this bug would be encounter by almost every new people using the current version. And that a 12.11.1 new release file should have been put on Sourceforge for people to avoid it.
It is unfortunate that this issue was resolved just after the release. For each release, we test Genode on various Linux systems, but apparently, none of the regular developers and testers had switched to the just released Ubuntu version at that time.
We haven't backported bug fixes to release snapshots, yet. So I'm a bit hesitant to start doing this.
As far as I know, most people use Genode from the Git repository where this issue is fixed. if you like to engage more with Genode, I'd highly recommend you to use the current master branch of Genode instead of a downloaded tarball:
https://github.com/genodelabs/genode/
Maybe we should make this point more clear in the documentation?
BTW, I would have liked it to be more clear that I needed to extract the toolchain in / (which seems a bit weird to me, would have expected to put it in the same directory as Genode).
That's a good point. I have slightly changed the paragraph about installing the prebuilt tool chain:
https://github.com/genodelabs/genode/commit/d27cb94702b7eb9dc623b41555663ef3...
I begin to doubt that the: $ export PATH=/usr/local/genode-gcc/bin:$PATH since the toolchain have it's own name: genode-x86-g++ genode-x86-gcc
Setting the PATH variable is not needed because the build system uses the tool prefix "/usr/local/genode-gcc/bin/genode-x86-" by default. (see 'base/etc/tools.conf'). If you like to place the tool chain somewhere else, the 'CROSS_DEV_PREFIX' can be overridden a local version of a 'tools.conf' file in your '<build-dir>/etc/' directory.
Can you give me the pointer where you picked up the information to add the tool-chain location to your PATH? I'd like to fix that.
Also, notre that the : [init] Could not open file "ld.lib.so" is still there in the now working version:
Even though this looks like an error, it is just a diagnostic message. Because the demo scenario does not use any dynamically linked binaries, a dynamic linker is not needed. So the message is not critical here. I agree that it would be nice to not print the message in this case. However, at the point where init prints the message, it does not yet know, whether or not there is any dynamically linked binary present. So it cannot decide about suppressing the message. Sorry for the confusion. If you have a good idea how to deal with it in a better way, this would be welcome. :-)
Cheers Norman