cpuid's Makefile passes -s to install to strip the binaries, but as this
uses the _host_ strip it can fail if that strip doesn't know about the
target (for example, building cpuid for x86 on aarch64):
install -D -s -m 755 cpuid .../image/usr/bin/cpuid
strip: Unable to recognise the format of the input file `.../image/usr/bin/cpuid'
Set INSTALL_STRIP='' so that the binaries are not stripped, and remove
the INSANE_SKIP for already-stripped.
Signed-off-by: Ross Burton <ross.burton@arm.com>
Changelog:
==============
- New architecture: mips
- New architecture: loongarch
- Output buffering can now be unconditionally disabled
- New provider: profile
- Incorrect stack management when accessing tracepoint data
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
The base problem this is trying to solve: capnproto has two main
components: libraries that can be linked against, and binary files
that can generate c++ code from capnproto definitions. When cross-compiling
one needs to use the cross-compiled libraries, but with the native
definition-compilers.
When linking against capnproto from another recipe, cross-compilation
fails, because the cmake files generated by capnproto verify the
existence of binary files in $bindir. When using a cross-compiled
version of capnproto, these binary files do not exist in RECIPE_SYSROOT, so
the compilation fails.
The previous patch: the previous solution patched the CMakeLists.txt
file in a way that it didn't export nor install the generated binary files.
Accidentally this also happened with native build (and happened knowingly with
target builds).
The new patch: instead of not installing and not exporting the binaries,
just install them without exporting, when creating a target build.
During compilation check is CMAKE_CROSSCOMPILING is set (coming from
cmake.bbclass) - if it is set, only install the binaries, without
exporting. When it is not set, resort to the original behavior.
Signed-off-by: Gyorgy Sarvari <skandigraun@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
When LAPACKE is enabled, the QA check fails with the following error:
ERROR: lapack-3.12.1-r0 do_package_qa: QA Issue: lapack-ptest rdepends on lapack-dev [dev-deps]
ERROR: lapack-3.12.1-r0 do_package_qa: Fatal QA errors were found, failing task.
The root cause is that `lapack-ptest` accidentally installed `lapacke.pc`,
which is a development file intended to be included only in the `lapack-dev` package.
To resolve this: Remove `lapacke.pc` from the `lapack-ptest` installation
Signed-off-by: Zhang Peng <peng.zhang1.cn@windriver.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
The correct dependency name for pyelftools is "python3-pyelftools".
Set the dependency name accordingly to avoid build failure with
this PACKAGECONFIG.
Signed-off-by: Gyorgy Sarvari <skandigraun@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
As a build time dependency, python3 provides python3-core - set the
PACKAGECONFIG accordingly to avoid build failure.
Signed-off-by: Gyorgy Sarvari <skandigraun@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
In case unwind PACKAGECONFIG is enabled, do_configure task
fails with the following error message:
| configure: error: Cannot enable both --with-libunwind and --with-elfutils
To avoid this error, disable elfutils with this PACKAGECONFIG.
Signed-off-by: Gyorgy Sarvari <skandigraun@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
The cmake files generated by this recipe contain a number
of interfacing libraries, with absolute paths, which also
contain the TMPDIR. The TMPDIR part of these paths were
just truncated by the recipe, to avoid the corresponding
QA check error.
However this made it impossible to to link against this
library from other recipes. When one tried, the find_package
command failed with the following error:
| Run Build Command(s): ninja -v -j 12 all
| ninja: error: '/usr/lib/libjsoncpp.so', needed by 'jsonrpctest', missing and no known rule to make it
To avoid this, instead of just truncating this path, set it to
${CMAKE_SYSROOT} placeholder (which is resolved by CMake to
the correct value at build-time, using the variable set by
cmake.bbclass)
Signed-off-by: Gyorgy Sarvari <skandigraun@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Changelog:
=============
* Mostly related to bazel build support.
* Min bazel supported is now 7 or higher, as WORKSPACE files are removed
* Minor C++ codegen fix removing extra semicolon
* Rust Full Reflection
* Mostly documentation updates hosted at https://flatbuffers.dev
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
This reverts commits 4271cc2827 ("android-tools: Add flag to enable
adbd service (#147)") and b85ae59968 ("android-tools 10: Add flag to
enable adbd service"). These two commits added optional
ROOTFS_POSTPROCESS_COMMAND touching the flag file, however this variable
doesn't make any sense in the package recipe, it is only concerned in
the image context.
Drop useless code from the android-tools recipe.
Fixes: 4271cc2827 ("android-tools: Add flag to enable adbd service (#147)")
Fixes: b85ae59968 ("android-tools 10: Add flag to enable adbd service")
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
protobuf-lite is a package, not recipe, so current code leads to
ERROR: Nothing PROVIDES 'protobuf-lite'
Moving it to 4th part (rdepends) is not needed as grpc links against it
so that rdependency is asutomatic.
Therefore protobuf-lite should be removed.
Note: for native, this packageconfig does not even compile and for
target it fails to link.
Signed-off-by: Peter Marko <peter.marko@siemens.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
googletest is needed only if we would build tests, and then it should be
conditional on PTEST_ENABLED
libnsl is not needed. there is no linking command in any cmake.
The only grep hit is in cares.cmake to disable it.
Commit 2ffc7b45d6 which added it talks
about host distros, but also such case would be wrong when adding it to
general depends (should be in native only depends) and it would have to
have be reference in cmake (in grpc or in one of recipe-sysroot).
Also sort the dependencies in the process.
Signed-off-by: Peter Marko <peter.marko@siemens.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
After the migration from Mercurial to GitHub the homepage has
changed and SIP is now licensed under the BSD-2-Clause license. The
upgrade to version 6.10.0 brings the following changes:
- SIP_ABI_VERSION has been added as a module attribute of the sip
module. This is an integer that represents the ABI version that
the module implements as a 3 part hexadecimal number.
This has been implemented in ABIs v12.17 and v13.10.
- The ability of sip-module to generate sdists for older ABI
versions has been restored. The oldest that can be generated are
v12.9 and v13.1 which are the oldest non-deprecated versions.
- The default minor ABI version to use is now the latest minor
version for a particular major version (rather than 0 as it was
previously).
- The --abi-version command line option has been added to sip-build,
sip-install and sip-wheel to specify the ABI version of the sip
module to generate code for.
- The %MinimumABIVersion directive is used to specify the minimum
sip module ABI to target in order to ensure that all calls to the
public API from handwritten code are available.
A consequence of this change is that passing string values to the
/Deprecated/ annotation no longer requires an ABI version that
supports them to be targeted. If the targeted ABI version does
not support them they are simply ignored.
- The value of a string annotation uses the ; and : characters to
allow platform- and feature-specific values to be defined. These
special characters can now be escaped using a leading \\. This
capability has now been documented.
- The license designator in setup.py for the latest versions of the
sip module are now correctly specified as BSD-2-Clause.
- The code generation has been fixed for classes created by
instantiating mapped type templates using a typedef with the
/NoTypeName/ annotation.
This work was sponsored by GOVCERT.LU.
License-Update: SIP is now licensed under the BSD-2-Clause license.
Signed-off-by: Leon Anavi <leon.anavi@konsulko.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Add all relevant products from following query.
Also remove generic "protobuf" to avoid matching golang:protobuf.
.../downloads/CVE_CHECK2$ sqlite3 nvdcve_2-2.db
sqlite> select vendor, product, count(*) from products where product like '%protobuf%' group by vendor, product;
golang|protobuf|1
google|google-protobuf|5
google|protobuf|2
google|protobuf-cpp|4
google|protobuf-java|15
google|protobuf-javalite|12
google|protobuf-kotlin|6
google|protobuf-kotlin-lite|4
google|protobuf-python|4
protobuf|protobuf|1
protobuf-c_project|protobuf-c|2
protobufjs_project|protobufjs|3
rust-protobuf_project|rust-protobuf|2
Signed-off-by: Peter Marko <peter.marko@siemens.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
We should not use additional vendored jsoncpp unless required due to
compatibility issues.
Signed-off-by: Peter Marko <peter.marko@siemens.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
This commit reverts
https://git.openembedded.org/meta-openembedded/commit/?id=5af1cd3ada4cc86864810a12c82771ba1afdce64
That commit prefers sdk development instead of release images.
The additional libraries are not needed for protobuf at runtime.
Also any component depending on protobuf will have whole abseil-cpp in
sysroots so linking all the libraries is possible and any additional
ones will be installed.
What may not work is if protobuf is installed in sdk image and
application using it wants to use an additional abseil-cpp library.
However that is easily fixable by adding also abseil-cpp to sdk.
Removing hard-dependency in release images is much harder.
Signed-off-by: Peter Marko <peter.marko@siemens.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
When linking to capnproto from another project, cmake fails to
find this package with the following error:
| CMake Error at ${RECIPE_SYSROOT}/usr/lib/cmake/CapnProto/CapnProtoTargets.cmake:176 (message):
| The imported target "CapnProto::capnp_tool" references the file
|
| "${RECIPE_SYSROOT}/usr/bin/capnp"
|
| but this file does not exist. Possible reasons include:
To solve this, this change includes the following:
1. Add a patch that removes the files installed (and exported) in
${bindir} from the target build. The CMake file originally verified
that these files exist when another recipe tried to use it, however
the ${RECIPE_SYSROOT} does not contain the binaries in ${bindir},
so it failed quick in the do_configure step. (This alone is enough
to link against the cross-compiled libraries of capnproto successfully,
but code-generation from capnproto definition fails)
2. Add a new bbclass for capnproto. To cross-compile an application
that uses capnproto, the application needs to be linked against the
cross-compiled version of the libraries, however the native version
of the binaries need to be used to generate C++ code from the
capnproto definitions. This class sets the correct CMake arguments, to
use the capnproto binaries from the native package, instead of looking
for the non-existent cross-compiled binaries. (These variables can
be found in ${libdir}/cmake/CapnProto/CapnProtoConfig.cmake file)
Signed-off-by: Gyorgy Sarvari <skandigraun@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Recipes are much more readable with whitespace around the assignment operators.
Fix various assignments in meta-openembedded recipes to show this is definitely
the preferred formatting.
This fixes recipes with larger numbers of issues but there are just under 100
other references left to fix.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
If not specified on build commandline for luke, it results in
pulling it from build host development headers under /usr/include
this was always happening but with recent fixes to GCC poisoning
host includes patch, this issue has come to fore.
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Building of android-tools-native aborted due to
missing dependency with android-tools-conf-native.
Fixed by extending android-tools-conf-configfs_1.0.bb recipe to build native
Signed-off-by: Christos Gavros <gavrosc@yahoo.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
ERROR: lapack-3.12.0-r0 do_package_qa: QA Issue:
File /usr/lib/lapack/ptest/bin/xccblat3 in package lapack-ptest contains reference to TMPDIR
File /usr/lib/lapack/ptest/bin/xdcblat3 in package lapack-ptest contains reference to TMPDIR
File /usr/lib/lapack/ptest/bin/xdcblat1 in package lapack-ptest contains reference to TMPDIR
File /usr/lib/lapack/ptest/bin/xscblat1 in package lapack-ptest contains reference to TMPDIR
File /usr/lib/lapack/ptest/bin/xccblat2 in package lapack-ptest contains reference to TMPDIR
File /usr/lib/lapack/ptest/bin/xzcblat2 in package lapack-ptest contains reference to TMPDIR
File /usr/lib/lapack/ptest/bin/xzcblat1 in package lapack-ptest contains reference to TMPDIR
File /usr/lib/lapack/ptest/bin/xccblat1 in package lapack-ptest contains reference to TMPDIR
File /usr/lib/lapack/ptest/bin/xdcblat2 in package lapack-ptest contains reference to TMPDIR
File /usr/lib/lapack/ptest/bin/xscblat2 in package lapack-ptest contains reference to TMPDIR
File /usr/lib/lapack/ptest/bin/xscblat3 in package lapack-ptest contains reference to TMPDIR
File /usr/lib/lapack/ptest/bin/xzcblat3 in package lapack-ptest contains reference to TMPDIR [buildpaths]
Signed-off-by: Martin Jansa <martin.jansa@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Changelog:
==========
* Parse unsafe attributes
* Fix local override of enum prefix-with-name
* Add rename-all=prefix
* ir: add support for UnsafeCell and SyncUnsafeCell
* Implement mangling for arrays
* Fix: Ignore 'CARGO_BUILD_TARGET' in tests
* Newline for each field for constexpr field constants
* Fix clippy warnings
* Add aarch64/arm64 to CI
* Add `unstable_ir` feature flag that makes the ir pub
* Support generated a symbols file
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Changelog:
===========
- Don't lose notifies received whilst the notifies() iterator is not running
- Make sure that the notifies callback is called during the use of the notifies() generator
- Raise the correct error returned by the database (such as AdminShutdown or
IdleInTransactionSessionTimeout) instead of a generic OperationalError when
a server error causes a client disconnection
- Build macOS dependencies from sources instead using the Homebrew versions in
order to avoid problems with MACOSX_DEPLOYMENT_TARGET
- Bump libpq to 17.2 in Linux and macOS binary packages.
- Bump libpq to 16.4 in Windows binary packages, using the vcpkg library
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
0001-fix-add-missing-zero-initialization-to-region.patch
removed since it's included in 4.3.0
Changlog:
=========
Added
------
Support std::optional as a template argument of toml::find
Support multiple arguments toml::visit(visitor, args...)
Fixed
------
toml::detail::region::last_ may be used uninitialized
Fix use with CMake 3.21 and older
fix: prevent size_t-max length string allocation
update README.md
Make parsing faster for very long line
Avoid known problem in MSVC
Check if source_location::file_name() is null before formatting
Changed
-------
Update hugo-book theme
Add MSVC 2017 to appveyor build
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Changelog:
==========
* Fixes for new release process
* Fixes for newer valac
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Last tag is from 2014, but bugfixing continued and last commit is from
year 2024. Additional 87 commits are present, mostly bugfixes.
PV already has "+git" although it was exactly on tag, no edit needed.
Drop 3 patches which are included in current git version.
Add CVE_STATUS for 2 CVEs from those patches.
Also mark one additional CVE as fixed: CVE-2021-33454.
Stack trace from https://github.com/yasm/yasm/issues/166
References the same line of code as corrected in
https://github.com/yasm/yasm/pull/244
Signed-off-by: Peter Marko <peter.marko@siemens.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
License-Update: Copyright year updated to 2025.
Changelog:
==========
- Many xml_attribute:: and xml_node:: functions now transparently support
std::string_view and std::string when C++17 support is detected.
- Improve pkg-config file generation for NixOS
- PUGIXML_BUILD_APPLE_FRAMEWORK CMake option can be used to build pugixml
as .xcframework
- PUGIXML_INSTALL CMake option can be used to disable installation targets
- Fix clang/gcc warnings -Wzero-as-null-pointer-constant, -Wuseless-cast,
-Wshorten-64-to-32
- Fix unreferenced function warnings in PUGIXML_NO_STL configuration
- Fix CMake 3.31 deprecation warnings
- Stop using deprecated throw() when noexcept is available
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Ross Burton
Changqing Li
Wang Mingyu
Gyorgy Sarvari
Zhang Peng
Dmitry Baryshkov
Peter Marko
Leon Anavi
Richard Purdie
Khem Raj
Christos Gavros
Jason Schonberg
Ayoub Zaki
Martin Jansa