nostr:nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqlwucuwz95hsr8phuqpdyjvkqp50vt8eyeuk6wfyyxgdn3uzd6apq5q6679 Have you tried nix-ld or similar "FHS" restoration techniques?

Reply to this note

Please Login to reply.

Discussion

nostr:nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpq0smdhqjvt80rt7g3mgqvwhvxs4qh8few5pyfgs6wcxap7w4vrl3sagx3yv Yes I've enabled nix-ld and this seems to sometimes work, but sometimes not. It did not help for my locally built Rust project, where I had to configure LD_LIBRARY_PATH manually in a shell.nix. Not sure why.

Because the shell is isolated and that has advantages of fine-tuning what you want there to be available but you really need to know what you're doing is the tradeoff.

Dynamically linked stuff is one of these headaches you must deal with if you don't know exactly what's happening. If sth is not found, look for it in the nix store and add it to the LD_LIBRARY_PATH.

I mostly got away with just putting the cargo bin dir on path during my limited number rust projects. But e.g. Python projects linking to rust can cause such problems.