From: Tom Rini <trini@konsulko.com>
To: richard.purdie@linuxfoundation.org
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/2] vim: Update to 8.1.1198
Date: Wed, 24 Apr 2019 09:53:28 -0400 [thread overview]
Message-ID: <20190424135328.GX31207@bill-the-cat> (raw)
In-Reply-To: <61f5389ee7e594055a18f5ce7a2e040a2b04de90.camel@linuxfoundation.org>
[-- Attachment #1: Type: text/plain, Size: 2043 bytes --]
On Wed, Apr 24, 2019 at 02:50:51PM +0100, richard.purdie@linuxfoundation.org wrote:
> On Wed, 2019-04-24 at 07:29 -0400, Tom Rini wrote:
> > On Wed, Apr 24, 2019 at 08:40:01AM +0100,
> > richard.purdie@linuxfoundation.org wrote:
> >
> > > What does "locale -a" show for you?
> >
> > On Fedora Core 29:
> > C
> > C.utf8
> > en_AG
> > en_AG.utf8
> > en_AU
> > en_AU.iso88591
> > en_AU.utf8
> > en_BW
> > en_BW.iso88591
> > en_BW.utf8
> > en_CA
> > en_CA.iso88591
> > en_CA.utf8
> > en_DK
> > en_DK.iso88591
> > en_DK.utf8
> > en_GB
> > en_GB.iso88591
> > en_GB.iso885915
> > en_GB.utf8
> > en_HK
> > en_HK.iso88591
> > en_HK.utf8
> > en_IE
> > en_IE@euro
> > en_IE.iso88591
> > en_IE.iso885915@euro
> > en_IE.utf8
> > en_IL
> > en_IL.utf8
> > en_IN
> > en_IN.utf8
> > en_NG
> > en_NG.utf8
> > en_NZ
> > en_NZ.iso88591
> > en_NZ.utf8
> > en_PH
> > en_PH.iso88591
> > en_PH.utf8
> > en_SC.utf8
> > en_SG
> > en_SG.iso88591
> > en_SG.utf8
> > en_US
> > en_US.iso88591
> > en_US.iso885915
> > en_US.utf8
> > en_ZA
> > en_ZA.iso88591
> > en_ZA.utf8
> > en_ZM
> > en_ZM.utf8
> > en_ZW
> > en_ZW.iso88591
> > en_ZW.utf8
> > POSIX
> >
> > And then my Ubuntu 16.04 regular build env:
> > C
> > C.UTF-8
> > en_AG
> > en_AG.utf8
> > en_AU.utf8
> > en_BW.utf8
> > en_CA.utf8
> > en_DK.utf8
> > en_GB.utf8
> > en_HK.utf8
> > en_IE.utf8
> > en_IN
> > en_IN.utf8
> > en_NG
> > en_NG.utf8
> > en_NZ.utf8
> > en_PH.utf8
> > en_SG.utf8
> > en_US.utf8
> > en_ZA.utf8
> > en_ZM
> > en_ZM.utf8
> > en_ZW.utf8
> > POSIX
>
> Does vim build cleanly on the 16.04 box? My working theory was the lack
> of iso88591 locale variants may be causing some kind of issue...
Yup. I do a nodistro build of my changes before posting to be sure it
builds somewhere at least.
> Failing that can you send me the log.do_compile from a successful build
> offlist and I can compare to my failing one (or send you my failing
> compile log).
Coming up in a moment.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2019-04-24 13:53 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
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 [this message]
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=20190424135328.GX31207@bill-the-cat \
--to=trini@konsulko.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
/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.