When EXTERNAL_TARGET_SYS != TARGET_PREFIX, which is generally the case,
we should ship symlinks with the other prefix. This is largely for
compatibility with existing scripts, but also means we don't need to
alter the variables in environment-setup, i.e. CC.
Signed-off-by: Christopher Larson <chris_larson@mentor.com>
This class will be used by the binutils and gcc cross-canadian recipes
which package and install the external toolchain binaries into the host
sysroot in the sdk.
Signed-off-by: Christopher Larson <chris_larson@mentor.com>
* general-fixes:
gcc-external{.inc,-cross}: use non-prefixed gcc_binaries
gcc-external.inc: drop unnecessary external-toolchain inherit
layer.conf: add fallback default for GCC_VERSION
gcc: Use globally set GCC_VERSION in recipes
tcmode-external: also blacklist libgfortran
tcmode-external: add prefs for gcc-runtime, libgcc-initial, libgfortran
meta-environment{,-extsdk}: don't include -B${gcc_bindir} in emitted TUNE_CC_ARCH
external-toolchain.bbclass: expand permissions beyond user
libgcc-external: drop the static files that won't be found anyway
libgfortran-external: don't package the static lib and headers
external-toolchain-cross.bbclass: drop sourcery-specific nopseudo handling
oe.external: obey EXTERNAL_FILES over FILES
oe.external: drop unneeded ,True from getVars
external-toolchain.bbclass: stop disabling strip
external-toolchain.bbclass: use PACKAGE_DEPENDS
binutils-external-cross: only link ld.bfd if necessary
This is pulled in already via external-toolchain-cross and
external-toolchain-cross-canadian.
Signed-off-by: Christopher Larson <chris_larson@mentor.com>
This is used in recipe PV variables, but is only defined when the tcmode
is loaded, so define a default for the case where it isn't sourced.
Signed-off-by: Christopher Larson <chris_larson@mentor.com>
Don't dump the -B${gcc_bindir} appended to TUNE_CCARGS and subsequently
to TARGET_CC_ARCH, since it consists of local machine toolchain paths.
Signed-off-by: Christopher Larson <chris_larson@mentor.com>
This lets one add files to be packaged beyond those being extracted from
the external toolchain, i.e. for files coming from elsewhere, or created
by do_install/do_install_extra.
Signed-off-by: Christopher Larson <chris_larson@mentor.com>
These were obsolete bits removed from the glibc recipe in oe-core, and
are provided both in another recipe, and, better yet, libtirpc.
Signed-off-by: Christopher Larson <chris_larson@mentor.com>
Currently the substitutions fail to match if the path contains re
special characters like '+', which is problematic.
Signed-off-by: Christopher Larson <chris_larson@mentor.com>
This returns immediately with 'UNKNOWN' if the external toolchain isn't
enabled, and also immediately adjusts sys.path regardless of OE_IMPORTS
handling to avoid the over-reliance upon that mechanism.
Signed-off-by: Christopher Larson <chris_larson@mentor.com>
The blacklist isn't necessary. We already provide the virtual, but if
someone wants the real thing, it shouldn't be harmful to allow it to
build.
Signed-off-by: Christopher Larson <chris_larson@mentor.com>
This will install, for example, a 'ld.gold' symlink in
STAGING_BINDIR_TOOLCHAIN/gcc, which we can then allow gcc to get to.
This makes it possible to rebuild just binutils-cross and use everything
else from an external toolchain, which can be useful to get ahold of
ld.gold when the external toolchain doesn't provide it.
Signed-off-by: Christopher Larson <chris_larson@mentor.com>
This ensures that _append/_prepend/_remove are also applied, so the user
can remove elements from the variable.
Signed-off-by: Christopher Larson <chris_larson@mentor.com>
We need to disable this for the same reason we disable the build-deps check.
The recursive dependency between libgcc and glibc has to be broken.
Signed-off-by: Christopher Larson <chris_larson@mentor.com>
Silence any errors from oe_multilib_header, as we don't care about missing
multilib headers, as the oe-core glibc version isn't necessarily the same as
our own.
Signed-off-by: Christopher Larson <chris_larson@mentor.com>
