They didn't generate on v0.5.0 due to a bug.
v0.5.1 fixed that bug.
Slipped through "rustic-rs: 0.5.0 -> 0.5.1" (484af2ff83ec84151e6e4e01bb7c0d147f2d5d89)
`tsm-client` is delivered with its
own `lib{crypto,ssl}.so` implementation.
Beginning with version 8.1.9.1, those `.so`-files came with
absolute symlinks to `/opt/...` causing `autoPatchelf`
to abort with error messages of the form
> error: auto-patchelf could not satisfy dependency libssl.so.1.1
I was under the impression that a new dependency
got introduced and added `openssl` to `builtInputs`
in commit 5ad0ecb9019e964d2abfe034e184f8b846e42dfa.
This fixed the build, but `tsm-client` no longer
linked against its own ssl implementation.
The commit at hand corrects that mistake:
It adds a small `preFixup` script that finds
and adapts absolute symlinks to `/opt/`,
so that `autoPatchelfHook` finds those
`so`-files again and sets RPATH properly.
This permits to drop `openssl` from the dependency list again.
Since commit 4e300e071b97e1e3a6ba4d856cc65e5386366f6f
building `tsm-client` fails with error messages
> error: auto-patchelf could not satisfy dependency libcrypt.so.1 wanted by [...]
Luckily, commit 9b766dd41b9b49cb0c1b1f3317fc2273f1f8f3a0
introduces `libxcrypt-legacy` which again provides `libcrypt.so.1`.
The former packages has seen its last release in 2020-10 and can be
considered abandoned. Meanwhile a new fork has appeared in
faust-cchardet, that we're going to use in its place.
Co-Authored-By: Robert Schütz <nix@dotlambda.de>
due to 2e9f70d496
there is another "sleep", which is now wrongly substituted.
This fixes the error:
Failed to inhibit: Invalid what specification
/nix/store/if12v01xkqladifvk8yqjdpbp6sisg74-coreutils-9.1/bin/sleep:shutdown
Signed-off-by: Florian Brandes <florian.brandes@posteo.de>
It won't be enough to fix cross in all cases, but it is in at least
one: pywayland. I've only made the change in cases I'm confident it's
correct, as it would be wrong to change this when python.interpreter
is used in wrappers, and possibly when it's used for running tests.
with structuredAttrs lists will be bash arrays which cannot be exported
which will be a issue with some patches and some wrappers like cc-wrapper
this makes it clearer that NIX_CFLAGS_COMPILE must be a string as lists
in env cause a eval failure
