Summary: | bash cross-compile dies in configure | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Daniel Glaser <daniel.glaser> |
Component: | Current packages | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED UPSTREAM | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Other | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Daniel Glaser
2006-09-23 07:59:30 UTC
export bash_cv_have_mbstate_t=yes bash has more fundamental cross-compiling issues (proper signal generation) that upstream is aware of ... if you want to be sane, you need to build bash on the target hardware and export ac_cv_func_setvbuf_reversed=no But how can I handle it correctly by ROOT="/somewhat" PORTAGE_CONFIGROOT="/somewhat" emerge bash If I put it in /somewhat/etc/make.conf everything works fine for cross-compiling it on my machine, but is it the best way to do so? Compiling it on the target is not possible for production use, because it is a small embedded system with ppc405 and about 32MB Ram. There are other packages that doesn't compile without interruption and I hope, that this will be as easy as this solution. But thanks for your reply. e-mail the gentoo-embedded mailing list |