All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mike Jones" <proclivis@gmail.com>
To: proclivis@gmail.com
Cc: Richard Purdie <richard.purdie@linuxfoundation.org>,
	poky@lists.yoctoproject.org
Subject: Re: [poky] win create failing at mcopy #poky #raspberrypi
Date: Tue, 11 May 2021 09:50:18 -0600	[thread overview]
Message-ID: <0C95CDCC-9F67-415C-9C0B-7B868B18EF24@gmail.com> (raw)
In-Reply-To: <167E049418E547AC.28983@lists.yoctoproject.org>


> On May 11, 2021, at 6:59 AM, Mike Jones via lists.yoctoproject.org <proclivis=gmail.com@lists.yoctoproject.org> wrote:
> 
> 
>>> On May 11, 2021, at 4:20 AM, Richard Purdie <richard.purdie@linuxfoundation.org> wrote:
>>> 
>>> On Mon, 2021-05-10 at 18:54 -0600, Mike Jones wrote:
>>> I have a little more info on this and a more specific question.
>>> 
>>> I copied the mtools code and hooked it into the layer so I could put in debug statements.
>>> 
>>> The problem occurs in charsetConv.c in the function cp_open, when it tries to do an iconv_open using
>>> “CP850”, which fails.
>>> 
>>> I ran “iconv —list” to see what it can convert, and CP850 is not listed.
>>> 
>>> To prove this is the problem, I hardcoded the iconv_open with “ASCII” and bit bake can go all the way
>>> through and “wic create” works properly.
>>> 
>>> So I ran iconv —version and saw it was “GNU libc 2.31” so I poked around those layers.
>>> 
>>> Best I can guess is this line from the mtools layer should tell the libc to provide CP850 via this line:
>>> 
>>> RDEPENDS_${PN}_libc-glibc = "glibc-gconv-ibm850”
>>> 
>>> Except that that is for runtime, and this is build time.
>>> 
>>> So I am not sure how glibc decides what converters are used. Is it just a set of defaults? Is there a layer
>>> somewhere defining them I could not find?
>>> 
>>> It seems that somewhere along the way, mtools changed its default to use 850, and it is not compatible
>>> anymore.
>>> 
>>> The solution is probably to tell glibc to provide CP850.
>>> 
>>> Does anyone know how to do that?
>> 
>> Which version of Yocto Project are you using? Are you using buildtools-tarball 
>> or uninative in your build?
> 
> I run poky/scripts/install-buildtools with no command line options.
> 
> It contains these defaults:
> 
> DEFAULT_INSTALL_DIR = os.path.join(os.path.split(scripts_path)[0],'buildtools')
> DEFAULT_BASE_URL = 'http://downloads.yoctoproject.org/releases/yocto'
> DEFAULT_RELEASE = 'yocto-3.2_M3'
> DEFAULT_INSTALLER_VERSION = '3.1+snapshot'
> DEFAULT_BUILDDATE = '20200923'
> 
> I see I can use command line options to use a different release if you have guidance on what to use.

After tweaking the script to change sha256 to sha256sum and removing one \s from the regular expression, I installed 3.2.3 and I will bitbake and see it it works.

I am guessing the script changes are due to an older version of poky, but poky is part of the openbmc project clone, not something we manually clone from a yocto repository.

If this works, I’ll have to address that issue on the openbmc listserv.

Mike

> 
> Mike
> 
>> 
>> I suspect you need a newer buildtools-tarball version which includes CP850.
>> 
>> Cheers,
>> 
>> Richard
>> 
> 
> 
> 

       reply	other threads:[~2021-05-11 15:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <167E049418E547AC.28983@lists.yoctoproject.org>
2021-05-11 15:50 ` Mike Jones [this message]
2021-05-03 17:37 win create failing at mcopy #poky #raspberrypi proclivis
2021-05-11  0:54 ` [poky] " proclivis
2021-05-11 10:20   ` Richard Purdie
2021-05-11 12:59     ` Mike Jones
     [not found]   ` <167DFBEC8E48E145.20137@lists.yoctoproject.org>
2021-05-11 10:31     ` Richard Purdie

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=0C95CDCC-9F67-415C-9C0B-7B868B18EF24@gmail.com \
    --to=proclivis@gmail.com \
    --cc=poky@lists.yoctoproject.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.