llvm.org GIT mirror llvm / b96646f
Removed information on common build problems. That is now documented in the FAQ (FAQ.html). git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@9087 91177308-0d34-0410-b5e6-96231b3b80d8 John Criswell 16 years ago
1 changed file(s) with 3 addition(s) and 60 deletion(s). Raw diff Collapse all Expand all
10091009
10101010
10111011
1012 Below are common problems and their remedies:
1013
1014
1015
When I run configure, it finds the wrong C compiler.
1016
1017 The configure script attempts to locate first gcc and
1018 then cc, unless it finds compiler paths set in CC and
1019 CXX for the C and C++ compiler, respectively.
1020
1021 If configure finds the wrong compiler, either adjust your
1022 PATH environment variable or set CC and CXX
1023 explicitly.
1024

1025
1026
I compile the code, and I get some error about /localhome.
1027
1028 There are several possible causes for this. The first is that you
1029 didn't set a pathname properly when using configure, and it
1030 defaulted to a pathname that we use on our research machines.
1031

1032 Another possibility is that we hardcoded a path in our Makefiles. If
1033 you see this, please email the LLVM bug mailing list with the name of
1034 the offending Makefile and a description of what is wrong with it.
1035
1036
The configure script finds the right C compiler, but it
1037 uses the LLVM linker from a previous build. What do I do?
1038
1039 The configure script uses the PATH to find
1040 executables, so if it's grabbing the wrong linker/assembler/etc, there
1041 are two ways to fix it:
1042
1043
  • Adjust your PATH environment variable so that the
  • 1044 correct program appears first in the PATH. This may work,
    1045 but may not be convenient when you want them first in your
    1046 path for other work.
    1047

    1048
    1049
  • Run configure with an alternative PATH that
  • 1050 is correct. In a Borne compatible shell, the syntax would be:
    1051

    1052 PATH= ./configure ...
    1053

    1054 This is still somewhat inconvenient, but it allows
    1055 configure to do its work without having to adjust your
    1056 PATH permanently.
    1057
    1058
    1059
    I've upgraded to a new version of LLVM, and I get strange build
    1060 errors.
    1061
    1062 Sometimes changes to the LLVM source code alters how the build system
    1063 works. Changes in libtool, autoconf, or header file dependencies are
    1064 especially prone to this sort of problem.
    1065

    1066 The best thing to try is to remove the old files and re-build. In most
    1067 cases, this takes care of the problem. To do this, just type make
    1068 clean and then make in the directory that fails to build.
    1069

    1070
    1071
    1012 If you are having problems building or using LLVM, or if you have any other
    1013 general questions about LLVM, please consult the
    1014 Frequently Asked Questions page.
    10721015
    10731016
    10741017

    Links