On Tue, 2012-07-17 at 17:34 -0700, Saul Wold wrote: > It seems to be getting the native sysroot python instead of the more > correct "#! /usr/bin/env python", this is causing a dependency failure. > > If you could look at this please.
I ran into this a while ago with flex/bison: https://lists.yoctoproject.org/pipermail/poky/2012-January/007403.html Apparently the "correct" fix is to set an environment variable like e.g. PYTHON="/usr/bin/env python" ./configure --prefix=foo ? That seems fairly gross though. Some more generic solution would be nice...I don't have any great ideas offhand though. I wonder if there's any actual use case for hardcoding the paths found at build time into the generated binaries. See also: https://bugzilla.gnome.org/show_bug.cgi?id=650763 https://bugzilla.gnome.org/show_bug.cgi?id=670718 _______________________________________________ Openembedded-core mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
