Thanks, this version built for me on that system where it was failing
before (I haven't tried to rebuild world, just gettext).
On Wed, Jan 24, 2018 at 12:09 AM, Burton, Ross
wrote:
> Yeah, I managed to typo. Latest ross/mut has a new version.
>
> Ross
>
> On 23 January
Yeah, I managed to typo. Latest ross/mut has a new version.
Ross
On 23 January 2018 at 22:29, Martin Jansa wrote:
> The
> --without-included-libunistring=
> change there
>
> -PACKAGECONFIG[libunistring] = "--without-included-libunistri
>
The
--without-included-libunistring=
change there
-PACKAGECONFIG[libunistring] = "--without-included-
libunistring,--with-included-libunistring,libunistring"
+PACKAGECONFIG[libunistring] = "--without-included-
libunistring=${STAGING_LIBDIR}/..,--with-included-libunistring,libunistring"
looks
Hi Martin,
I've a patch at the top of poky-contrib:ross/mut which hopefully fixes
this. It's a bit more invasive than I'd like but this is gettext and I'm
still at least partially sane, so that's a win as far as I'm concerned.
I've a build running now but touching gettext causes a rebuild of
This is causing QA errors:
ERROR: gettext-0.19.8.1-r0 do_package_qa: QA Issue: gettext:
/work/corei7-64-poky-linux/gettext/0.19.8.1-r0/packages-split/gettext/usr/lib/gettext/hostname
contains probably-redundant RPATH /usr/lib/../lib
gettext:
* add --with-*-prefix variables to prevent configure trying to search in host
paths
* fixes:
ERROR: This autoconf log indicates errors, it looked at host include and/or
library paths while determining system capabilities.
gettext/0.19.8.1-r0/build/gettext-tools/config.log:cc1: warning: