similar to: [LLVMdev] Linking tblgen debug executable (without symbols) onMinGW

>From: Jeff Cohen <jeffc at jolt-lang.org> >Date: Tue, 28 Sep 2004 13:05:16 -0700 > >They are part of the Platform SDK from Microsoft, part of Visual Studio. >They correspond to Window system DLLs dbghelp.dll and psapi.dll in Arrrggg, I forget this relation... >\winnt\system32. If you do not have these libs, then you are out of >luck. Mingw should have provided them

>From: Jeff Cohen <jeffc at jolt-lang.org> >Date: Wed, 15 Sep 2004 10:35:36 -0700 > >What's a "compiling mesh?" What I meant, was that there are some implicit defines in mingw (like __GCC) and vcX (like _MVC) but possibly also other unsupported? internal structures. As I stated earlier mingw should be win32 api compliant, but not for complicating matters. But

Hi I've been able to semi compile (i.e. excluded code not present on the platform) the source code of the LLVM tblgen tool on the MinGW platform. However, when linking the object files the linker does not succeed: -------------------------- Linking tblgen debug executable (without symbols) C:/MinGW/msys/local/build/llvm/lib/Debug/libLLVMsystem.a(Signals.o)(.text+0x7e3): In function

----Original Message Follows---- From: Jeff Cohen <jeffc at jolt-lang.org> Reply-To: jeffc at jolt-lang.org, LLVM Developers Mailing List <llvmdev at cs.uiuc.edu> To: LLVM Developers Mailing List <llvmdev at cs.uiuc.edu> Subject: Re: [LLVMdev] VC++: Cannot open include file: 'windows.h': No suchfileor directory Date: Thu, 23 Dec 2004 08:05:39 -0800 >Yes, it

I agree completely with you, Jeff. However, I think it somehow would be nice, if you guys could tell comming users that the win32 solution is geared toward VC++ 7.1 (and hence use of other tools are at their own risk). And, I think it also would be really cool, if you guys come up with a solution how to handle multiple VC++ x solutions/projects from the same source, possibly ranging from VC

It's a possibility, though it would be better to create whole separate trees for different versions of VS. It's not just the project and solutions that need to be kept separate; the object files themselves cannot be mixed between different versions of VS. There's no rush though. Trust me, C/C++ programmers will not rush to adopt Whidbey once it's released. You'd be

Hi Jeff and Morten, I was just wondering if below wisdom is true, why not prefix every solution and project file with VC71 in front of the file name to signal the case that it is only designed for that specific IDE/tool? This gives us room for comming up with other solution and project files for another MS specific IDE/tool independt of each other. Henrik. ----Original Message Follows----

I successfully build llvm from cvs using vs2005 and stlport. I also had a couple of issues, but most were due to outdated project files. I also had to implement code for the alloca instruction. On 3/10/07, Jeff Cohen <jeffc at jolt-lang.org> wrote: > > The recent issues concern the head revision, post 1.9. As no one has > ever submitted patches to fix 2005 problems with the 1.9

Henrik Bach wrote: > ----Original Message Follows---- > From: Jeff Cohen <jeffc at jolt-lang.org> > Reply-To: jeffc at jolt-lang.org, LLVM Developers Mailing List > <llvmdev at cs.uiuc.edu> > To: LLVM Developers Mailing List <llvmdev at cs.uiuc.edu> > Subject: Re: [LLVMdev] VC++: Cannot open include file: 'windows.h': > No suchfileor

----Original Message Follows---- From: Jeff Cohen <jeffc at jolt-lang.org> Reply-To: jeffc at jolt-lang.org, LLVM Developers Mailing List <llvmdev at cs.uiuc.edu> To: LLVM Developers Mailing List <llvmdev at cs.uiuc.edu> Subject: Re: [LLVMdev] VC++: Cannot open include file: 'windows.h': No suchfile or directory Date: Tue, 21 Dec 2004 16:29:47 -0800

Yes, it should find windows.h with the default configuration. But you have to be suspicious of beta code that Microsoft gives out for free. It might just be very buggy, or it might be deliberately crippled. Considering the price tag on Visual Studio, it's one or the other (and probably both). Out of curiosity, did it accept the solution and project files as is, or did it want to

>From: "Henrik Bach" <henrik_bach_llvm at hotmail.com> >Date: Tue, 14 Sep 2004 18:10:29 +0200 > >>From: Jeff Cohen <jeffc at jolt-lang.org> >>Date: Tue, 14 Sep 2004 07:25:11 -0700 >> >>On Tue, 14 Sep 2004 12:46:31 +0200 >>"Henrik Bach" <henrik_bach_llvm at hotmail.com> wrote: >> >> > >From: Jeff Cohen

Hi Jeff, Typically, I've found out that these missing functions are placed beneath lib/System/Unix in some of *.cpp files. These function can be copied to their respectively lib/System/Win32 *.cpp files. Henrik. ----Original Message Follows---- From: Jeff Cohen <jeffc at jolt-lang.org> Reply-To: jeffc at jolt-lang.org, LLVM Developers Mailing List <llvmdev at

Dear R users, I have a response variable in a csv file called "y" and a matrix of predictor variables in a csv file called "mat". I have used the function "nls" I have specified the nonlinear relation between these variable.The code I have witten is called Rprog which begins with the phrase: L.minor.m1<-nls(Y~a ....etc.. The program when I execute the program, I

The recent issues concern the head revision, post 1.9. As no one has ever submitted patches to fix 2005 problems with the 1.9 release, it is safe to say they still exist. Andreas Fredriksson wrote: > On 3/10/07, Jeff Cohen <jeffc at jolt-lang.org> wrote: >> It is, if only because it's the version I use, but 2005 is supposed to >> work also. That being said, I

On Thu, 9 Sep 2004 08:52:10 -0700 Jeff Cohen <jeffc at jolt-lang.org> wrote: > > I haven't got around to this yet but I will. The odds are good the > > problem is in a BSD system header file so I need to capture the > > preprocessed source. > > I guess not... the file 2004-01-01-UnknownInitSize.c does not include > anything else, so there is no preprocessed

>From: Jeff Cohen <jeffc at jolt-lang.org> >Date: Mon, 13 Sep 2004 21:24:47 -0700 > > >But there are some issues with System I'm going to have to take care of >besides using Win32. There appears to be some Unix assumptions like the >presence of /etc or the HOME environment variable. Neither have any >true equivalent in Windows. > Will be fixed in a working

On 3/10/07, Jeff Cohen <jeffc at jolt-lang.org> wrote: > It is, if only because it's the version I use, but 2005 is supposed to > work also. That being said, I wouldn't be surprised to learn that it > doesn't due to recent STL issues. Versions prior to 2003 won't work. I'm using the basic stuff (just libraries, 1.9) with 2005, although we had to fix a few

r257499 On Sun, Jan 10, 2016 at 1:23 PM, Jakob Bornecrantz <wallbraker at gmail.com> wrote: > On Thu, Dec 24, 2015 at 1:28 AM, Jakob Bornecrantz <wallbraker at gmail.com> > wrote: > > On Wed, Dec 23, 2015 at 9:38 PM, Aaron Ballman <aaron at aaronballman.com> > wrote: > >> On Wed, Dec 23, 2015 at 3:28 PM, Reid Kleckner <rnk at google.com> wrote:

On Mon, 30 Aug 2004 20:48:45 -0700 Jeff Cohen <jeffc at jolt-lang.org> wrote: > When I ran configure after updating, I get various errors. First: > > % ../configure --enable-jit --with-llvmgccdir=/home/llvm/cfrontend/x86/llvm-gcc > checking for a BSD-compatible install... /usr/bin/install -c > checking build system type... i386-unknown-freebsd5.2.1 > checking host system