FS#73500 - [duktape] support polkit by linking with libm
Attached to Project:
Community Packages
Opened by tinywrkb (tinywrkb) - Tuesday, 25 January 2022, 17:04 GMT
Last edited by Toolybird (Toolybird) - Tuesday, 02 August 2022, 23:30 GMT
Opened by tinywrkb (tinywrkb) - Tuesday, 25 January 2022, 17:04 GMT
Last edited by Toolybird (Toolybird) - Tuesday, 02 August 2022, 23:30 GMT
|
Details
Polkit now supports Duktape as the Javascript engine but
it's failing with the error: "polkitd[5586]:
/usr/lib/polkit-1/polkitd: Relink
`/usr/lib/libduktape.so.206' with `/usr/lib/libm.so.6' for
IFUNC symbol `ceil'".
So I suggest forcing linking against libm. I also added a patch with the packaging/buildsystem changes from https://github.com/svaarala/duktape/pull/2457, so we can drop most of the buildsystem hacks, though I suggest removing the optimization flag `-Os` and just default to whatever we have in CFLAGS. This also enables full RELRO, D_FORTIFY_SOURCE. |
This task depends upon
Closed by Toolybird (Toolybird)
Tuesday, 02 August 2022, 23:30 GMT
Reason for closing: Fixed
Additional comments about closing: Reporter says "Change was implemented."
Tuesday, 02 August 2022, 23:30 GMT
Reason for closing: Fixed
Additional comments about closing: Reporter says "Change was implemented."
[1] https://stackoverflow.com/questions/8140494/why-am-i-getting-a-gcc-undefined-reference-error-trying-to-create-shared-objec
Here's an updated patch that also fixes an issue that my previous suggestion introduced to the prefix variable of the pkgconfig file.
I attached an updated patch for the packaging.
Why is this bug report being ignored? Please look at the changes here.
Is it safe to upgrade or should we stick to tinywrkb's PKGBUILD?
* It is safe to upgrade, unless you depend on this feature request being implemented.
So unless I'm doing something wrong, I don't see a way to avoid linking duktape to libm, and if there's no other way to solve, then this is not a feature request but a packaging issue that should be fixed.