On Tue, 2012-01-03 at 21:20 -0500, Colin Walters wrote: > On Tue, 2012-01-03 at 16:53 -0800, Saul Wold wrote: > > > The flex and bison configure scripts use AC_PATH_PROG to get a > > > full path to m4 and embed this in config.h (and then to the > > > generated binary), but this blows up when the m4 binary is in a > > > temporary staging directory. > > > > > > Since we are always shipping GNU m4, just set M4=m4 at configure > > > time so we don't use a hardcoded path. > > > > > > This is an equivalent to what already exists in autoconf.bb. > > > > > > > > This should really be posted to [email protected]. > > I CC'd, hopefully won't be rejected as I'm not yet a subscriber. > > > Don't you loose the setting of BISON_PKGDATADIR in this case? Does that > > need to be poart of the EXTRA_OECONF? > > Good catch - I'll double check, but I doubt it's necessary. From the > bison source: > > char const * > compute_pkgdatadir (void) > { > char const *pkgdatadir = getenv ("BISON_PKGDATADIR"); > return pkgdatadir ? pkgdatadir : PKGDATADIR; > } > > For us though PKGDATADIR should be enough I think.
For on target device development, yes. For use in bison-native, its not enough unfortunately as it gets added into the sstate packages and those may end up installed at a different location. I like the idea of simplifying looking for m4 though. Cheers, Richard _______________________________________________ Openembedded-core mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
