All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Aníbal Limón" <anibal.limon@linux.intel.com>
To: Matt Madison <matt@madison.systems>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/2] Debian multilib packaging fixes
Date: Wed, 16 Dec 2015 09:50:58 -0600	[thread overview]
Message-ID: <56718862.80803@linux.intel.com> (raw)
In-Reply-To: <CAGgRHJptKNTkhDi5s9F1S821PG5apBDtW4mG7anGqA84m5d7kw@mail.gmail.com>

Hi Matt,

I tried to do again without your patches and the problem appears, seems
to be an older problem.

Regards,
	alimon

On 12/16/2015 07:31 AM, Matt Madison wrote:
> On Tue, Dec 15, 2015 at 2:23 PM, Aníbal Limón
> <anibal.limon@linux.intel.com> wrote:
>> Hi Matt,
>>
>> Trying to build core-image-sato with qemux86-64 and multilib enabled an
>> errors appear (see attached log), next the config.
> 
> OK, yep, I can reproduce this.  I'll investigate further.
> 
> Thanks,
> -Matt
> 
> 
>>
>> MACHINE ??= "qemux86-64"
>>
>> IMAGE_INSTALL_append = " lib32-connman"
>> require conf/multilib.conf
>> MULTILIBS = "multilib:lib32"
>> DEFAULTTUNE_virtclass-multilib-lib32 = "x86"
>> PACKAGE_CLASSES ?= "package_deb"
>> EXTRA_IMAGE_FEATURES = "debug-tweaks package-management"
>>
>> Kind regards,
>>         alimon
>>
>>
>> On 12/15/2015 01:28 PM, Matt Madison wrote:
>>> On Tue, Dec 15, 2015 at 9:29 AM, Aníbal Limón
>>> <anibal.limon@linux.intel.com> wrote:
>>>> Hi Matt,
>>>>
>>>> I'm starting to look at your patches, in what arches/combinations you
>>>> test the patches?
>>>
>>> I've been working on a BSP layer for the jetson-tx1, which is
>>> aarch64/armv7a-hf, so that's what I've been testing with.  The BSP
>>> defs are in https://github.com/madisongh/meta-tegra.
>>>
>>> Thanks,
>>> -Matt
>>>
>>>
>>>>
>>>> Kind regards,
>>>>         alimon
>>>>
>>>>
>>>> On 12/06/2015 11:25 AM, Matt Madison wrote:
>>>>> I ran into sevearl issues while trying to build an ARM multilib rootfs
>>>>> using Debian packaging.  After several go-rounds, it looked like the
>>>>> cleanest solution was to tweak how DPKG_ARCH gets constructed and
>>>>> to have the DpkgPM class in oe/package_manager.py use that variable
>>>>> to locate multilib variants (similar to RpmPM).  I also took the
>>>>> liberty of expanding the Debian architecture mappings so the names
>>>>> align better with what's documented on the Debian wiki, for those
>>>>> cases where a direct mapping is possible.
>>>>>
>>>>> Matt Madison (2):
>>>>>   package_deb.bbclass, cross-canadian.bbclass: DPKG_ARCH mapping
>>>>>     function
>>>>>   package_manager.py: fixes for multilib deb packaging builds
>>>>>
>>>>>  meta/classes/cross-canadian.bbclass |  2 +-
>>>>>  meta/classes/package_deb.bbclass    | 35 +++++++++++++++++++++++++----------
>>>>>  meta/lib/oe/package_manager.py      | 17 +++++++++++------
>>>>>  3 files changed, 37 insertions(+), 17 deletions(-)
>>>>>


  reply	other threads:[~2015-12-16 15:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-06 17:25 [PATCH 0/2] Debian multilib packaging fixes Matt Madison
2015-12-06 17:25 ` [PATCH 1/2] package_deb.bbclass, cross-canadian.bbclass: DPKG_ARCH mapping function Matt Madison
2015-12-06 17:25 ` [PATCH 2/2] package_manager.py: fixes for multilib deb packaging builds Matt Madison
2015-12-15 17:29 ` [PATCH 0/2] Debian multilib packaging fixes Aníbal Limón
2015-12-15 19:29   ` Matt Madison
     [not found]   ` <CAGgRHJqibg_vCYzFp_nQktE4kEcMYe1SMWrz=UH0Up0Q2vuXmg@mail.gmail.com>
2015-12-15 22:23     ` Aníbal Limón
2015-12-16 13:31       ` Matt Madison
2015-12-16 15:50         ` Aníbal Limón [this message]
2015-12-16 16:33           ` Matt Madison
2015-12-17 20:23             ` Matt Madison

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=56718862.80803@linux.intel.com \
    --to=anibal.limon@linux.intel.com \
    --cc=matt@madison.systems \
    --cc=openembedded-core@lists.openembedded.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.