Hi Teresa, On Wed, Sep 10, 2014 at 04:46:08PM +0200, Teresa Gámez wrote: > The defaultenv_add_base() functions adds the enviroment coming from > CONFIG_DEFAULT_ENVIRONMENT_PATH. But this is not only for > traditional enviroments, but also for external enviroments in e.g. build > systems. The external enviroment should override the enviroment set > in the board file and not the other way around. Made sure that > external enviroment is always added last. > > Signed-off-by: Teresa Gámez <t.gamez@xxxxxxxxx> So what happens is: At some point board code calls defaultenv_append() which calls defaultenv_add_base() which in turn registers all default env snippets including the one from CONFIG_DEFAULT_ENVIRONMENT_PATH. After this defaultenv_append adds the snippet passed to it. Instead you want CONFIG_DEFAULT_ENVIRONMENT_PATH to be the last instance and register it right before using the default environment in defaultenv_load(). I had some trouble understanding what was wrong and how you solved it, the above is mainly for me. I hope I find it the next time I stumble upon this ;) Something tells me this is not the last time I think about this piece of code. Ok, applied. Sascha -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | _______________________________________________ barebox mailing list barebox@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/barebox
