Re: cmake PG should ensure correct libdir, otherwise ports are broken on linux

[Ken Cunningham]

There’s a collection of software that doesn’t work properly on 64 bit linux. Exactly the same deal with macOS, which is why we have some universal software now. The best option is to look at what every other Linux distribution on Earth does, and copy that. That is precisely what I am suggesting you might consider doing before it is Too Late. That is why cmake is looking for lib64 now.  The point of pointing out that these directories exist for a reason is simply to make sure that folks realize that doing an expedient incorrect fix is generally  a recipe for disaster, and then it has to be all undone later and every single thing rebuilt. Personally, I’m going to continue using Debian, so this doesn’t matter to me in the slightest. Whether it ever matters at all to anyone is an interesting question to ponder, but it might.  K Sent from my iPhone On Sep 17, 2024, at 6:26 PM, Sergey Fedorov <vital....@gmail.com> wrote:  On Wed, Sep 18, 2024 at 7:12 AM Ken Cunningham <ken.cunningham.web...@gmail.com> wrote: Of course, if you over-write 64 bit libs with 32 bit libs of the same name, or vice versa, in the same location, you are just hosed, ldconfig or no ldconfig. Which is why linux has the lib32 and lib64 subfolders iin the first place. If I build something for i386 and something else for x86_64 on macOS (which is technically possible) without knowing what and why I am doing, that won’t work either. Doing silly stuff will bring silly results. TBH, I don’t see a meaningful reason why a non-developer would want to build for 32-bit on a 64-bit system (visa versa perhaps is not even possible). On macOS it might make sense on old systems, but why on modern Linux?