| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
|
|
|
|
|
|
| |
Standalone multilibs are only needed when building a PetaLinux specific
toolchain. So remove this from the general bbappends.
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
|
|
|
| |
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
|
|
|
|
|
|
|
|
|
| |
Workaround for:
ERROR: binutils-cross-canadian-aarch64-2.39-r0 do_package_qa: QA Issue: non -staticdev package contains static .a library: binutils-cross-canadian-aarch64 path '/usr/local/oe-sdk-hardcoded-buildpath/sysroots/x86_64-oesdk-linux/usr/lib/aarch64-xilinx-elf/bfd-plugins/libdep.a' [staticdev]
Need for the workaround was introduced with latest version of poky (langdale)
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
|
|
|
|
|
|
|
|
|
| |
related"
This reverts commit a906596017b9fd3e55555862700594aad8867c27.
No longer necessary after change made to embeddedsw
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
getentropy and the related arc4random function are defined in unistd.h, they
appear to be defined in some iterations of libgloss. However the defintion
is not enough in the general case, which causes C++ linkage to fail with:
libstdc++.a(random.o): in function `std::(anonymous namespace)::__libc_getentropy(void*)':
(.text._ZNSt12_GLOBAL__N_117__libc_getentropyEPv+0x14): *undefined reference to `getentropy'*
This change doesn't remove getentropy or arc4random, but does instruct
libstdc++ to not use either function.
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
|
|
|
| |
Signed-off-by: Mark Hatle <mark.hatle@kernel.crashing.org>
|
|
|
|
|
|
|
| |
Remove -enable-target-optspace, which forces -Os when building various
internal libraries.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
| |
armrm override is now replaced by armv7r and armv8r overrides. Adjust
recipes to match the new usage.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
| |
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
| |
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
| |
This reverts commit 2c819946b5258291d1725dabb3f5180d36971bd6.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
| |
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
|
|
|
|
| |
The regular (all version) bbappend will work with both gcc 10 and gcc 11.
It only needs to tell the system it is compatible with baremetal builds.
The special gcc-source_10 version works with the unique microblaze gcc only.
This verifies, and configures the microblaze toolchain for the large
multiconfig SDK build.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
| |
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
|
|
|
| |
This is the result of automated script (0.9.0) conversion:
oe-core/scripts/contrib/convert-overrides.py .
converting the metadata to use ":" as the override character instead of "_".
Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
|
|
|
|
|
|
| |
Upgrade gcc-source 10.% -> 11.%
Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
When the user chooses to build a microblaze target, the compiler can fail
to patch properly as a symptom. Users may think it's a simple patch failure,
but really they forgot to include the meta-microblaze layer itself.
Declare the meta-microblaze layer as a recommended layer, and verify in the
gcc-source bbappend that it has been included, if a microblaze target is being
built.
Signed-off-by: Mark Hatle <mark.hatle@kernel.crashing.org>
|
|
|
|
|
|
|
|
|
| |
Due to the way the multilib xilinx-standalone works, one or more empty
directories under ${D}/lib may exist. This triggers a QA error about
unpackaged files. Use rmdir to delete these directories to ensure they
are empty.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
|
| |
Move newlib/libgloss from 3.1.0 to 3.%
Move the gcc configuration for standalone to gcc 10.
Signed-off-by: Mark Hatle <mark.hatle@kernel.crashing.org>
|
|
|
|
|
|
| |
Remove recipe bbappends pointing to older versions. The newer versions are available in meta-microblaze
Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
Issue: CR-1069415
Issue: CR-1069801
Linux based SDK toolchains need to disabled multilib support, similar to
the existing 0004-64-bit-multilib-hack.patch from OE. This will fix
compiling C++ applications, as well as potentially other multilib header
and library issues.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Issue: CR-1065455
Microblaze does not support initfini_array in a baremetal configuration.
This has previously been disabled in binutils, but it was missed in GCC and
related libraries.
This patch slightly restructures the baremetal configurations to move the
common configuration elements into a single configure set. This matches the
behavior from the Yocto Project gcc-configure-common.inc file.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The key is using COMPATIBLE_HOST to declare, for each recipe, which
OS they are compatible with. This is a regex, so we need to
carefully specify the arch/vendor wild cardscomponents so that we match
only the OS parts.
In the distro configuration, default to the standard Linux HOST_SYS
setting.
In the various baremetal recipes (or esw class) set the specific
compatibility to allow baremetal recipes to build.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
|
| |
compatibility"
This reverts commit 4f3edb6da405ffff957d6f194bc7db7bdd9f1463.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
|
|
| |
When appending file paths the ':' should be at the beginning of the
path. The patched appending lines were still working because there was
no paths added after the '__default:'
Fixing typo to ensure no breakages later
Signed-off-by: Jaewon Lee <jaewon.lee@xilinx.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Following the example of base.bbclass in OE-Core, a new COMPATIBLE_OS
variable is defined. Similar to COMPATIBLE_MACHINE, it is a regex that
can be used to declare TARGET_OS string compatibility on a per-recipe
basis. Either the distro configuration or the recipes themselves will
need to inherit this class.
By default the class assumes we're building a Linux based system, and
thus any recipe who has not declared compatibility is compatible with
Linux. The default compatible field was copied from bitbake.conf to
ensure there are no surprised.
Additionally, enable the usage of this class throughout
meta-xilinx-standalone layer.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
|
| |
When the xilinx-standalone distribution is not enabled, we need to make sure
that we do not affect various task hashes. This conforms to the Yocto
Project Compliance requirements.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Enable the following multilibs:
.
le
bs
p
m
fpd
m/fpd
p/m
p/fpd
p/m/fpd
bs/p
bs/m
bs/fpd
bs/m/fpd
bs/p/m
bs/p/fpd
bs/p/m/fpd
le/m64
le/bs
le/p
le/m
le/fpd
le/m/fpd
le/p/m
le/p/fpd
le/p/m/fpd
le/bs/p
le/bs/m
le/bs/fpd
le/bs/m/fpd
le/bs/p/m
le/bs/p/fpd
le/bs/p/m/fpd
le/m64/bs
le/m64/p
le/m64/m
le/m64/fpd
le/m64/m/fpd
le/m64/p/m
le/m64/p/fpd
le/m64/p/m/fpd
le/m64/bs/p
le/m64/bs/m
le/m64/bs/fpd
le/m64/bs/m/fpd
le/m64/bs/p/m
le/m64/bs/p/fpd
le/m64/bs/p/m/fpd
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
|
|
|
|
| |
As part of the merge of the code bases, changes were introduced that
changed the way the cortexr5 was defined. To sync this between the
baremetal compilation and the baremetal toolchain compilation we
create a new armrm tune file, define a new tune feature of 'armrm',
define 'armrm' as a new machine override based on the feature 'armrm',
and move the cortexr5 tuning to a common file.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
|
|
| |
The C++ headers are slightly different for different multilibs. The Yocto
Project name (canonical arch) is different then the gcc multilib directory
name. Put in code that will syncronize these two items, allows C++ support
to function properly, avoiding conflicts in the process.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Distro Changes:
When building a multilib, we need to disable configsite cache. Otherwise
the system will fail to generate the SDK as there are no configsite entries
due to newlib based multilibs.
Recipe Changes:
gcc - globally disable multilib configuration
- Disable Linux specific configurations (EXTRACONFFUNCS)
gcc-cross-canadian - enable multilib on a recipe specific basis
libgcc - add a noop override to do_multilib_install to avoid Linux specific
multilib processing
newlib - arm/v6+m/nofp and arm/v8-m.base/nofp do not have newlib trap
implementations. libgloss contains these, workaround by
disabling builtin trap syscall handler.
- misc workarounds for multilib installs
libgloss - Allow MLPREFIX for newlib dependencies
meta-toolchain - adjust to install only the items we want/need
packagegroup-newlib-standalone-sdk-target - new pkggroup for the
custom baremetal SDK to select the right set of packages
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
| |
zynqmp and versal variants
Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com>
|
|
|
|
| |
Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com>
|
|
on recipes-devtools
Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com>
|