Commit Graph

33709 Commits

Author SHA1 Message Date
Jason Schonberg
a6ed1c867d
Fix warning : lack of whitespace around assignment
Signed-off-by: Jason Schonberg <schonm@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2025-04-05 07:45:31 -07:00
Markus Volk
f3d83ffa99
libgsf: fix lack of whitespace around the assignment
Signed-off-by: Markus Volk <f_l_k@t-online.de>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2025-04-05 07:45:31 -07:00
Markus Volk
f360efb4e1
evolution-data-server: fix lack of whitespace around the assignment
Signed-off-by: Markus Volk <f_l_k@t-online.de>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2025-04-05 07:45:31 -07:00
Markus Volk
1fd4551021
accountsservice: fix Upstream-Status
This fixes:
ERROR: accountsservice-23.13.9-r0 do_patch: QA Issue: Malformed Upstream-Status in patch
/home/flk/poky/meta-openembedded/meta-gnome/recipes-support/accountsservice/accountsservice/00b6e12ad4044d33cc54c71c75773c5a653dad09.patch

Signed-off-by: Markus Volk <f_l_k@t-online.de>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2025-04-05 07:45:31 -07:00
Jason Schonberg
7f5fbc73f2
Fix warning : lack of whitespace around assignment
Signed-off-by: Jason Schonberg <schonm@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2025-04-04 19:18:48 -07:00
Sofiane HAMAM
d2ebc1fdd5
openocd : Fix non reproducible build
This package defines PKGBLDDATE as build timestamp which makes
it non reproducible. Use SOURCE_DATE_EPOCH if it is found, otherwise
use build timestamp. Following best practices, see :
https://reproducible-builds.org/docs/source-date-epoch/

Co-developed-by: Yoann Congal <yoann.congal@smile.fr>
Signed-off-by: Yoann Congal <yoann.congal@smile.fr>
Signed-off-by: Sofiane HAMAM <sofiane.hamam@smile.fr>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2025-04-04 19:18:48 -07:00
Soumya Sambu
9e90eac533
python3-django: upgrade 5.0.11 -> 5.0.13
Includes fix for CVE-2025-26699

Release Notes:
https://docs.djangoproject.com/en/dev/releases/5.0.12/
https://docs.djangoproject.com/en/dev/releases/5.0.13/

Signed-off-by: Soumya Sambu <soumya.sambu@windriver.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2025-04-04 19:18:48 -07:00
Soumya Sambu
54f5df8907
python3-django: upgrade 4.2.18 -> 4.2.20
Includes fix for CVE-2025-26699

Release Notes:
https://docs.djangoproject.com/en/dev/releases/4.2.19/
https://docs.djangoproject.com/en/dev/releases/4.2.20/

Signed-off-by: Soumya Sambu <soumya.sambu@windriver.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2025-04-04 19:18:48 -07:00
Nguyen Dat Tho
39dfe8a24b
f2fs-tools: Fix build with gcc-15
Backport patch to fix error: https://errors.yoctoproject.org/Errors/Details/850170/

Signed-off-by: Nguyen Dat Tho <tho3.nguyen@lge.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2025-04-04 19:18:48 -07:00
Khem Raj
25f64b605c
python3-pychromecast: Upgrade to 14.0.7
Apply a backport to fix build with setuptools 0.78.x

Signed-off-by: Khem Raj <raj.khem@gmail.com>
2025-04-04 19:18:48 -07:00
Jason Schonberg
48fdb7a1b9
Fix warning : lack of whitespace around assignment
Signed-off-by: Jason Schonberg <schonm@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2025-04-04 19:18:47 -07:00
Peter Kjellerstedt
7bc205ba54
ne10: Avoid requesting an executable stack
This avoids warnings like:

  ld: warning: NE10_physics.neon.s.o: missing .note.GNU-stack section
  implies executable stack
  ld: NOTE: This behaviour is deprecated and will be removed in a future
  version of the linker

With glibc 2.41, the need for an executable stack lead to errors like
this in runtime:

  [ ERR     ] foo@0[984]: [setup-script: /usr/share/foo/foo.enc] sol:
  runtime error: libNE10.so.10: cannot enable executable stack as shared
  object requires: Invalid argument

Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2025-04-04 19:18:47 -07:00
Jason Schonberg
838a8ae9ca
Fix warning : lack of whitespace around assignment
Signed-off-by: Jason Schonberg <schonm@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2025-04-04 19:18:47 -07:00
Denis OSTERLAND-HEIM
d51084073d
libftdi: cpp-wrapper fix cmake support
Backport fix for C++ wrapper cmake support.

Signed-off-by: Denis Osterland-Heim <denis.osterland@diehl.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2025-04-04 19:18:47 -07:00
mark.yang
9e57cd65cc
cyusbserial: fix build with gcc-15
* Fix incompatible pointer type error in signal function parameter
TOPDIR/tmp/work/core2-64-oe-linux/libcyusbserial/1.0.0+git/git/tools/cyusbserialtest.c:101:22: error: passing argument 2 of 'signal' from incompatible pointer type [-Wincompatible-pointer-types]
  101 |     signal (SIGUSR1, deviceHotPlug);
      |                      ^~~~~~~~~~~~~
      |                      |
      |                      void (*)(void)
In file included from TOPDIR/tmp/work/core2-64-oe-linux/libcyusbserial/1.0.0+git/git/tools/cyusbserialtest.c:25:
TOPDIR/tmp/work/core2-64-oe-linux/libcyusbserial/1.0.0+git/recipe-sysroot/usr/include/signal.h:88:57: note: expected '__sighandler_t' {aka 'void (*)(int)'} but argument is of type 'void (*)(void)'
   88 | extern __sighandler_t signal (int __sig, __sighandler_t __handler)
      |                                          ~~~~~~~~~~~~~~~^~~~~~~~~
TOPDIR/tmp/work/core2-64-oe-linux/libcyusbserial/1.0.0+git/git/tools/cyusbserialtest.c:83:6: note: 'deviceHotPlug' declared here
   83 | void deviceHotPlug () {
      |      ^~~~~~~~~~~~~
TOPDIR/tmp/work/core2-64-oe-linux/libcyusbserial/1.0.0+git/recipe-sysroot/usr/include/signal.h:72:16: note: '__sighandler_t' declared here
   72 | typedef void (*__sighandler_t) (int);
      |                ^~~~~~~~~~~~~~

Signed-off-by: mark.yang <mark.yang@lge.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2025-04-04 19:18:47 -07:00
Pulkit Singh Tak
12da079155
opencv: Adding FastCV-HAL enablement option as packageconfig
Migration to Fastcv static lib for Fastcv Extns and
adding fastcv enablement option as packageconfig.

Signed-off-by: Pulkit Singh Tak <quic_ptak@quicinc.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2025-04-04 19:18:47 -07:00
Nguyen Dat Tho
a842854681
thrift: Fix build with gcc-15
Backport patch to fix issue: https://errors.yoctoproject.org/Errors/Details/850167/

TOPDIR/tmp/work/core2-64-oe-linux/thrift/0.21.0/thrift-0.21.0/lib/cpp/src/thrift/concurrency/Mutex.h:47:26: error: 'int64_t' has not been declared
   47 |   virtual bool timedlock(int64_t milliseconds) const;
      |                          ^~~~~~~
TOPDIR/tmp/work/core2-64-oe-linux/thrift/0.21.0/thrift-0.21.0/lib/cpp/src/thrift/concurrency/Mutex.h:25:1: note: 'int64_t' is defined in header '<cstdint>'; this is probably fixable by adding '#include <cstdint>'
   24 | #include <thrift/TNonCopyable.h>
  +++ |+#include <cstdint>

Signed-off-by: Nguyen Dat Tho <tho3.nguyen@lge.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2025-04-04 19:18:46 -07:00
Nguyen Dat Tho
eaf94b092d
udevil: Fix build with gcc-15
Fix error related to "error: passing argument 2 of 'signal' from incompatible pointer type [-Wincompatible-pointer-types]".
Details in https://errors.yoctoproject.org/Errors/Details/850171/

Signed-off-by: Nguyen Dat Tho <tho3.nguyen@lge.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2025-04-04 19:18:46 -07:00
Chen Qi
14ff80c9dc
version-check.conf: add mechanism for checking version mismatch
Add a mechanism to check mismatch between runtime version and build time version.

To use, add the following line to local.conf:

  include conf/version-check.conf

Ideally, layers will have their own conf/version-check.conf to establish
some baseline, so that any future warning indicates some error. In such
case, users can use include_all:

  include_all conf/version-check.conf

The basic idea is to use qemu to run executables at build time, extract
possible versions, and check if there's a mismatch found.

Python meta data and .pc files are also checked for quick match. This
is because such info are also easy to be checked by users.

check-version-mismatch.bbclass is the class that does the actual work.
A new variable, CHECK_VERSION_PV, is introduced. It defaults to ${PKGV},
but also allows override. This allows us to handle special cases in each
layer.

version-check.conf is the configuration file that makes this functionality
easier to use and draws some baseline. It contains some override settings
for some recipes. With these overrides, all recipes in oe-core are handled
well. All warnings are valid warnings.

Note that 'ps' is added to HOSTTOOLS in version-check.conf. This is because
we need 'ps' to find stale processes and then clean them.

The warnings are like below:

  WARNING: time-1.9-r0 do_package_check_version_mismatch: Possible runtime versions ['UNKNOWN'] do not match recipe version 1.9
  WARNING: python3-unittest-automake-output-0.2-r0 do_package_check_version_mismatch: Possible runtime versions ['0.1'] do not match recipe version 0.2
  WARNING: pinentry-1.3.1-r0 do_package_check_version_mismatch: Possible runtime versions ['1.3.1-unknown'] do not match recipe version 1.3.1
  ...

There will be a data directory containing all details: tmp/check-version-mismatch.
This directory contains detailed data for each recipe that is built.
If users don't want it, they can set DEBUG_VERSION_MISMATCH_CHECK to 0.

Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2025-04-04 19:18:46 -07:00
mark.yang
0f08684d7f
sharutils: fix build with gcc-15.0.1
* gcc-15 uses gnu23 standard for c:
  https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=55e3bd376b2214e200fa76d12b67ff259b06c212
  bool is included as a reserved word, causing an error due to duplicate declaration.

  Also, when parameters are empty, an error occurs. Therefore, when using
  functions from the standard library, modify the defines in configure.ac
  and source code to use standard library functions.

* ../../sharutils-4.15.2/lib/system.h:51:36: error: expected ';', identifier or '(' before 'bool'
   51 | typedef enum {false = 0, true = 1} bool;
      |                                    ^~~~
  ../../sharutils-4.15.2/lib/system.h:79:7: error: conflicting types for 'fdopen'; have 'FILE *(void)'
   79 | FILE *fdopen ();
      |       ^~~~~~
  In file included from ../lib/stdio.h:43,
                 from ../../sharutils-4.15.2/libopts/autoopts/options.h:42,
                 from ../../sharutils-4.15.2/src/shar-opts.h:49:
  recipe-sysroot/usr/include/stdio.h:299:14: note: previous declaration of 'fdopen' with type 'FILE *(int,  const char *)'
  299 | extern FILE *fdopen (int __fd, const char *__modes) __THROW
      |              ^~~~~~
  ../../sharutils-4.15.2/lib/system.h:82:7: error: conflicting types for 'popen'; have 'FILE *(void)'
   82 | FILE *popen ();
      |       ^~~~~
  recipe-sysroot/usr/include/stdio.h:893:14: note: previous declaration of 'popen' with type 'FILE *(const char *, const char *)'
  893 | extern FILE *popen (const char *__command, const char *__modes)
      |              ^~~~~
  ../../sharutils-4.15.2/src/shar.c:112:12: error: conflicting types for 'localtime'; have 'struct tm *(void)'
  112 | struct tm *localtime ();
      |            ^~~~~~~~~
  In file included from ../lib/time.h:39,
                 from ../lib/sys/stat.h:44,
                 from ../../sharutils-4.15.2/lib/system.h:32:
  recipe-sysroot/usr/include/time.h:136:19: note: previous declaration of 'localtime' with type 'struct tm *(const time_t *)' {aka 'struct tm *(const long int *)'}
  136 | extern struct tm *localtime (const time_t *__timer) __THROW;
      |                   ^~~~~~~~~
  ../../sharutils-4.15.2/src/uudecode.c:85:16: error: conflicting types for 'getpwnam'; have 'struct passwd *(void)'
   85 | struct passwd *getpwnam ();
      |                ^~~~~~~~
  In file included from ../../sharutils-4.15.2/src/uudecode.c:76:
  recipe-sysroot/usr/include/pwd.h:116:23: note: previous declaration of 'getpwnam' with type 'struct passwd *(const char *)'
  116 | extern struct passwd *getpwnam (const char *__name) __nonnull ((1));
      |                       ^~~~~~~~
      |            ^~~~~~~~~

Signed-off-by: mark.yang <mark.yang@lge.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2025-04-04 19:18:20 -07:00
Martin Jansa
31519530f3
gpiod-sysfs-proxy, smbnetfs, zfs: add whitespace around assignments
With:
https://lists.openembedded.org/g/bitbake-devel/message/17508
there are WARNINGs like:

WARNING: meta-oe/meta-filesystems/recipes-filesystems/smbnetfs/smbnetfs_git.bb: meta-oe/meta-filesystems/recipes-filesystems/smbnetfs/smbnetfs_git.bb:9 has a lack of whitespace around the assignment: 'HOMEPAGE ="http://sourceforge.net/projects/smbnetfs"'
WARNING: meta-oe/meta-filesystems/recipes-filesystems/zfs/zfs_2.2.5.bb: meta-oe/meta-filesystems/recipes-filesystems/zfs/zfs_2.2.5.bb:5 has a lack of whitespace around the assignment: 'HOMEPAGE ="https://github.com/openzfs/zfs"'
WARNING: meta-oe/meta-filesystems/dynamic-layers/meta-python/recipes-support/gpiod-sysfs-proxy/gpiod-sysfs-proxy_0.1.2.bb: meta-oe/meta-filesystems/dynamic-layers/meta-python/recipes-support/gpiod-sysfs-proxy/gpiod-sysfs-proxy_0.1.2.bb:27 has a lack of whitespace around the assignment: 'export MOUNTPOINT="${@bb.utils.contains('PACKAGECONFIG', 'sys-class-mount', '/sys/class/gpio', '/run/gpio', d)}"'

Signed-off-by: Martin Jansa <martin.jansa@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2025-04-02 09:49:30 -07:00
Khem Raj
8e1979dfa3
python3-breathe: Inherit ptest-python-pytest instead of ptest
This eliminates more boiler plate code and add needed depednecies for
ptest package

Signed-off-by: Khem Raj <raj.khem@gmail.com>
2025-04-02 09:27:44 -07:00
Christian Lindeberg
42a47b364c
crucible: Use go module fetcher
Use the go module fetcher instead of allowing network access during the
compile task.
Reorder variables according to the recipe style guide.

Signed-off-by: Christian Lindeberg <christian.lindeberg@axis.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2025-04-02 07:29:32 -07:00
mark.yang
c022f3ec33
unbound: fix build with gcc-15.0.1
* fix following error:
  http://errors.yoctoproject.org/Errors/Details/850313/
  ../git/compat/malloc.c:9:7: warning: conflicting types for built-in function 'malloc'; expected 'void *(long unsigned int)' [-Wbuiltin-declaration-mismatch]
    9 | void *malloc ();
      |       ^~~~~~
  ../git/compat/malloc.c:5:1: note: 'malloc' is declared in header '<stdlib.h>'
    4 | #include "config.h"
  +++ |+#include <stdlib.h>
    5 | #undef malloc
  ../git/compat/malloc.c: In function 'rpl_malloc_unbound':
  ../git/compat/malloc.c:23:10: error: too many arguments to function 'malloc'; expected 0, have 1
   23 |   return malloc (n);
      |          ^~~~~~  ~
  ../git/compat/malloc.c:9:7: note: declared here
    9 | void *malloc ();
      |       ^~~~~~

* Seeing that there is '#undef malloc', it appears they don't want to
  use the malloc from stdlib.h.
  Therefore, we need to correctly define the parameters for malloc.

Signed-off-by: mark.yang <mark.yang@lge.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2025-04-02 07:29:32 -07:00
Kai Kang
0a4e093940
python-blivet: 3.9.2 -> 3.12.1
Upgrade python-blivet from 3.9.2 to 3.12.1:

* rebase 0002-run_program-support-timeout.patch

Signed-off-by: Kai Kang <kai.kang@windriver.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2025-04-02 07:29:32 -07:00
Randy MacLeod
fc17e47134
valkey: update from 8.0.2 -> 8.1.0
Release notes:
   https://github.com/valkey-io/valkey/releases/tag/8.1.0

The license file checksum changed because upstream added the line:
   SPDX-License-Identifier: BSD-3-Clause

Adjust the patches using devtool and manually munge the Upstream-Status-es.

Signed-off-by: Randy MacLeod <Randy.MacLeod@windriver.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2025-04-02 07:27:48 -07:00
Mingli Yu
39c914c41f
python3-pydot: Upgrade 2.0.0 -> 3.0.4
Switch to use python_setuptools_build_meta after the commit [1]
introduced in the new version.

Changelog:
  https://github.com/pydot/pydot/blob/main/ChangeLog

[1] d1627c95cb

Signed-off-by: Mingli Yu <mingli.yu@windriver.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2025-04-02 07:27:48 -07:00
mark.yang
a0b88afd79
pm-qa: fix build with gcc-15.0.1
* fix following error:
  http://errors.yoctoproject.org/Errors/Details/850314
    utils/uevent_reader.c: In function 'main':
    utils/uevent_reader.c:33:24: error: passing argument 2 of 'signal' from incompatible pointer type [-Wincompatible-pointer-types]
    33 |         signal(SIGINT, exit_handler);
        |                        ^~~~~~~~~~~~
        |                        |
        |                        void (*)(void)
    In file included from utils/uevent_reader.c:4:
    TOPDIR/tmp/work/core2-64-oe-linux/pm-qa/0.5.2/recipe-sysroot/usr/include/signal.h:88:57: note: expected '__sighandler_t' {aka 'void (*)(int)'} but argument is of type 'void (*)(void)'
    88 | extern __sighandler_t signal (int __sig, __sighandler_t __handler)
        |                                          ~~~~~~~~~~~~~~~^~~~~~~~~
    utils/uevent_reader.c:15:6: note: 'exit_handler' declared here
    15 | void exit_handler()
        |      ^~~~~~~~~~~~
    TOPDIR/tmp/work/core2-64-oe-linux/pm-qa/0.5.2/recipe-sysroot/usr/include/signal.h:72:16: note: '__sighandler_t' declared here
    72 | typedef void (*__sighandler_t) (int);
        |                ^~~~~~~~~~~~~~
    make: *** [<builtin>: utils/uevent_reader] Error 1

  Set PATCHTOOL to git because this recipe compiles all .c files including those in .pc/ directory which causes build errors.
  .pc/0001-fix-build-with-gcc-15-Wincompatible-pointer-types-er.patch/utils/uevent_reader.c:15:6: note: 'exit_handler' declared here
   15 | void exit_handler()

Signed-off-by: mark.yang <mark.yang@lge.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2025-04-02 07:27:48 -07:00
Mingli Yu
b0b2efe4e4
minizip: Make rconflicts with minizip-ng
Fixes:
  Error: Transaction test error:
  file /usr/bin/minizip conflicts between attempted installs of minizip-1.3.1-r0.riscv64 and minizip-ng-4.0.8-r0.riscv64
  file /usr/lib/libminizip.so.1 conflicts between attempted installs of minizip-1.3.1-r0.riscv64 and minizip-ng-4.0.8-r0.riscv64

Signed-off-by: Mingli Yu <mingli.yu@windriver.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2025-04-02 07:27:48 -07:00
Mingli Yu
aea21d5a39
minizip-ng: Add ptest support
# ./run-ptest
[==========] Running 55 tests from 6 test suites.
[----------] Global test environment set-up.
[----------] 22 tests from crypt
PASS:  crypt.rand
PASS:  crypt.sha1
PASS:  crypt.sha224
PASS:  crypt.sha256
PASS:  crypt.sha384
PASS:  crypt.sha512
PASS:  crypt.aes128
PASS:  crypt.aes128_cbc
PASS:  crypt.aes128_gcm
PASS:  crypt.aes194
PASS:  crypt.aes256
PASS:  crypt.hmac_sha1
PASS:  crypt.hmac_sha1_short_password
PASS:  crypt.hmac_sha256
PASS:  crypt.pbkdf2
PASS:  crypt.pbkdf2_long_odd_password
PASS:  crypt.pbkdf2_short_password
PASS:  crypt.pbkdf2_rfc6070_v1
PASS:  crypt.pbkdf2_rfc6070_v2
PASS:  crypt.pbkdf2_rfc6070_v3
PASS:  crypt.pbkdf2_rfc6070_v4
PASS:  crypt.pbkdf2_rfc6070_v5
[----------] 1 test from os
PASS:  os.utf8_unicode_string
[----------] 2 tests from encrypt
PASS:  encrypt.pkcrypt
PASS:  encrypt.aes
[----------] 2 tests from stream
bzip compressed from 877 to 505
bzip uncompressed from 505 to 877
PASS:  stream.bzip
lzma compressed from 877 to 526
lzma uncompressed from 526 to 877
PASS:  stream.lzma
[----------] 20 tests from os/path_resolve
PASS:  os/path_resolve.os/0
PASS:  os/path_resolve.os/1
PASS:  os/path_resolve.os/2
PASS:  os/path_resolve.os/3
PASS:  os/path_resolve.os/4
PASS:  os/path_resolve.os/5
PASS:  os/path_resolve.os/6
PASS:  os/path_resolve.os/7
PASS:  os/path_resolve.os/8
PASS:  os/path_resolve.os/9
PASS:  os/path_resolve.os/10
PASS:  os/path_resolve.os/11
PASS:  os/path_resolve.os/12
PASS:  os/path_resolve.os/13
PASS:  os/path_resolve.os/14
PASS:  os/path_resolve.os/15
PASS:  os/path_resolve.os/16
PASS:  os/path_resolve.os/17
PASS:  os/path_resolve.os/18
PASS:  os/path_resolve.os/19
[----------] 8 tests from stream/stream_find
PASS:  stream/stream_find.find/0
PASS:  stream/stream_find.find/1
PASS:  stream/stream_find.find/2
PASS:  stream/stream_find.find/3
PASS:  stream/stream_find.find/4
PASS:  stream/stream_find.find/5
PASS:  stream/stream_find.find/6
PASS:  stream/stream_find.find/7
[----------] Global test environment tear-down
[==========] 55 tests from 6 test suites ran.
[  PASSED  ] 55 tests.

Signed-off-by: Mingli Yu <mingli.yu@windriver.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2025-04-02 07:27:48 -07:00
Mingli Yu
7840c5e2c7
minizip-ng: Add new recipe
minizip-ng is a zip manipulation library written in C that is supported
on Windows, macOS, and Linux.

minizip-ng has new features and bug fixes compared to the original library
minizip [1] which had not been maintained for a long period of time.

[1] https://github.com/madler/zlib/tree/master/contrib/minizip

Signed-off-by: Mingli Yu <mingli.yu@windriver.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2025-04-02 07:27:48 -07:00
mark.yang
f452fa2fce
freediameter: fix build with gcc-15.0.1
* backport fix from:
  https://github.com/freeDiameter/freeDiameter/issues/72
  a54f10082f

  to fix:
  http://errors.yoctoproject.org/Errors/Details/850312/
  TOPDIR/tmp/work/qemux86_64-oe-linux/freediameter/1.5.0+git/git/libfdcore/sctp.c:622:21: note: 'bool' is a keyword with '-std=c23' onwards
  TOPDIR/tmp/work/qemux86_64-oe-linux/freediameter/1.5.0+git/git/libfdcore/sctp.c:622:26: error: expected identifier or '(' before '=' token
  622 |                 int bool = 1;
      |                          ^

Signed-off-by: mark.yang <mark.yang@lge.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2025-04-01 23:08:15 -07:00
mark.yang
41723a2a7d
xmlrpc-c: fix build with gcc-15.0.1
* Fix build error with gcc-15.0.1
  http://errors.yoctoproject.org/Errors/Details/850147/
    srcdir/lib/util/include/bool.h:13:5: error: cannot use keyword 'false' as enumeration constant
    13 |     false = 0,
        |     ^~~~~
    srcdir/lib/util/include/bool.h:13:5: note: 'false' is a keyword with '-std=c23' onwards
    srcdir/lib/util/include/bool.h:15:3: error: expected ';', identifier or '(' before 'bool'
    15 | } bool;
        |   ^~~~
    srcdir/lib/util/include/bool.h:15:3: warning: useless type name in empty declaration
    In file included from sleep.c:2:
    srcdir/lib/util/include/bool.h:13:5: error: cannot use keyword 'false' as enumeration constant
    13 |     false = 0,
        |     ^~~~~
    srcdir/lib/util/include/bool.h:13:5: note: 'false' is a keyword with '-std=c23' onwards
    srcdir/lib/util/include/bool.h:15:3: error: expected ';', identifier or '(' before 'bool'
    15 | } bool;
        |   ^~~~

  gcc-15 switched to -std=c23 by default.
  https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=55e3bd376b2214e200fa76d12b67ff259b06c212

Signed-off-by: mark.yang <mark.yang@lge.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2025-04-01 22:33:45 -07:00
Yoann Congal
246072bd3e
cmatrix: Fix host-based non-reproducibility
cmatrix configuration code choose where to install fonts based on what
directory exists on build host. This is not reproducible[0].

Remove the existence check and change the lists to the ones matching
OpenEmbedded paths.

[0]: https://autobuilder.yoctoproject.org/valkyrie/#/builders/87/builds/38/steps/32/logs/stdio

Signed-off-by: Yoann Congal <yoann.congal@smile.fr>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2025-04-01 21:59:45 -07:00
Khem Raj
afe1c610c5
python3-lief: Upgrade to latest on tip of trunk
Adds new dependency on typing-inspection module
Fix build with GCC-15 while here

Signed-off-by: Khem Raj <raj.khem@gmail.com>
2025-04-01 21:59:45 -07:00
Khem Raj
c86c9fa882
python3-pydantic: Add dependency on typing-inspection
Skip running test_readonly_qualifier_warning as it results in warnings
but Werror means it is reported as fails.

Signed-off-by: Khem Raj <raj.khem@gmail.com>
2025-04-01 21:59:39 -07:00
Khem Raj
2ce7725d8e
python3-pydantic: Upgrade to 2.11.1 release
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2025-04-01 21:54:57 -07:00
Khem Raj
2694eb1fe0
python3-pydantic-core: Upgrade to 2.33.0 release
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2025-04-01 21:54:56 -07:00
Khem Raj
a8823315bb
deqp-runner: Upgrade to 0.20.3 release
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2025-04-01 21:54:56 -07:00
Khem Raj
52138d7faf
python3-typing-inspection: Add recipe
This is needed by new versions of lief and pydantic python modules

Signed-off-by: Khem Raj <raj.khem@gmail.com>
2025-04-01 21:54:56 -07:00
Peter Marko
d9468fad73
gimp: ignore CVE-2007-3741
Restore CVE_STATUS statement from recipe version 2.10.38.
This was dropped on upgrade to 3.0.2, however NVD still tracks this CVE
as version-less, so explicit ignore is needed.

Signed-off-by: Peter Marko <peter.marko@siemens.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2025-04-01 21:54:56 -07:00
mark.yang
f3880aa2bb
linpack: fix build with gcc-15.0.1
* fix following error:
    linpacknew.c: In function 'dgefa':
    linpacknew.c:257:9: error: conflicting types for 'idamax'; have 'int(void)'
    257 |     int idamax(),j,k,kp1,l,nm1;
        |         ^~~~~~
    linpacknew.c:63:13: note: previous declaration of 'idamax' with type 'int(int,  REAL *, int)' {aka 'int(int,  double *, int)'}
    63 | static int  idamax   (int n,REAL *dx,int incx);
        |             ^~~~~~
    linpacknew.c:272:21: error: too many arguments to function 'idamax'; expected 0, have 3
    272 |                 l = idamax(n-k,&a[lda*k+k],1) + k;
        |                     ^~~~~~ ~~~
    linpacknew.c:257:9: note: declared here
    257 |     int idamax(),j,k,kp1,l,nm1;
        |         ^~~~~~
    linpacknew.c:326:21: error: too many arguments to function 'idamax'; expected 0, have 3
    326 |                 l = idamax(n-k,&a[lda*k+k],1) + k;
        |                     ^~~~~~ ~~~
    linpacknew.c:257:9: note: declared here
    257 |     int idamax(),j,k,kp1,l,nm1;
        |         ^~~~~~

    The function was already declared as static int idamax(int n, REAL *dx, int incx);
    on line 63, but it was redeclared as int idamax() inside the dgefa function on line 257,
    causing a conflict.
    where functions are redeclared without parameters,
    causing conflicts with the original function definitions.

Signed-off-by: mark.yang <mark.yang@lge.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2025-04-01 20:43:27 -07:00
mark.yang
0d2b2b54fc
libmcrypt: fix build with gcc-15.0.1
* see more details: http://errors.yoctoproject.org/Errors/Details/850150/
    des.c:199:9: error: too many arguments to function 'spinit'; expected 0, have 1
    199 |         spinit(key);
        |         ^~~~~~ ~~~
    des.c:38:56: note: declared here
    38 | static void permute_ip(), permute_fp(), perminit_ip(), spinit(),
        |                                                        ^~~~~~

* Move function forward declarations to .h file to fix the following errors:
    tripledes.c: In function '_mcrypt_desinit':
    tripledes.c:198:18: error: passing argument 1 of 'perminit' from incompatible pointer type [-Wincompatible-pointer-types]
    198 |         perminit(&key->iperm, ip);
        |                  ^~~~~~~~~~~
        |                  |
        |                  char (*)[16][16][8]
    In file included from tripledes.c:23:
    tripledes.h:11:27: note: expected 'char (*)[16][8]' but argument is of type 'char (*)[16][16][8]'
    11 | static void perminit(char perm[][16][8], char p[64]);
        |                      ~~~~~^~~~~~~~~~~~~
    tripledes.c:199:18: error: passing argument 1 of 'perminit' from incompatible pointer type [-Wincompatible-pointer-types]
    199 |         perminit(&key->fperm, fp);
        |                  ^~~~~~~~~~~
        |                  |
        |                  char (*)[16][16][8]
    tripledes.h:11:27: note: expected 'char (*)[16][8]' but argument is of type 'char (*)[16][16][8]'
    11 | static void perminit(char perm[][16][8], char p[64]);
        |                      ~~~~~^~~~~~~~~~~~~

	Changed parameter from &key to key
	perminit(key->iperm, ip);
	perminit(key->fperm, fp);

Signed-off-by: mark.yang <mark.yang@lge.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2025-04-01 20:43:27 -07:00
mark.yang
31595e28fa
sqlite-orm: fix build with gcc-15.0.1
* see more details:
  http://errors.yoctoproject.org/Errors/Details/850148/
    TOPDIR/tmp/work/core2-64-oe-linux/sqlite-orm/1.5/git/examples/synchronous.cpp:7:5: error: 'uint16_t' does not name a type
        7 |     uint16_t src_port;
        |     ^~~~~~~~
    TOPDIR/tmp/work/core2-64-oe-linux/sqlite-orm/1.5/git/examples/synchronous.cpp:3:1: note: 'uint16_t' is defined in header '<cstdint>'; this is probably fixable by adding '#include <cstdint>'
        2 | #include <sqlite_orm/sqlite_orm.h>
    +++ |+#include <cstdint>
        3 | #include <string>

While this was backported from 6a96d1cec4(Explicitly included <cstdint> in examples and unit tests),
since it was a commit made in v1.9, only synchronous.cpp was modified as other files do not exist in the current version.

Signed-off-by: mark.yang <mark.yang@lge.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2025-04-01 09:21:23 -07:00
mark.yang
e2c8a25c1b
mcpp: Stick to C17
* Fix build error with gcc-15 by renaming goto labels
  see more details:
  http://errors.yoctoproject.org/Errors/Details/850149/
  ../../mcpp-2.7.2/src/system.c:3436:15: error: expected identifier or '*' before 'true'

  true, false are reserved keywords in gcc-15
  Rename goto 'labels' from 'ture' to 'true_label', from 'false' 'false_label' to avoid conflicts.

Signed-off-by: mark.yang <mark.yang@lge.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2025-04-01 09:21:23 -07:00
Wang Mingyu
713d35adce
python3-web3: upgrade 7.9.0 -> 7.10.0
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2025-03-31 15:00:33 -07:00
Wang Mingyu
f60d48485c
python3-tzdata: upgrade 2025.1 -> 2025.2
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2025-03-31 15:00:33 -07:00
Wang Mingyu
8fade2c177
python3-tox: upgrade 4.24.2 -> 4.25.0
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2025-03-31 15:00:33 -07:00
Wang Mingyu
58e31bd3cd
python3-sqlalchemy: upgrade 2.0.39 -> 2.0.40
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2025-03-31 15:00:33 -07:00
Wang Mingyu
7a3ffa58c0
python3-pymisp: upgrade 2.5.8.1 -> 2.5.9
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2025-03-31 15:00:33 -07:00