Yves Goergen

That doesn't seem to work. This is the full output of that command: ``` configure.ac:36: warning: macro 'AM_PROG_LIBTOOL' not found in library configure.ac:36: error: possibly undefined macro: AM_PROG_LIBTOOL If this...

Yes, with the help from the above comments I could build the source code on a Raspberry Pi and have successfully copied that binary to other ARM32-based systems (other Raspberry...

That works better. The key point seems to be searching for `["y"]` instead of `"y"` (at the default array index of 0 in the data array). Judging from the examples...

Not sure what "co-transparent" means but the transparency seems useless to me as it is now. It's just unreliable and doesn't work most of the time. Too frustrating to even...

Ah you mean transparent in both directions. I mean transparent to itself. Neither is true at the moment. Both are needed for colour transparency to be frustration-free. But as I'm...

Oh, I see, I have version 4.2.0. Need to update that again.

Okay, how can I update this? It doesn't do with `npm update -g` (all other tools are updated but not csso). The package csso-cli stays at 3.0.0 and `csso --version`...

Any idea how I should follow your suggestion? It seems impossible with npm. Or there's a packaging bug in csso.

@lahmatiy Looks like the version you suggested is not available. See https://github.com/css/csso-cli/issues/25

Indeed, I observed this with a custom property: ```css .something { --link-hover-color-l: calc(var(--link-color-l) + max(0%, (100% - var(--link-color-l)) * var(--link-hover-lf)) - max(0%, var(--link-color-l) * (0 - (var(--link-hover-lf))))); } ```