Hi! While trying to build HLVM using the trunk of today, I noticed that I couldn't get llvm-gcc-4.0 installed by simply doing ./install llvm- gcc-4.0 in llvm-top. I did a fresh checkout of llvm-top and pulled some other modules by doing ./get VERBOSE=1 PREFIX=/Users/kroepke/Projects/llvm llvm-gcc-4.0 core support cfe hlvm test-suite Afterwards I did: ./build llvm and ./install llvm which left me with LLVM's libraries and tools in llvm-top/installed But I was missing the llvm-gcc-4.0 binaries, which didn't even get installed after issuing ./install llvm-gcc-4.0 in llvm-top. I had to manually do a 'make install' in llvm-top/build.llvm-gcc-4.0/ to get it into ./installed/ Also, I noticed that I ended up with a separate copy of llvm-gcc-4.0 in llvm-top/llvm/ which apparently got checked out while building llvm. Checking with lsof and netstat (combined with the huge time delay the checkout of gcc implied) confirmed there was a second checkout going on. Is this expected, or is it a minor flaw in the build scripts? Thanks, -k -- Kay Röpke http://classdump.org/
Hi Kay, On Sun, 2007-08-12 at 23:07 +0200, Kay Roepke wrote:> Hi! > > While trying to build HLVM using the trunk of today, I noticed that I > couldn't get llvm-gcc-4.0 installed by simply doing ./install llvm- > gcc-4.0 > in llvm-top. > > I did a fresh checkout of llvm-top and pulled some other modules by > doing > > ./get VERBOSE=1 PREFIX=/Users/kroepke/Projects/llvm llvm-gcc-4.0 core > support cfe hlvm test-suite > > Afterwards I did: > ./build llvm > and > ./install llvm > > which left me with LLVM's libraries and tools in llvm-top/installed > But I was missing the llvm-gcc-4.0 binaries, which didn't even get > installed > after issuing ./install llvm-gcc-4.0 in llvm-top. > > I had to manually do a 'make install' in llvm-top/build.llvm-gcc-4.0/ to > get it into ./installed/ > > Also, I noticed that I ended up with a separate copy of llvm-gcc-4.0 in > llvm-top/llvm/ which apparently got checked out while building llvm. > Checking with lsof and netstat (combined with the huge time delay the > checkout > of gcc implied) confirmed there was a second checkout going on.The llvm-top stuff is designed to handle all the dependencies for you. In fact, all you needed to do was issue "./install llvm-gcc-4.0" and it would have checked out llvm for you, built and installed it and then built and installed llvm-gcc-4.0. At least, that's the way it is supposed to work.> > Is this expected, or is it a minor flaw in the build scripts?No, its not expected. I'm trying to replicate here because I thought this was working. There are two problems you reported: 1. llvm-gcc-4.0 should have been checked out into the llvm-top directory. 2. The install of llvm-gcc-4.0 should have worked. Thanks for noting it. I'll take a look and see if there's a bug. FYI: llvm-top isn't ready for prime time yet (hasn't even been announced) as it needs more testing. Thanks for testing! :) Reid.> > Thanks, > > -k
Kay, The "install" script in llvm-top should be fixed now. Thanks for reporting it. Reid. On Sun, 2007-08-12 at 23:07 +0200, Kay Roepke wrote:> Hi! > > While trying to build HLVM using the trunk of today, I noticed that I > couldn't get llvm-gcc-4.0 installed by simply doing ./install llvm- > gcc-4.0 > in llvm-top. > > I did a fresh checkout of llvm-top and pulled some other modules by > doing > > ./get VERBOSE=1 PREFIX=/Users/kroepke/Projects/llvm llvm-gcc-4.0 core > support cfe hlvm test-suite > > Afterwards I did: > ./build llvm > and > ./install llvm > > which left me with LLVM's libraries and tools in llvm-top/installed > But I was missing the llvm-gcc-4.0 binaries, which didn't even get > installed > after issuing ./install llvm-gcc-4.0 in llvm-top. > > I had to manually do a 'make install' in llvm-top/build.llvm-gcc-4.0/ to > get it into ./installed/ > > Also, I noticed that I ended up with a separate copy of llvm-gcc-4.0 in > llvm-top/llvm/ which apparently got checked out while building llvm. > Checking with lsof and netstat (combined with the huge time delay the > checkout > of gcc implied) confirmed there was a second checkout going on. > > Is this expected, or is it a minor flaw in the build scripts? > > Thanks, > > -k