Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Connor Smith <connor.smith@ni.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: Library Patches Causing Many Packages to Rebuild
Date: Fri, 10 Jul 2015 12:09:23 -0500	[thread overview]
Message-ID: <559FFC43.4030505@ni.com> (raw)
In-Reply-To: <CAJTo0LZwXTDEKtR8+3EHfdEpMbB4P9nxyaC1odqW_dGHz5svAQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1100 bytes --]



On 07/10/2015 04:20 AM, Burton, Ross wrote:
>
> On 10 July 2015 at 00:24, Connor Smith <connor.smith@ni.com> wrote:
>
>     rpm-native appears to be recompiling because the do_populate_sysroot
>     hash is changing for the native versions of openssl and python. I'm not
>     sure why either of these tasks are changing.
>
>
> This is likely the source of a lot of the rebuilds.  openssl was changed, openssl-native rebuilds, causing a rebuild of rpm-native, which likely causes a re-package of everything.
>
> If this doesn't explain the situation then attaching the cooker log demonstrating the problem might help identify it.
>
> Ross

Ah, that makes sense. I investigated some more, and the do_package task
has a hard-coded dependency on rpm-native. Removing this dependency and
rebuilding resolved the issue; the only ipks being rebuilt now are from
packages that depend on openssl and need to be recompiled.

Should this dependency be based off PACKAGE_CLASSES, or is it necessary
to always depend on rpm-native? We're using opkg, not rpm.

Thanks,
Connor Smith


[-- Attachment #2: Type: text/html, Size: 1743 bytes --]

  reply	other threads:[~2015-07-10 17:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-09 23:24 Library Patches Causing Many Packages to Rebuild Connor Smith
2015-07-10  9:20 ` Burton, Ross
2015-07-10 17:09   ` Connor Smith [this message]
2015-07-10 19:19     ` Burton, Ross

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=559FFC43.4030505@ni.com \
    --to=connor.smith@ni.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox