The commit adding uloop support failed to actually install the .so and
add the correct dependencies.
[2022/12/26 18:19:38:1835] E: lws_create_context: failed to load evlib_uloop
Fixes: 1557ac367a ("libwebsockets: enable built in uloop support")
Signed-off-by: John Crispin <john@phrozen.org>
This library needs the kernel config option 'CONFIG_GPIO_CDEV_V1=y' to
be set. If this is not set, the tool 'gpioinfo' produces the error message
'error creating line iterator'. Add the missing kernel config option to
build CDEV with API Version 1 fixes this.
Signed-off-by: Florian Eckert <fe@dev.tdt.de>
Version 2.03.17 - 10th November 2022
====================================
Add new options (--fs, --fsmode) for FS handling when resizing LVs.
Fix 'lvremove -S|--select LV' to not also remove its historical LV right away.
Fix lv_active field type to binary so --select and --binary applies properly.
Switch to use mallinfo2 and use it only with glibc.
Error out in lvm shell if using a cmd argument not supported in the shell.
Fix lvm shell's lastlog command to report previous pre-command failures.
Extend VDO and VDOPOOL without flushing and locking fs.
Add --valuesonly option to lvmconfig to print only values without keys.
Updates configure with recent autoconf tooling.
Fix lvconvert --test --type vdo-pool execution.
Add json_std output format for more JSON standard compliant version of output.
Fix vdo_slab_size_mb value for converted VDO volume.
Fix many corner cases in device_id, including handling of S/N duplicates.
Fix various issues in lvmdbusd.
libdm changes:
Version 1.02.187 - 10th November 2022
=====================================
Add DM_REPORT_GROUP_JSON_STD for more JSON standard compliant output format.
Signed-off-by: Daniel Golle <daniel@makrotopia.org>
this Makefile still used `CONFIG_GCC_USE_VERSION_*` to select various
compilation options, for GCC versions that are antiquated
convert to parsing the major from the `CONFIG_GCC_VERSION` which will
always exist and can also be used with range logic
intent seemed to be:
* `-DEXTERN_UNLESS_MAIN_MODULE=static` for "=10" (and newer, probably)
* no additional options for "not =10" (or older, probably)
GCC 11 or 12 would likely revert to the default (not =10) option,
because 10 was the newest at the time, and 11 and 12 are "not 10"
Signed-off-by: Tony Butler <spudz76@gmail.com>
Changes from 5.2.0 to 5.2.1
---------------------------
1. Infrastructure upgrades: PMA version Avon 8.
2. Issues related to the sign of NaN and Inf values on RiscV have
been fixed; gawk now gives identical results on that platform as
it does on others.
3. A few issues with the debugger have been fixed.
4. More subtle issues with untyped array elements being passed to
functions have been fixed.
5. The rwarray extension's readall() function has had some bugs fixed.
6. The PMA allocator is now supported on FreeBSD, OpenBSD and Linux on S/390x.
Is is now supported also on both Intel and M1 macOS systems.
7. There have been several minor code cleanups and bug fixes. See the
ChangeLog for details.
Signed-off-by: Daniel Golle <daniel@makrotopia.org>
CHANGES:
* fsck.exfat: Keep traveling files even if there is a corrupted
directory entry set.
* fsck.exfat: Introduce the option "b" to recover a boot sector even
if an exFAT filesystem is not found.
* fsck.exfat: Introduce the option "s" to create files in
"/LOST+FOUND", which have clusters allocated but was not belonged
to any files.
* fsck.exfat: Rename '.' and '..' entry name to the one user want.
NEW FEATURES:
* fsck.exfat: Repair corruptions of an exFAT filesystem.
Please refer to fsck.exfat manpage to see what kind of corruptions
can be repaired.
* exfat2img: Dump metadata of an exFAT filesystem. Please refer to
exfat2img manpage to see how to use it.
BUG FIXES:
* fsck.exfat: Fix an infinite loop while traveling files.
* tune.exfat: Fix bitmap entry corruption when adding new volume
lablel.
Signed-off-by: Daniel Golle <daniel@makrotopia.org>
1.5.1 - 14 November 2022, Ludovic Rousseau
Add support of
Access IS ATR220 with idProduct: 0x0184
Alcor Link AK9567
Alcor Link AK9572
BLUTRONICS TAURUS NFC
CHERRY SmartTerminal ST-1144
CREATOR CRT-603(CZ1) CCR
Dexon Tecnologias Digitais LTDA DXToken
ESMART Reader ER433x ICC
ESMART Reader ER773x Dual & 1S
Flight system consulting Incredist
Ledger Nano S
Ledger Nano S Plus
Ledger Nano SP
Ledger Nano X
SafeNet eToken Fusion
Sensyl SSC-NFC Reader
Adjust USB drivers path at run-time via environment variable PCSCLITE_HP_DROPDIR
configure.ac: add --enable-strict option
Fix a problem with AUTO PPS readers and ATR convention inverse cards
examples/scardcontrol:
- add support of 6A xx error codes
- check WinSCard error early
- parse wLcdLayout & bEntryValidationCondition
macOS: log non sensitive strings as "%{public}s"
Some other minor improvements
What's Changed
Fix debug logging of lang in ccid.c in LudovicRousseau/CCID#96
Signed-off-by: Daniel Golle <daniel@makrotopia.org>
this Makefile still used `CONFIG_GCC_USE_VERSION_*` to select various
compilation options, for GCC versions that are antiquated
convert to parsing the major from the `CONFIG_GCC_VERSION` which will
always exist and can also be used with range logic
intent seemed to be:
* `-flto` for "not =10" (or newer, probably)
* no additional options for "=10" (and newer, probably)
GCC 11 or 12 would likely revert to the default (not =10) option,
because 10 was the newest at the time, and 11 and 12 are "not 10"
unsure of what actually works, perhaps `-flto` works in all versions by
now (possibly early gcc 10 bug workaround?)
GCC 11 will have been using `-flto` anyway by the current logic and I
guess it must be working or there would have been changes
Signed-off-by: Tony Butler <spudz76@gmail.com>
this Makefile still used `CONFIG_GCC_USE_VERSION_*` to select various
compilation options, for GCC versions that are antiquated
convert to parsing the major from the `CONFIG_GCC_VERSION` which will
always exist and can also be used with range logic
intent seemed to be:
* `-flto` for "not =10" (or newer, probably)
* no additional options for "=10" (and newer, probably)
GCC 11 or 12 would likely revert to the default (not =10) option,
because 10 was the newest at the time, and 11 and 12 are "not 10"
unsure of what actually works, perhaps `-flto` works in all versions by
now (possibly early gcc 10 bug workaround?)
GCC 11 will have been using `-flto` anyway by the current logic and I
guess it must be working or there would have been changes
Signed-off-by: Tony Butler <spudz76@gmail.com>
