All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Oleksiy Obitotskyi -X (oobitots - GLOBALLOGIC INC@Cisco)" <oobitots@cisco.com>
To: "bitbake-devel@lists.openembedded.org"
	<bitbake-devel@lists.openembedded.org>
Cc: "Taras Kondratiuk \(takondra\)" <takondra@cisco.com>,
	"Ruslan Bilovol -X \(rbilovol - GLOBALLOGIC INC at Cisco\)"
	<rbilovol@cisco.com>
Subject: nativesdk dependencies on shared packages
Date: Tue, 1 Oct 2019 11:23:36 +0000	[thread overview]
Message-ID: <1569929018481.70045@cisco.com> (raw)

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

Hi,


We have situation when MACHINE value change affect nativesdk packages (thud but the same situation was on krogoth).

MACHINE="x86" bitbake nativesdk-<package> -> build package and dependencies x86
MACHINE="x86-64" bitbake nativesdk-<package> -> build package and dependencies for x86-64
and finally
MACHINE="x86" bitbake nativesdk-<cpackage> -> a lot of setscene functons executed for nativesdk packages

MACHINE value affects BASELIB. For x86-64 we override BASELIB = lib64.
For x86 BASELIB = lib. baselib for cross/natviesdk ramains unchanged (lib).

# $BASELIB
#   set <>/openembedded-core/meta/conf/bitbake.conf:12
#     "lib"
# pre-expansion value:
#   "lib"
BASELIB="lib"

# $BASELIB [2 operations]
#   set <>/openembedded-core/meta/conf/bitbake.conf:12
#     "lib"
#   set <>/x86-64-platforms.inc:22
#     "lib64"
# pre-expansion value:
#   "lib64"
BASELIB="lib64"

Tracking dependencies shows that nativesdk-<package> depends on gcc-crosssdk which depend on
shared gcc-source package. And gcc-source tasks hash values (starting from from gcc-source.do_patch) are different for
x86 and x86-64 (due to baselib), so nativesdk-<package> task stamp signature deps part depends on gcc-source tasks hash

and also become different if we change MACHINE.


Technically  it can be fixed with tweaking sstate_rundepfilter - but it's not generic solution.

Is there any way to avoid rebuilding nativesdk packages that depend on shared packages (e.g. gcc-source)?


Regards,

Oleksiy

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

             reply	other threads:[~2019-10-01 11:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-01 11:23 Oleksiy Obitotskyi -X (oobitots - GLOBALLOGIC INC@Cisco) [this message]
2019-10-15  9:01 ` nativesdk dependencies on shared packages Oleksiy Obitotskyi -X (oobitots - GLOBALLOGIC INC@Cisco)

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=1569929018481.70045@cisco.com \
    --to=oobitots@cisco.com \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=rbilovol@cisco.com \
    --cc=takondra@cisco.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 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.