By default, the configure script used for the ebuild for version 2.3.0 ignores the build host. With the following (a diff between the edited ebuild and the original), the build will use the correct CHOST-specific compiler instead of a generic one. 307d306 < --host="${CHOST}" \
The patch is reversed, plus please use unified diffs, not the unreadable context ones.
Created attachment 132212 [details] The unified diff you want/need
Are you sure this changes anything at all? Your diff adds this to the ooo-build configure-script which doesn't check for host-settings at all, see: http://svn.gnome.org/viewcvs/ooo-build/trunk/configure.in?revision=10389&view=markup The openoffice-configure-script itself indeed has a host-check, but what do you gain by altering it? Which problem does it solve?
(In reply to comment #3) > Are you sure this changes anything at all? Your diff adds this to the ooo-build > configure-script which doesn't check for host-settings at all, see: > > http://svn.gnome.org/viewcvs/ooo-build/trunk/configure.in?revision=10389&view=markup > > The openoffice-configure-script itself indeed has a host-check, but what do you > gain by altering it? Which problem does it solve? > What I gain is that this way, if CC is invoked it invokes (on my box) "i686-pc-linux-gnu-gcc" instead of simply "cc" or "gcc". With the old way, it could get messed up if you were were doing something like cross-compiling and called the wrong compiler (the system one instead of the cross-compiler or vice-versa if the cross-compiler was somehow early in your $PATH).
I've added this, thanks for the bug report
