On 2014年05月15日 01:45, Christopher Larson wrote:
On Wed, May 14, 2014 at 2:30 AM, Wenlin Kang <wenlin.k...@windriver.com <mailto:wenlin.k...@windriver.com>> wrote:When build bash, a error occurs, the cause is that autotools uses improper Makefile.in.in <http://Makefile.in.in> which is from path/gettext/po/ but not bash itself in bash/po/,so to avoid some error to occur, we should use package itself Makefile.in.in <http://Makefile.in.in> file if it has. Signed-off-by: Wenlin Kang <wenlin.k...@windriver.com <mailto:wenlin.k...@windriver.com>>This will cause breakage when the shipped Makefile.in.in <http://Makefile.in.in> gettext version mismatches with the gettext-native/gettext we built.
but if we directly use gettext-native/gettext/Makefile.in.in just as now, for bash, it do occur some problem, can't get correct value of PACKAGE, VERSION due to use incorrect variable name(the right should is PACKAGE_NAME, PACKAGE_VERSION) , can't get BUILD_DIR, and can't get po-directories(it indeed isn't exist) in bash/po/Makefile. these all can trigger a build error in bash/po , so, whether we can have a much well solution for it, can you have some good advices, thanks?
-- Christopher Larson clarson at kergoth dot com Founder - BitBake, OpenEmbedded, OpenZaurus Maintainer - Tslib Senior Software Engineer, Mentor Graphics
-- Thanks, Wenlin Kang
-- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
