On Sat, 6 Jan 2024 07:21:29 -0600 2QdxY4RzWzUUiLuE@potatochowder.com wrote:
I know that pete said that the question marks in the original post are artifacts, but I'm still hung up on the fact that in that original post, the filenames appear to be relative rather than absolute, as if some environment variable is unset, or perhaps mistakenly set to an empty string instead of being unset.
I admit that I haven't read every post in excruciating detail, but if something in pete's system is looking in usr/lib, but all the people helping are looking in /usr/lib, that might explain some of the apparently contradictory results.
Can pete please verify that the warnings name files in /usr/lib/... (an absolute path) and not usr/lib/... (a relative path)? Or perhaps capture the output from commands that generate the warnnings in a file and post/attach that instead of (presubably) copying and pasing from a terminal program (which is evidently not a lossless copy)?
relatives paths are perfectly normal here. That's how pacman works.