This ensures that host tools like 'gen' are built for build host and not
target. internal bind build supplies its own options to configuring it,
where it does not pass --host option and as a result it does not deduce
it to be a cross compile and hence these variables are not set property
inside bind build
Fixes
| ./gen: /usr/lib/libc.so.6: version `GLIBC_2.38' not found (required by ./gen)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
It does not build with 6.4+ kernel, it is using symbols which are not
abailable to non GPL modules anymore
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Pass it via cflags from environment, so it can be controlled for
platforms where it is not supported
Pass -fstack-clash-protection for clang too, it is available now a days
Signed-off-by: Khem Raj <raj.khem@gmail.com>
The currently used version 1.6.20 of pv does not show the progress
bar if no controlling terminal is set. Added a patch which restores
previous behavior of pv as in version 1.6.6.
Tested with pv in the busybox initscript of GyroidOS which is
running on /dev/console (which has no controlling tty). With this
fix, we get the progress bar back on /dev/console as before.
This was also submitted upstream but dangling since several Months:
https://github.com/a-j-wood/pv/pull/64
Signed-off-by: Michael Weiß <michael.weiss@aisec.fraunhofer.de>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Currently we see ptest failures like below
testseries | result_id : oeqa | runtime_meta-python-ptest-image-python3-requests-toolbelt_qemux86-64_20230713012809
ptestresult.python3-requests-toolbelt.tests/test_dump.py::TestDumpRealResponses::test_dump_all
ptestresult.python3-requests-toolbelt.tests/test_dump.py::TestDumpRealResponses::test_dump_response
ptestresult.python3-requests-toolbelt.tests/test_sessions.py::TestBasedSession::test_prepared_request_override_base
ptestresult.python3-requests-toolbelt.tests/test_sessions.py::TestBasedSession::test_prepared_request_with_base
ptestresult.python3-requests-toolbelt.tests/test_sessions.py::TestBasedSession::test_request_override_base
ptestresult.python3-requests-toolbelt.tests/test_sessions.py::TestBasedSession::test_request_with_base
These patches from a posted pull upstream fixes them
Signed-off-by: Khem Raj <raj.khem@gmail.com>
native as well as target recipe often fail on AB still
therefore re-introduce the patch to disable parallel build
to 6.0.5 as well.
Signed-off-by: Khem Raj <raj.khem@gmail.com>
The current use of RDEPENDS to add a dependency on bats results
in the QA warning/error
lib32-libgpiod package lib32-libgpiod-ptest-dev - suspicious values
'bats-dev' in RRECOMMENDS [multilib]
when building lib32-libgpiod with ptest not enabled. We add the
dependency only if ptest is enabled.
Signed-off-by: Joe Slater <joe.slater@windriver.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
It fails to build fltk-native on Ubuntu 20.04 with glibc 2.31:
| /path_to/tmp/hosttools/ld: lib/libfltk.a(Fl_Native_File_Chooser.cxx.o): in function `fl_dlopen(char const*, char const*)':
| Fl_Native_File_Chooser.cxx:(.text+0x61a): undefined reference to `dlopen'
| /path_to/tmp/hosttools/ld: lib/libfltk.a(Fl_Native_File_Chooser.cxx.o): in function `Fl_GTK_File_Chooser::probe_for_GTK_libs()':
| Fl_Native_File_Chooser.cxx:(.text+0xf92): undefined reference to `dlerror'
The original fix in fltk-native recipe does not work any more because '-ldl'
appears before lib/libfltk.a and causes dlopen() unresolved. The reason why it
doesn't fail on other hosts is that the functions dlopen(), dlerror() etc. have
been moved to libc.so since glibc 2.34 via the commits in glibc:
0c1c3a771e dlfcn: Move dlopen into libc
add8d7ea01 dlfcn: Move dlvsym into libc
6dfc0207eb dlfcn: Move dlinfo into libc
492560a32e dlfcn: Move dladdr1 into libc
6a1ed32789 dlfcn: Move dlmopen into libc
77f876c0e3 dlfcn: Move dlsym into libc
602252b553 dlfcn: Move dladdr into libc
d8cce17d2a dlfcn: Move dlclose into libc
Append 'dl' to fltk link items explictly to fix the error.
Signed-off-by: Kai Kang <kai.kang@windriver.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
The C++ bindings are new in libiio 0.25 , make those available.
Unlike python bindings which are gated off by PACKAGECONFIG, it
seems the C++ bindings have no dependencies, the C++ compiler is
always present, so the bindings can always be enabled.
Signed-off-by: Marek Vasut <marex@denx.de>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
The only known consumer of this library was the xorgcfg utility, which
was disabled by default in xorg-server 1.4 (Sep. 2007) and removed in
xorg-server 1.6 (Feb. 2009).
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
This hasn't seen any upstream activity since 2017, as users should be
using xinput --set-mode instead.
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
This is the client-side library for the LBX extension, which was removed
from xserver 1.2 (released 2007).
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
- use system bubblewrap and xdg-dbus-proxy instead of building subprojects
- fix seccomp PACKAGECONFIG
Signed-off-by: Markus Volk <f_l_k@t-online.de>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Update the recipe to latest git revision to pull in latest fixes.
Signed-off-by: Marek Vasut <marex@denx.de>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
This is a bugfix release that is API and ABI compatible with previous
0.3.x releases.
- Fixes an ALSA resume after suspend error.
- Handle and disable seemingly wrong hires timestamps from ALSA.
- Filter-chain now has loadable plugin modules. The LV2 and sofa plugins are
moved to a separate .so file to make things more modular.
- Rate changes in the graph should now be handled more gracefully by loopback
and filter-chain.
- A regression in the rtp-sap module was fixed where it would in some cases
fail to start.
- A potential crash in the peaks resampler was fixed.
- Many cleanups and other small bug fixes.
- Fix a potential segfault when no fallback driver was set in the config.
- Improve OPUS detection.
- Add ASYNC flag to pw-filter and pw-stream when queue/dequeue is not called
from the process function. This ensure we allocate an extra buffer.
- Discard pending process callbacks when disconnecting. (#3314)
- Cleanups and improvements to the debug environment variable parsing.
- The graph rate was tweaked to better handle very low rates such as those
requested by pavucontrol when it does the signal monitoring.
- An example filter module was added.
- Filter-chain and loopback now disable the resamplers if no rate is specified
and will always follow the graph rate.
- Improve setup of filter-chain. The graph is now created when starting
because this ensure the target graph rate is known.
- Filter-chain can now link notify ports to control ports in the graph.
- Filter-chain now has loadable plugin modules. The LV2 and sofa plugins are
moved to a separate .so file.
- A regression in the rtp-sap module was fixed where it would in some cases
fail to start.
- Module-rt now has options to disable rlimits, portal and rtkit.
- module-raop-discover now has an options to set the latency. (#3247)
- pw-cat now supports overriding all stream properties.
- Disable rate negotiation when the resampler is disabled. We will always
follow the graph rate.
- Set device.icon property for UCM ports as well.
- Improve ALSA recover when using hires timestamps. This fixes some problems
after resume from suspend. (#3315)
- ALSA will now warn and disable hires timestamp when they seem wrong.
They can also be disabled manually with a property.
- V4l2 will now gracefully handle ENOTTY when enumerating frame sizes and
frame rates. (#3325)
- A potential crash in the peaks resampler was fixed. (#3320)
- A client crash in pavucontrol is avoided by always setting a card name.
- The graph rate is now taken correctly when using the FIX flags. (#3317)
- An option was added to ignore the FIX flags of a stream. Also the
documentation for those options was updated. (#3317)
- module-raop-discover now support latency_msec. (#3247)
- Remove an assert and issue a warning/recover instead when a buffer is too
small.
- The device provider does locking when destroying the registry.
Signed-off-by: Markus Volk <f_l_k@t-online.de>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
