/data/download/gcc-linaro-7.2.1-2017.11-x86_64_arm-linux-gnueabihf/bin/arm-linux-gnueabihf-ld
-EL --defsym __L4_KIP_ADDR__= --defsym __l4sys_invoke_direct=+ --defsym
__l4sys_debugger_direct=+ --build-id -o .tmp_vmlinux1 -T
./arch/l4/kernel/vmlinux.lds --whole-archive built-in.o
--no-whole-archi
Hi l4 hackers,
../arch/l4/arm-mach-l4/l4.c:33:10: fatal error: l4/io/io.h: No such file
or directory
#include
^~~~
compilation terminated.
so I just workaround to `ln -s` manually:
build-freescale-imx6/include/l4/io/
├── io.h -> /data/project/xiangzhai/l4re/l4/pkg/io/libi
Yes, that's it. Do you have any good suggestions?于 2018-01-10 06:36:25,Adam Lackorzynski写道:Hi nico,
On Tue Jan 09, 2018 at 19:18:20 +0800, nico wrote:
> I started uvmm and found that all ram space allocated to vm are cleared.
Yes, sure. We do not want to see any other data in there, possibly
com
On Tue Jan 09, 2018 at 23:17:10 +0100, Paul Boddie wrote:
> On Tuesday 9. January 2018 01.02.58 Paul Boddie wrote:
> >
> > So, I am assuming that the compiler gets confused by the freestanding
> > assembly language definition of the function, and the object goes missing
> > in some way that then
On Tuesday 9. January 2018 01.02.58 Paul Boddie wrote:
>
> So, I am assuming that the compiler gets confused by the freestanding
> assembly language definition of the function, and the object goes missing
> in some way that then leads to the error. Of course, the above introduces
> other operation
Hi nico,
On Tue Jan 09, 2018 at 19:18:20 +0800, nico wrote:
> I started uvmm and found that all ram space allocated to vm are cleared.
Yes, sure. We do not want to see any other data in there, possibly
coming from another domain and leaking some information.
> But I do not need to do that, becau
Hi Adam, I started uvmm and found that all ram space allocated to vm are
cleared. But I do not need to do that, because uboot has loaded image file to
ram, and vm linux would use that image file. Could you tell me where the uvmm
did the cleanup? Regards, Nico_
