Originally Posted by wildwizard
There are plenty of us with multilib enabled systems that compile code on a regular basis but never have these sorts of problems.
Which is why I asked for the output from export as it would show what he has done to his systems environment to cause this error. And setting yet another environment variable is not a fix, it is just covering up the problem further and may result in even more failures in the long term.
And how about the people with multilib enabled systems who compile code on a regular basis who do
have these sorts of problems?
I maintain a few hundred of my own SlackBuild scripts for the software I use. Most software builds fine without the need of adding an LDFLAGS env variable to force the linker to look in the correct place. Very few of them don't work correctly, most likely because of something amiss in their configure scripts.
This isn't necessarily due to user error or a broken environment. The issue pops up from time to time here and elsewhere. I'm not the first person to suggest this, and I doubt I'll be the last.