http://llvm.org/bugs/show_bug.cgi?id=11201
Summary: LLVM_ETCDIR (used in Path.cpp) results in path being
hard-coded into object file
Product: new-bugs
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P
Component: new bugs
AssignedTo: [email protected]
ReportedBy: [email protected]
CC: [email protected]
In a release build Path.o is the only object file with a path encoded in it
(the
install directory). This is bad. Consider the binary releases we do: LLVM is
built by (say) me on my machine and installed in some directory, for example in
/home/duncan/llvm-3.0/install. The path /home/duncan/llvm-3.0/install/etc/llvm
is then hard-wired into the binaries. We now tar up the install directory and
distribute it. People install this somewhere, for example in /usr/local. But
their binaries will try to do things with
/home/duncan/llvm-3.0/install/etc/llvm
that doesn't exist on their machines!
Also, this causes bootstrap comparison failures: when building LLVM+clang with
itself in a bootstrap, the Path.o object files from different stages fail to
match because they were built in different directories.
--
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.
_______________________________________________
LLVMbugs mailing list
[email protected]
http://lists.cs.uiuc.edu/mailman/listinfo/llvmbugs
