[LLVMdev] Building llvm-gcc4
rspencer at reidspencer.com
Wed Dec 20 10:49:05 PST 2006
On Wed, 2006-12-20 at 02:10 -0800, Erick Tryzelaar wrote:
> Reid Spencer wrote:
> >> If not, does it make
> >> sense to package the two in the two packages?
> >> Macports is a source-based
> >> packaging system, so it would seem odd to have to temporarily install
> >> llvm-gcc to build llvm, but then install llvm-gcc in a separate package.
> > That issue goes away with llvm-gcc4. You would simply build llvm and
> > then build llvm-gcc4. With llvm-gcc3, its a little more contorted:
> > 1. build llvm tools only (don't build the runtime)
> > 2. build llvm-gcc3
> > 3. build the llvm runtime library
> Hi Reid,
> I got llvm all up and running, thanks.
> I'm now trying to set up
> llvm-gcc4. Does llvm-gcc4 require the llvm object files, or can I
> install llvm, remove all the intermediary files, and then build
llvm-gcc4 links in the objects and libraries built by LLVM, so you can't
> Also, if I'm just doing a one-off build, do I have to make an
> obj and install directory, or can I just build it straight out of the
> llvm-gcc4 source directory?
The recommended way to build any gcc or variant is in a separate obj
directory. It will make things much easier when you want to rebuild (rm
> Finally, do I have to install into the
> parallel install directory, or can I install into any directory I'd like?
You can install anywhere you like, just set --prefix=/path/to/install/to
on your llvm-gcc configure command.
> Thanks again,
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu
More information about the llvm-dev