On Thu, 2005-05-19 at 22:34 +0100, Aaron Gray wrote:> I do not really feel upto looking into makefiles yet as I don't really know > automake, configure scripts, etc, etc >Aaron, its trivial. Open up tools/llvm-ar/Makefile in an editor. Go to the TOOLNAME line, delete the space at the end of the line, save the file, rebuild.> >I'll patch the makefiles when UIUC's CVS server isn't so sluggish.The patches are committing right now, albeit slowly.> > Okay, I'm working from the 1.5 release at the moment. I will move to > checking the CVS Cygwin build once the groff error is solved. I believe I > found another error in the post 1.5 "fork" CVS before the 1.5 release :(Not sure what you mean by that.> > Thanks for solving that. I do not mind doing the Cygwin builds, although I > wish I had updated the RAM on this machine to 1GByte as the whole build > process takes over three hours. It would be good to workout how to do > non-debug builds as that would speed up the linking, which is particularly > slow.Yeah, cygwin's a bit of a pig. To do a release build, just do: make ENABLE_RELEASE=1 that's all there is to it. You might want to take a gander at http://llvm.cs.uiuc.edu/docs/MakefileGuide.html> > I don't want to be a slave driver but any thoughts on the groff error ???:)Nope, because I haven't seen it on the list. Can you repost? Reid -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20050519/c5119dca/attachment.sig>
>Aaron, its trivial. Open up tools/llvm-ar/Makefile in an editor. Go to >the TOOLNAME line, delete the space at the end of the line, save the >file, rebuild.okay, done that, just got to rebuild .... 2 hours later ... :)>The patches are committing right now, albeit slowly.Okay I will check the CVS build tomorrow.>> Okay, I'm working from the 1.5 release at the moment. I will move to >> checking the CVS Cygwin build once the groff error is solved. I believe I >> found another error in the post 1.5 "fork" CVS before the 1.5 release :( > > Not sure what you mean by that.The CVS post the 1.5 freeze has a possible cygwin build error I bumped in to.>> Thanks for solving that. I do not mind doing the Cygwin builds, although >> I >> wish I had updated the RAM on this machine to 1GByte as the whole build >> process takes over three hours. It would be good to workout how to do >> non-debug builds as that would speed up the linking, which is >> particularly >> slow. > >Yeah, cygwin's a bit of a pig.Yep. I should have my Linux laptop working but it is stuck with Fedora Core 1 386 build and is too damb slow with too little RAM (256MB), plus I have forgotten the password !!! Have to get Core 3 and some hand me down RAM from this machine when I update it.>To do a release build, just do: > make ENABLE_RELEASE=1 >that's all there is to it.Okay.>You might want to take a gander at >http://llvm.cs.uiuc.edu/docs/MakefileGuide.htmlokay>> I don't want to be a slave driver but any thoughts on the groff error >> ???:) >Nope, because I haven't seen it on the list. Can you repost?I'll do it in a separate post ... Aaron
On Thu, 2005-05-19 at 23:06 +0100, Aaron Gray wrote:> okay, done that, just got to rebuild .... 2 hours later ... :)In this case, you only need to rebuild the two tools. You can do that from the top level build directory with: make -C tools/llvm-ar make -C tools/llvm-ranlib That should cut the 2 hours down to minutes. :) Reid -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20050519/2fd00c98/attachment.sig>
On Thu, May 19, 2005 at 02:50:54PM -0700, Reid Spencer wrote:> Yeah, cygwin's a bit of a pig. To do a release build, just do: > make ENABLE_RELEASE=1Actually, it's "make ENABLE_OPTIMIZED=1". Perhaps it should also allow ENABLE_RELEASE=1 as a synonym. Note that if you run ./configure the usual way, you *always* have to run "make ENABLE_OPTIMIZED=1" to build, and if you ever run just "make" it will happily do a debug build for you. Note that the objdir can hold 3 separate build trees for the same source code: Debug, Release, and Profile, with those subdirectory names. To make life easier for yourself, run "configure --enable-optimized" and it will then default to ALWAYS building release mode, assuming you don't want debug mode at all. This is documented here: http://llvm.cs.uiuc.edu/docs/GettingStarted.html#config Personally, I think --enable-optimized is a strange name, because why would anyone want to "disable" optimization? :) Maybe it should be something like --build-optimized, --build-profile, and --build-debug, or even --build={opt,prof,debug} since it's a 3-way switch, and you can't pick and choose more than one of them at a time. -- Misha Brukman :: http://misha.brukman.net :: http://llvm.cs.uiuc.edu
On Thu, 2005-05-19 at 18:04 -0500, Misha Brukman wrote:> On Thu, May 19, 2005 at 02:50:54PM -0700, Reid Spencer wrote: > > Yeah, cygwin's a bit of a pig. To do a release build, just do: > > make ENABLE_RELEASE=1 > > Actually, it's "make ENABLE_OPTIMIZED=1". Perhaps it should also allow > ENABLE_RELEASE=1 as a synonym.Shows you how long its been since I've done a release build :)> Personally, I think --enable-optimized is a strange name, because why > would anyone want to "disable" optimization? :) Maybe it should be > something like --build-optimized, --build-profile, and --build-debug, or > even --build={opt,prof,debug} since it's a 3-way switch, and you can't > pick and choose more than one of them at a time.I'd recommend (and have long thought about): --build-mode={opt,prof,debug,...} There doesn't need to be only three. They really should be a set so that you could do "optimized debug" or "profiled debug" or "profiled optimized", etc. There might also be some other types of builds that someone would want but I can't think of any right now. Anyhow, this is in my notes for separating the makefile system to its own project. Reid. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20050519/7b15b3f0/attachment.sig>