I went ahead and filed ticket 599 to address the issue of making the build more
reliable in these situations (llvm-gcc and llvm-g++ being found by the LLVM
build).
On Feb 02, 2010, at 21:55, Jordan Breeding wrote:
> Alright, so since llvm-gcc is now in /bin (in some new tools that might have
>
Alright, so since llvm-gcc is now in /bin (in some new tools that might have
been released in late Jan), MacRuby advice is "try not to build with llvm-gcc",
and the default llvm build searches all of PATH for llvm-gcc, etc. I fixed it
using a lot of extra configuration upfront.
Instead of:
./c
You're building LLVM with llvm-gcc. I don't know if this will work.
Laurent
On Feb 2, 2010, at 4:46 PM, Jordan Breeding wrote:
LLVM version:
Path: .
URL: https://llvm.org/svn/llvm-project/llvm/trunk
Repository Root: https://llvm.org/svn/llvm-project
Repository UUID: 91177308-0d34-0410-b5e6-96
Yeah, I haven't even gotten to the point where I would be building MacRuby,
although I already removed it. I was thinking about removing llvm, but it is
just in /usr/local and a separate copy (for clang) in /opt/llvm. Neither one of
those is getting picked up, this is the one getting picked up:
I rm -rf my llvm repo and pulled again, also don't forget to rake clean
before building macruby.
- Matt
On Tue, Feb 2, 2010 at 4:46 PM, Jordan Breeding wrote:
> LLVM version:
>
> Path: .
> URL: https://llvm.org/svn/llvm-project/llvm/trunk
> Repository Root: https://llvm.org/svn/llvm-project
> Re
LLVM version:
Path: .
URL: https://llvm.org/svn/llvm-project/llvm/trunk
Repository Root: https://llvm.org/svn/llvm-project
Repository UUID: 91177308-0d34-0410-b5e6-96231b3b80d8
Revision: 89156
Node Kind: directory
Schedule: normal
Last Changed Author: dpatel
Last Changed Rev: 89156
Last Changed Da