similar to: [LLVMdev] Clang-test and Windows

Hi, I accidentally noticed the following line when building LLVM and Clang on Windows 7 x64 using Mingw64: Linking CXX shared library ..\..\..\..\bin\liblibclang.dll "Liblib" seems a bit overkill. FYI. BTW, for those who happen to search on LLVM, Clang, Windows, and Mingw64: The v3.1 release does NOT build with Mingw64. I believe this has been fixed in the Subversion sources as

Hi, I just did a "make install" on Win7x64 using Mingw64 and it dropped off the files in "C:\Program Files (x86)\LLVM". That's almost right, but nicer would be if the 64-bit build was dropped off in "C:\Program Files\LLVM". I am fairly confident that it is me who is doing something wrong because I simply do this: (retrieve trunk version of LLVM, Clang,

That reminds me: Do the web documents reside in a repository somewhere or should I just grab them using wget? 2012/6/14 Michael Spencer <bigcheesegs at gmail.com> > On Wed, Jun 13, 2012 at 4:02 PM, Mikael Lyngvig <mikael at lyngvig.org> > wrote: > > If nobody else is doing it, I can translate the FAQ into Sphinx as I'd > like > > to begin gradually extending

Hi, Here's the final, confirmed working version of my Windows guide for how to set up a MinGW buildbot slave. Please consider to include it in the documentation on the LLVM website. Basically, it saves the newcoming Windows user about two or three days of experimentation to get it all working. I think those days are important as many people balk at spending days on figuring out how to get

On Sat, Jun 9, 2012 at 12:40 AM, Mikael Lyngvig <mikael at lyngvig.org> wrote: > Hi, > > Here's the final, confirmed working version of my Windows guide for how to > set up a MinGW buildbot slave. Please consider to include it in the > documentation on the LLVM website. > > Basically, it saves the newcoming Windows user about two or three days of >

On Wed, Jun 13, 2012 at 4:47 PM, Mikael Lyngvig <mikael at lyngvig.org> wrote: > That reminds me: Do the web documents reside in a repository somewhere or > should I just grab them using wget? The website is at http://llvm.org/viewvc/llvm-project/www/trunk/ . The llvm docs are in llvm/docs. Which actually makes me wonder if the LLVM-project FAQ (in reference to Chandler's post in

On 28 May 2012, at 16:46, Mikael Lyngvig wrote: > > Hi, > > I accidentally noticed the following line when building LLVM and Clang on Windows 7 x64 using Mingw64: > > Linking CXX shared library ..\..\..\..\bin\liblibclang.dll > > "Liblib" seems a bit overkill. FYI. See http://llvm.org/bugs/show_bug.cgi?id=12620 for links to several threads on the clang

A tiny question (I hardly know what Ninja is, but am looking forward to trying it out): Does the changes also work with MinGW builds? I've got a Windows buildbot slave that does nothing but building LLVM+Clang using MinGW64 all day, every day. Or, is it only for Visual Studio? 2012/6/13 Justin Holewinski <justin.holewinski at gmail.com> > Wow, this is seriously fast on Windows!

Does Clang/Clang++ not have its own set of standard headers? Isn't this a serious issue if Clang/Clang++ is ever to outdo GCC/G++? Is there any work in progress on this? Ideally, Clang would ship as a ready-to-use installation image that included everything needed to use it as the possibly best C and C++ compiler on the market. Or, am I ahead of myself again? Cheers, Mikael -- Love Thy

Hi, [Synopsis: Mikael thinks Windows support is overlooked and that this is a strategic error. You can skip to the next mail now, if you'd like :-) Long, long, long mail follows.] Before I go on, I'd like to informally apologize for my many postings to this mailing list. I have no intentions of spamming it, but I still feel a need to grasp certain things that seem to be implied by the

The irony of this reply is killing me :) On Wed, Jun 13, 2012 at 7:54 PM, Mikael Lyngvig <mikael at lyngvig.org> wrote: > You're not alone :) Don't let it bug you. > > I finally decided to install a GMail extension that enables reply-all for > all messages, because I kept forgetting. Perhaps you can find such an > extension or simply enable reply-all by default?

Hehe, I intentionally left out the group because I just wanted to cheer you up and let you know that there's more than one "retard" on the list. 2012/6/14 Sean Silva <silvas at purdue.edu> > The irony of this reply is killing me :) > > > On Wed, Jun 13, 2012 at 7:54 PM, Mikael Lyngvig <mikael at lyngvig.org>wrote: > >> You're not alone :)

If nobody else is doing it, I can translate the FAQ into Sphinx as I'd like to begin gradually extending it so that it some day becomes more than just bare metal. I figure that extending the FAQ is one way to reduce the "noise" on the various mailing lists. Cheers, Mikael -- -- Love Thy Frog! -------------- next part -------------- An HTML attachment was scrubbed... URL:

btw, the "default reply-to-all" extension for gmail works great! On Wed, Jun 13, 2012 at 8:11 PM, Mikael Lyngvig <mikael at lyngvig.org> wrote: > Hehe, I intentionally left out the group because I just wanted to cheer > you up and let you know that there's more than one "retard" on the list. > > > 2012/6/14 Sean Silva <silvas at purdue.edu> >

Hi, Just a brief follow-up on my link time issue: It was caused by excessive trashing; I tried rebuilding on a box with 8 gigs of RAM and observed the memory load while linking clang.exe: It peaked at 5 gigabytes memory, so now I've written this piece of info into the LLVM/Windows document that I posted earlier (I have already made a substantial number of corrections in the document). All in

On Jun 13, 2012, at 4:47 PM, Mikael Lyngvig wrote: > 2012/6/14 Michael Spencer <bigcheesegs at gmail.com> > On Wed, Jun 13, 2012 at 4:02 PM, Mikael Lyngvig <mikael at lyngvig.org> wrote: > > If nobody else is doing it, I can translate the FAQ into Sphinx as I'd like > > to begin gradually extending it so that it some day becomes more than just > > bare

On Wed, Jun 13, 2012 at 4:02 PM, Mikael Lyngvig <mikael at lyngvig.org> wrote: > If nobody else is doing it, I can translate the FAQ into Sphinx as I'd like > to begin gradually extending it so that it some day becomes more than just > bare metal.  I figure that extending the FAQ is one way to reduce the > "noise" on the various mailing lists. > > > Cheers,

Do you specify CMAKE_BUILD_TYPE if you are using cmake? 2012/05/27 18:21 "Mikael Lyngvig" <mikael at lyngvig.org>: > Hi, > > Just a brief follow-up on my link time issue: It was caused by excessive > trashing; I tried rebuilding on a box with 8 gigs of RAM and observed the > memory load while linking clang.exe: It peaked at 5 gigabytes memory, so > now I've

> > the problem is that very few LLVM developers use or know anything about > Windows. > The only way for this to change is for people who do know and care about > Windows > to step forward, work on improving Windows support, and contribute their > Windows > viewpoint to design discussions etc. > As it is now, Windows users will quite likely drop LLVM because of the

Hi, I'm building using MINGW64 on a very slow system (Intel Atom 330 X2 1.6 GHz), but it seems rather odd that the system has been linking clang.exe for the past two hours. It appears that a couple of gigabytes of virtual memory are being used (causing constant swapping) - the system has only 2 GB of physical memory. Is this a bug in MINGW64 (binutils 2.22) or is it just too little RAM in