Hi,
It appears that the 16.05 build uses a new environment parameter
BASE_HW_DIR, which cause a build on a Cortex A9 based platform to fail
in lib/mk (that is, base-hw/lib/mk/spec/cortex_a9.h)
bob@tegra-ubuntu:/Work/Genode/Builds/16.05/437x$ make run/printf
including /Work/Genode/genode-16.05/tool/run/boot_dir/hw
including /Work/Genode/genode-16.05/tool/run/image/uboot
including /Work/Genode/genode-16.05/repos/base/run/printf.run
building targets: core init test/printf
spawn make core init test/printf
make[1]: Entering directory `/Work/Genode/Builds/16.05/437x'
checking library dependencies...
/Work/Genode/genode-16.05/repos/base-hw/lib/mk/spec/cortex_a9/core.inc:25:
/lib/mk/spec/smp/core.inc: No such file or directory
/Work/Genode/genode-16.05/repos/base-hw/lib/mk/spec/cortex_a9/core.inc:26:
/lib/mk/spec/arm_v7/core.inc: No such file or directory
make[3]: *** No rule to make target `/lib/mk/spec/arm_v7/core.inc'. Stop.
make[2]: *** [gen_prg_rule] Error 2
make[1]: *** [traverse_dependencies] Error 1
make[1]: Leaving directory `/Work/Genode/Builds/16.05/437x'
Error: Genode build failed
make: *** [run/printf] Error 252
This can be fixed by including in cortex_a9.h the line;
BASE_HW_DIR := $(REP_DIR)
But why is it necessary to have this new variable?
Bob Stewart
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
genode-main mailing list
genode-main@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/genode-main
