Lukas Märdian

Thanks for your quick response. I tried to re-produce the problem by running `python3 tools/build.py` on `master` of jerryscript alone. It works. Closing this issue.

Actually, I had another look into this. And the Jerryscript revision in question is: 56e328be416c32d31988644a57e18aeb959e6be2 It builds successfully when I run `python3 tools/build.py` but it does fail with the above...

Thanks for getting back to this! I've now been able to reproduce the failure on 56e328b, using `python3 tools/build.py --debug --all-in-one ON`. It seems to be related to the `-D_FORTIFY_SOURCE=2`...

I've now worked around this problem by building the Debian/Ubuntu package using this option: ``` CMAKE_OPTIONS+=-DCMAKE_BUILD_TYPE=MinSizeRel ``` But it might still be good to look into this at some point,...

I cannot seem to reproduce it on v2.4.0. Previously I could trigger it using `python3 tools/build.py --debug --all-in-one ON`. But the `--all-in-one` option is gone from v2.4.0, using `--amalgam ON`...

I agree that having the `mii-monitor-interval` set to 100 would be the common case for detecting link failures of the underlying physical interfaces of the bond. I did not find...

Yes. Maybe it would be worth calculating once in the beginning if there are any double-digit weeks in the current test. If so, fill=3 else fill=2 Then use python's FormatSpec...

Thanks for your quick reply! Yeah... I just saw there are new `test/` and `tests/` directories, which are for some reason not part of the Debian package... Maybe the "old"...

> Yeah - I'm assuming you're using the AppImage? No. I'm using the .deb package actually. Thanks for looking into it!

Awesome, thank you! Will there be a new release including this change, soon? Oh, nevermind :) https://github.com/Textualize/rich/releases/tag/v13.2.0