The depends flag isn't automatically updated to include the MLPREFIX the way the
DEPENDS variable is by multilib_global, so this must include it directly.
JIRA: SB-21758
Signed-off-by: Christopher Larson <chris_larson@mentor.com>
We needed a `${MLPREFIX}` reference here to align with the behavior of
external-toolchain.bbclass.
JIRA: SB-21758
Signed-off-by: Christopher Larson <chris_larson@mentor.com>
This bug effectively broke use of MULTILIBS with external oe sdk toolchains, but
this fixes it.
JIRA: SB-21758
Signed-off-by: Christopher Larson <chris_larson@mentor.com>
* origin/SB-21854:
libgcc-external: add needed entries to DEBUG_PREFIX_MAP
gcc-runtime-external: override REL_S
gcc-no-shared-source.inc: bring back fetch/unpack
external-toolchain.bbclass: inherit external-debugsrc
external-toolchain.bbclass: stop overriding S, we need it for debugsrc
external-debugsrc.bbclass: use oe.path.copyhardlinktree
external-debugsrc.bbclass: add class
copydebugsources_extra.bbclass: add class
oprofile-external: avoid too-greedy FILES pattern
These ensure that external-debugsrc.bbclass and package.bbclass pick up
the needed libgcc debug sources.
JIRA: SB-21854
Signed-off-by: Christopher Larson <chris_larson@mentor.com>
This is needed to fix the debug prefix map, as we want to be looking for
gcc and gcc-runtime, not gcc-runtime-external.
JIRA: SB-21854
Signed-off-by: Christopher Larson <chris_larson@mentor.com>
external-debugsrc copies debug sources from the external toolchain in
do_unpack, so we need that task to exist.
JIRA: SB-21854
Signed-off-by: Christopher Larson <chris_larson@mentor.com>
We want debug sources for all the target external toolchain recipes, so inherit
it here.
JIRA: SB-21854
Signed-off-by: Christopher Larson <chris_larson@mentor.com>
We need to be able to copy sources from the external toolchain into it in
do_unpack, then back out into the install area in do_install.
Note that attempts were made to bypass this indirection by having do_package
directly copy sources from the external toolchain, and while this did function,
it results in pseudo failures breaking the build. Further investigation could be
done on this in the future.
JIRA: SB-21854
Signed-off-by: Christopher Larson <chris_larson@mentor.com>
This class copies debug sources out of the external toolchain, obeying the paths
in DEBUG_PREFIX_MAP, the same way do_package does to copy those sources into the
src binary package. Between the two, this redistributes the debug sources in the
appropriate -src packages as it would for non-external recipes.
JIRA: SB-21854
Signed-off-by: Christopher Larson <chris_larson@mentor.com>
This class, which comes from our toolchain builds, worked around the inability
of package.bbclass to fetch sources from work-shared, but as a consequence, also
works around issues with using the debug sources we pull from the external
toolchain.
JIRA: SB-21854
Signed-off-by: Christopher Larson <chris_larson@mentor.com>
Using `${bindir}/op*` was also picking up files that had nothing to do
with oprofile, so use an explicit list to prevent this.
JIRA: SB-21854
Signed-off-by: Christopher Larson <chris_larson@mentor.com>
This expansion resulted in absolute filesystem paths in the signature rather
than the unexpanded forms.
JIRA: SIEJIR-6415
Signed-off-by: Christopher Larson <chris_larson@mentor.com>
TUNE_CCARGS, while most appropriate, has a `vardepvalue` set which
causes its fully expanded version to end up in checksums, not the
unexpanded version, which causes a problem if that value includes an
absolute path. Place it in TARGET_CC_ARCH instead.
JIRA: SIEJIR-6415
Signed-off-by: Christopher Larson <chris_larson@mentor.com>
Without this, we get this failure when using an external toolchain:
ERROR: Nothing PROVIDES 'gcc-source-11.3.0-13.0.1'. Close matches:
gcc-source-11.3.0
Signed-off-by: Christopher Larson <chris_larson@mentor.com>
This isn't necessary, as linux-libc-headers isn't included in the build
in this configuration anyway, and avoids a need to deal with mismatched
provides between the two recipes, ie "one provides something the other
does not".
JIRA: SB-21212
Signed-off-by: Christopher Larson <chris_larson@mentor.com>
There's no need for the linux-libc-headers provide in glibc-external, as
it doesn't get pulled into the build regardless in a non-rebuild case,
it just adds complexity.
JIRA: SB-21212
Signed-off-by: Christopher Larson <chris_larson@mentor.com>
