Ralf Corsepius <rc040203@xxxxxxxxxx> writes: > Right, but it suffers from the same limitations as Sergei's approach. > If you'd want to have a better guess, you have to apply some magic > examining the multilib subdir involving compiler internals, e.g. > gcc --print-multi-os You have to decide what you're trying to accomplish. My goal was to handle a few common cases in a relatively safe way to reduce the number of places where the user has to use --libdir. I think it accomplishes that. Completely eliminating the need for the user to ever use --libdir to set the installation path is a much harder (possibly impossible) problem. Anyway, Works For Me. People can certainly do more work if they want, or come up with other solutions, or just bail and ask the user to always use --libdir. -- Russ Allbery (rra@xxxxxxxxxxxx) <http://www.eyrie.org/~eagle/> _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx https://lists.gnu.org/mailman/listinfo/autoconf