All of lore.kernel.org
 help / color / mirror / Atom feed
From: McClintock Matthew-B29882 <B29882@freescale.com>
To: Mark Hatle <mark.hatle@windriver.com>
Cc: McClintock Matthew-B29882 <B29882@freescale.com>,
	"yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: RPM multilib package installation issue
Date: Fri, 2 Sep 2011 19:29:29 +0000	[thread overview]
Message-ID: <CAEsOVNepquHxYUJGFE9DVZ+9-SvmQQNEjamSuh50JasQf1ETVg@mail.gmail.com> (raw)
In-Reply-To: <4E6126C4.5020303@windriver.com>

FYI: ipkg appears to work fine if you have
MULTILIB_IMAGE_INSTALL and MULTILIB_PACKAGE_ARCH set.

Will file a bug shortly.

-M

On Fri, Sep 2, 2011 at 1:56 PM, Mark Hatle <mark.hatle@windriver.com> wrote:
> On 9/2/11 1:36 PM, McClintock Matthew-B29882 wrote:
>> On Fri, Sep 2, 2011 at 12:09 PM, Mark Hatle <mark.hatle@windriver.com> wrote:
>>> For everything I see, that should work.
>>>
>>> In classes/image.bbclass, RDEPENDS is augmented by the contents of
>>> IMAGE_INSTALL, LINGUAS_INSTALL, MULTILIB_IMAGE_INSTALL, and NORMAL_FEATURE_INSTALL.
>>
>> The bitbake side is fine, It's getting put into RDEPENDS and all the
>> packages are beinh built properly. RPMs are built as well.
>>
>>> The place to start looking for this is within the log.do_rootfs in the rootfs
>>> directory you are working on.  You should see something that indicates it's
>>> trying to install the "lib64-perl".  (in the case of RPM, it should eventually
>>> rename it to "perl" -- but choose the 64-bit version.)
>>
>> However, I don't see code that invokes package_rpm.bbclass properly.
>> It looks like it could work, but no where is MLPREFIX set for image.
>> There is some override or something missing on my end or in the code
>> to properly export these vars for the ML rpm install scenario.
>>
>> Further more, from what I see no where in rootfs_rpm.bbclass do we
>> pass MULTILIB_PACKAGE_INSTALL into the list of packages to be
>> installed... thus they fall off. ipk looks like it might have this
>> stuff done.
>
> This looks like a typo of some sorts:
>
> image.bbclass:RDEPENDS += "${IMAGE_INSTALL} ${LINGUAS_INSTALL}
> ${MULTILIB_IMAGE_INSTALL} ${NORMAL_FEATURE_INSTALL}"
>
> image.bbclass:export MULTILIB_PACKAGE_INSTALL ?= "${MULTILIB_IMAGE_INSTALL}"
>
> So you should be setting MULTILIB_IMAGE_INSTALL, this should feed into the
> RDEPENDS and that should in turn seed the roofs stuff..  So there looks to be a
> disconnect of some sort between the implementation of the image.bbclass and the
> individual package_*.bbclasses.
>
> (The only place I see MULTILIB_PACKAGE_INSTALL is in rootfs_ipk.bbclass.)
>
> The way the rootfs_rpm (which uses package_rpm) gets the list of things to
> install is via:
>
> package_linguas=INSTALL_PACKAGES_LINGUAS_RPM=LINGUAS_INSTALL
>
> package_to_install=INSTALL_PACKAGES_NORMAL_RPM=PACKAGE_INSTALL="${IMAGE_INSTALL}
>  ${FEATURE_INSTALL}"
>
> package_attemptonly=INSTALL_PACKAGES_ATTEMPTONLY_RPM=PACKAGE_INSTALL_ATTEMPTONLY=FEATURE_INSTALL_OPTIONAL
>
> Where you see RPM above, replace with ipk and deb and the same ordering should
> be used.  So based on that, RDEPENDS is being populated from the
> "image.bbclass", but nothing is populating the MULTILIB_IMAGE_INSTALL like it
> should be.  Either it needs to be added to the 'PACKAGE_INSTALL' or something
> similar needs to be invented and added to each of the rootfs_* types.  (Note,
> there needs to be a translation step between the definition of
> MULTILIB_IMAGE_INSTALL and where it's used.. since things like "zlib" can become
> "libz1" via name translation.  (translation happens in runtime_mapping_rename if
> I remember correctly.. in image.bbclass)
>
> I'd suggest you file a bug about this in the yocto system.  We'll get someone to
> work on it...  (I agree it's broken BTW..)  The ipk usage may turn out to be an
> example for the deb and rpm usage... but the three should continue to be in sync
> for most of it.
>
> --Mark
>
>> -M
>>
>> -M
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>


  reply	other threads:[~2011-09-02 19:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-02  7:33 RPM multilib package installation issue Xu, Dongxiao
2011-09-02 15:03 ` Mark Hatle
2011-09-02 15:40   ` McClintock Matthew-B29882
2011-09-02 15:48     ` Mark Hatle
2011-09-02 16:24       ` McClintock Matthew-B29882
2011-09-02 17:09         ` Mark Hatle
2011-09-02 18:36           ` McClintock Matthew-B29882
2011-09-02 18:56             ` Mark Hatle
2011-09-02 19:29               ` McClintock Matthew-B29882 [this message]
2011-09-02 19:40                 ` McClintock Matthew-B29882
2011-09-03  0:49   ` Xu, Dongxiao

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=CAEsOVNepquHxYUJGFE9DVZ+9-SvmQQNEjamSuh50JasQf1ETVg@mail.gmail.com \
    --to=b29882@freescale.com \
    --cc=mark.hatle@windriver.com \
    --cc=yocto@yoctoproject.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.