#28698: llvm 2.8 buildroot leaky --------------------------------------+------------------------------------- Reporter: howarth@… | Owner: erickt@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.2 Keywords: | Port: llvm --------------------------------------+------------------------------------- Comment(by howarth@…): I suspect you will see the same problem in MacPorts (as I saw in fink with my llvm-clang packaging). Previously, the LDFLAGS and LD.Flags were handled inappropriately. If you already had installed an earlier version of llvm in /opt/local/lib and passed -L/opt/local/lib on LDFLAGS for the build of the new llvm, there would be misc build failures. These were always suppressed by uninstalling the older release of llvm. The problem was due to the fact that LDFLAGS was placed in front of LD.Flags in the LINK command in Makefile.rules. This caused a linkage on the new executables against the old llvm libraries in /opt/local/lib instead of the newly built ones. See... http://lists.cs.uiuc.edu/pipermail/cfe-dev/2011-March/013760.html http://lists.cs.uiuc.edu/pipermail/cfe-dev/2011-March/013778.html http://lists.cs.uiuc.edu/pipermail/cfe-dev/2011-March/013783.html http://lists.cs.uiuc.edu/pipermail/cfe-dev/2011-March/013784.html Of course if MacPorts never had a llvm package before llvm 2.8, you won't see the problem. It would manifest itself if llvm 2.7 was installed and llvm 2.8 was built. Note you won't see this problem with llvm 2.9 because my patch is committed upstream for that release. -- Ticket URL: <https://trac.macports.org/ticket/28698#comment:4> MacPorts <http://www.macports.org/> Ports system for Mac OS