The configure script finds the right C compiler, but it uses the LLVM linker from a previous build. What do I do?
The configure script uses the PATH to find executables, so if it’s grabbing the wrong linker/assembler/etc, there are two ways to fix it: • Adjust your PATH environment variable so that the correct program appears first in the PATH. This may work, but may not be convenient when you want them first in your path for other work. • Run configure with an alternative PATH that is correct. In a Borne compatible shell, the syntax would be: % PATH=[the path without the bad program] ./configure … This is still somewhat inconvenient, but it allows configure to do its work without having to adjust your PATH permanently.
Related Questions
- When I compile software that uses a configure script, the configure script thinks my system has all of the header files and libraries it is testing for. How do I get configure to work correctly?
- The configure script finds the right C compiler, but it uses the LLVM linker from a previous build. What do I do?
- How do I configure the programs that Konqueror uses to open different types of files?
