Uninstalling TOT to use a branch release

Hello everybody,

I have been puzzling over how to uninstall the SVN Head release of LLVM for compatibility with llvm-gcc 4.2-2.6. Our project is based on 2.6 of LLVM but I needed to install TOT to check if a bug was ours or had been fixed in the latest LLVM. Now that the bug is fixed, I need to go back to LLVM 2.6. I used CMake to build TOT on MacOSX 10.5.x and there is no "make uninstall" option. When I try to build LLVM 2.6 it seems to skip over some of the files during the "make install" stage and llvm-g++ doesn't do its --emit-llvm functionality as a result.

If you need more information about the error I get or what the project I'm working on is, I'll be watching the list carefully for replies.

Thanks for your time,

--Sam

Still unresolved.

The exact error message I get each time I try to use llvm-g++ is 'unrecognized command line option "-emit-llvm-bc" '. I've tried reinstalling both LLVM and LLVM-GCC using MacPorts. I've searched the archives of the mailing list. Does anybody know what files need to be removed from a SVN head install of LLVM to make my Mac running MacOSX 10.5.x work with version 2.6 again?

From: Samuel Crow <samuraileumas@yahoo.com>
To: LLVM Developers Mailing List <llvmdev@cs.uiuc.edu>
Sent: Tue, April 13, 2010 12:54:42 PM
Subject: [LLVMdev] Uninstalling TOT to use a branch release

Hello everybody,

I have been puzzling over how to uninstall the SVN Head

release of LLVM for compatibility with llvm-gcc 4.2-2.6. Our project is
based on 2.6 of LLVM but I needed to install TOT to check if a bug was ours or
had been fixed in the latest LLVM. Now that the bug is fixed, I need to go
back to LLVM 2.6. I used CMake to build TOT on MacOSX 10.5.x and there is
no "make uninstall" option. When I try to build LLVM 2.6 it seems to skip
over some of the files during the "make install" stage and llvm-g++ doesn't do
its --emit-llvm functionality as a result.

If you need more information

about the error I get or what the project I'm working on is, I'll be watching
the list carefully for replies.

Thanks for your

time,

--Sam

Samuel Crow wrote:

Still unresolved.
  
I don't have an answer to your question other than the obvious but unsatisfactory answer of looking manually in the install directory for all LLVM tools and libraries. It shouldn't be that bad, but I understand that it is less than ideal.

I suppose another option is to install LLVM 2.6 into a different directory and set your $PATH to search that directory first. That should at least verify that your problem stems from having non-LLVM 2.6 components lying around.

Moving to your other issue, are you sure that -emit-llvm-bc is the right option name? Isn't it just -emit-llvm? I seem to recall reading about an -emit-llvm-bc option but then discovering that the document was wrong.

-- John T.

Hello John,

That is the option that gets passed to cc1plus or whatever the compiler driver is called. I get that error message whenever I try to use llvm-g++ with the --emit-llvm option enabled.

Thanks for trying anyway,

--Sam

Moving to your other issue, are you sure that -emit-llvm-bc

is the right option name? Isn't it just -emit-llvm? I seem to recall
reading about an -emit-llvm-bc option but then discovering that the document was
wrong.

-- John T.