[LLVMbugs] [Bug 5191] New: release management; llvm-config has absolute paths

bugzilla-daemon at cs.uiuc.edu bugzilla-daemon at cs.uiuc.edu
Wed Oct 14 16:25:39 PDT 2009


http://llvm.org/bugs/show_bug.cgi?id=5191

           Summary: release management; llvm-config has absolute paths
           Product: new-bugs
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: new bugs
        AssignedTo: unassignedbugs at nondot.org
        ReportedBy: nicholas at mxc.ca
                CC: llvmbugs at cs.uiuc.edu


I did an LLVM build with --prefix=/home/nicholas/2.6/llvm-2.6-install. The
resulting bin/llvm-config binary has these lines:
  my $PREFIX              = q{/home/nicholas/2.6/llvm-2.6-install};
  my $LLVM_SRC_ROOT       = q{/home/nicholas/2.6/llvm-2.6};
  my $LLVM_OBJ_ROOT       = q{/home/nicholas/2.6/llvm-2.6};
and if I were to also have built with llvm-gcc, these:
  my $LLVMGCCDIR          = q{/home/nicholas/llvm-gcc/install};
  my $LLVMGCC             = q{/usr/local/bin/llvm-gcc};
  my $LLVMGXX             = q{/usr/local/bin/llvm-g++};

There's nothing wrong with this until you start thinking about a release. We
don't know where people are going to put their llvm install trees. Can we
mandate that they unpack into /usr/local/? Should we have a special "relative
to $0" mode for releases?


-- 
Configure bugmail: http://llvm.org/bugs/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.



More information about the llvm-bugs mailing list