[tz_vmm] Build error (#2)

[Martin Stein]

Hey Yevgeny,

Am 17.04.2016 um 09:09 schrieb Yevgeny:
> Yes, I've already tried: make run/tz_vmm, however, it doesn't create the
> *uImage* in the *var/run/tz_vmm/* directory.

A run script merely contains the common set-up of a Genode scenario.
Thus, it doesn't create bootloader-specific output like a uImage. For
such customization there is the file <builddir>/etc/build.conf. In your
case you would need to add a line:

RUN_OPT += --include image/uboot

This is also documented in [1]. I think it would be the best if follow
the tutorial in there. It describes the complete process how to create a
bootable SD card with the tz_vmm script.

> I started off with this tutorial:
> https://github.com/inversepath/usbarmory/wiki/Genode-OS and everything
> went fine untill this point: cp var/run/tz_vmm/uImage to SD_CARD. Err:
> no such file or directory"

The Wiki recently was updated as the previous version seemed to cause
misconceptions. Please check out the new version.

> I've taken the following steps provided in the first link of you msg.
> export TARGET_DEV=/dev/sdX
> cd genode-16.02
> ./tool/create_builddir hw_usb_armory
> ./tool/create_uboot hw_usb_armory
> sudo dd if=contrib/uboot/build/hw_usb_armory/mmc_img of=$TARGET_DEV
> bs=1K seek=1 conv=fsync
> cd genode-16.02/build/hw_usb_armory/
> echo "RUN_OPT += --include image/uboot" >> etc/build.conf
> make run/tz_vmm
>
> and ended up with the following error:
>
> couldn't execute "mkimage": no such file or directory

I assume thta this is related to the above problems. Could please give
it another try?
>
> if instead of echo "RUN_OPT += --include image/uboot" >> etc/build.conf
> I change RUN_OPT = --include boot_dir/hw to RUN_OPT = --include
> boot_dir/hw image/uboot the build succeeds but no uImage gets created.

There is missing an --include after boot_dir/hw.

> I'm using clean Ubuntu 15.10 VM, Genode15.05 x86-64 tool chain, and the
> latest version of Genode 16.02

That should be fine. If you try using the wrong tool chain, the build
system should tell you and stop.

Cheers,
Martin

[1] https://github.com/genodelabs/genode/blob/master/repos/os/run/tz_vmm.run



Am 08.04.2016 um 11:08 schrieb Martin Stein:
> Hey Yevgeny,
> 
> If you only want to try the default setup, you can simply use the run
> script [1] by doing 'make run/tz_vmm' in your build directory. The
> script automatically downloads a precompiled Linux image. Have you tried
> that?
> 
> If you're really interested in customizing your Normal World Linux,
> there is also a link in the run script to a detailed explanation on how
> to compile the images [2]. I assume that your approach fails because of
> the wrong toolchain. Does the tutorial fix your problem?
> 
> Cheers,
> Martin
> 
> [1] https://github.com/genodelabs/genode/blob/master/repos/os/run/tz_vmm.run
> 
> [2]
> https://github.com/m-stein/genode_binaries/blob/master/tz_vmm/usb_armory/README
> 
> Am 05.04.2016 um 21:49 schrieb Yevgeny:
>> I'm trying to compile Genode for usbarmory. After executing this command
>> *make ARCH=arm zImage LOADADDR=0x80008000 modules* from the root dir of
>> the downloaded linux kernel, it gives me the following error.
>>
>> Makefile:664: Cannot use CONFIG_CC_STACKPROTECTOR_STRONG:
>> -fstack-protector-strong not supported by compiler
>> CHK include/config/kernel.release
>> CHK include/generated/uapi/linux/version.h
>> CHK include/generated/utsrelease.h
>> make[1]: 'include/generated/mach-types.h' is up to date.
>> CC kernel/bounds.s
>> gcc: error: unrecognized argument in option ‘-mabi=apcs-gnu’
>> gcc: note: valid arguments to ‘-mabi=’ are: ms sysv
>> gcc: error: unrecognized command line option ‘-mlittle-endian’
>> gcc: error: unrecognized command line option ‘-mapcs’
>> gcc: error: unrecognized command line option ‘-mno-sched-prolog’
>> Kbuild:35: recipe for target 'kernel/bounds.s' failed
>> make[1]: *** [kernel/bounds.s] Error 1
>> Makefile:980: recipe for target 'prepare0' failed
>> make: *** [prepare0] Error 2
>>
>> Please advise
>>
>> —
>> You are receiving this because you are subscribed to this thread.
>> Reply to this email directly or view it on GitHub
>> <https://github.com/m-stein/linux/issues/2>
>>