From: richard.purdie@linuxfoundation.org
To: Tom Rini <trini@konsulko.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/2] vim: Update to 8.1.1198
Date: Tue, 23 Apr 2019 23:22:14 +0100 [thread overview]
Message-ID: <e6b4feb2584669c83dabbf50761f2e68b990140f.camel@linuxfoundation.org> (raw)
In-Reply-To: <20190423220106.GA30419@bill-the-cat>
On Tue, 2019-04-23 at 18:01 -0400, Tom Rini wrote:
> On Tue, Apr 23, 2019 at 04:02:49PM +0100, Richard Purdie wrote:
> > On Sun, 2019-04-21 at 13:57 -0400, Tom Rini wrote:
> > > This brings us to the current version of vim.
> > >
> > > Signed-off-by: Tom Rini <trini@konsulko.com>
> > > ---
> > > meta/recipes-support/vim/{vim-tiny_8.1.1017.bb => vim-
> > > tiny_8.1.1198.bb} | 0
> > > meta/recipes-support/vim/{vim_8.1.1017.bb =>
> > > vim_8.1.1198.bb} | 2 +-
> > > 2 files changed, 1 insertion(+), 1 deletion(-)
> > > rename meta/recipes-support/vim/{vim-tiny_8.1.1017.bb => vim-
> > > tiny_8.1.1198.bb} (100%)
> > > rename meta/recipes-support/vim/{vim_8.1.1017.bb => vim_8.1.1198.bb}
> > > (98%)
> >
> > https://autobuilder.yoctoproject.org/typhoon/#/builders/40/builds/527
>
> Does the current version even work in this case? Digging down into
> https://autobuilder.yoctoproject.org/typhoon/#/builders/40/builds/527/steps/7/logs/step1b
> there's a certain level of "how does that even work today then?" that
> springs to mind.
>
> I need a few more details to know how to reproduce this locally as I
> don't see whatever must be in site.conf/etc to turn regular poky into
> no-x11. The errors are also around iconv stuff so maybe nls is also
> removed here? Thanks!
perhaps simpler, qemux86-world also failed:
https://autobuilder.yoctoproject.org/typhoon/#/builders/52/builds/515
with:
| /home/pokybuild/yocto-worker/qemux86-world/build/build/tmp/work/i586-
poky-linux/vim/8.1.1198-r0/recipe-sysroot-native/usr/bin/msgfmt: Cannot
convert from "ISO-8859-2" to "UTF-8". msgfmt relies on iconv(), and
iconv() does not support this conversion.
| make[2]: *** [gvim.desktop] Error 1
So perhaps there is host contamination and this works one some build
machine setups but not more minimal ones?
The build configuration hasn't changed, just the new version upgrade
and the other patch. I suppose its possible it depends which of our
workers its built upon but that seems unlikely for two world failures
(no-x11 is also a world failure).
Cheers,
Richard
next prev parent reply other threads:[~2019-04-23 22:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-21 17:57 [PATCH 1/2] vim: Rework to not rely on relative directories Tom Rini
2019-04-21 17:57 ` [PATCH 2/2] vim: Update to 8.1.1198 Tom Rini
2019-04-23 15:02 ` Richard Purdie
2019-04-23 22:01 ` Tom Rini
2019-04-23 22:22 ` richard.purdie [this message]
2019-04-23 22:29 ` Tom Rini
2019-04-24 1:17 ` Tom Rini
2019-04-24 5:24 ` Tim Orling
2019-04-24 12:01 ` Tom Rini
2019-04-24 7:40 ` richard.purdie
2019-04-24 11:29 ` Tom Rini
2019-04-24 13:50 ` richard.purdie
2019-04-24 13:53 ` Tom Rini
2019-04-24 21:08 ` [RFC DO NOT APPLY][PATCH 3/2] vim: Add a work-around for some locale issues Tom Rini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e6b4feb2584669c83dabbf50761f2e68b990140f.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=trini@konsulko.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.