Hi Bahadir,
> Do you want to try our v0.5 sources, or would you rather go with the
> open git.l4dev.org sources?
I'd prefer to go with the open-source version to enable users of Genode
to give Codezero a quick try with no strings attached. With the
proprietary version, this is not possible ATM.
Hi Norman,
Do you want to try our v0.5 sources, or would you rather go with the
open git.l4dev.org sources?
Thanks,
Bahadir
On Mon, 2011-09-12 at 20:51 +0200, Norman Feske wrote:
> Hi Amit,
>
> thank you for considering my suggestions. Will you push the updates to
> git.l4dev.org?
>
> Thanks
Hi Amit,
thank you for considering my suggestions. Will you push the updates to
git.l4dev.org?
Thanks
Norman
___
codezero-devel mailing list
[email protected]
http://lists.l4dev.org/mailman/listinfo/codezero-devel_lists.l4dev.org
On Mon, 2011-09-12 at 10:25 +0530, Amit Mahajan wrote:
> On Mon, 2011-09-05 at 12:10 +0200, Norman Feske wrote:
> > Codezero expects the tool chain to be used for the kernel to not support
> > shared libraries. (this is the case for Codesourcery's arm-none-eabi
> > tool chain) Such tool chains use
On Mon, 2011-09-05 at 12:10 +0200, Norman Feske wrote:
> Codezero expects the tool chain to be used for the kernel to not support
> shared libraries. (this is the case for Codesourcery's arm-none-eabi
> tool chain) Such tool chains use to incorporate both libgcc and
> libgcc_eh into the single libg
Codezero expects the tool chain to be used for the kernel to not support
shared libraries. (this is the case for Codesourcery's arm-none-eabi
tool chain) Such tool chains use to incorporate both libgcc and
libgcc_eh into the single libgcc.a library. In contrast, for tool chains
built with '--enable
