similar to: [ win32utils-Bugs-16211 ] win32-service will not install/build corectly if the system has VC8

On Thu, 24 Aug 2006 srhilber at ncsu.edu wrote: > I've managed to get LLVM 1.8 to build properly with MSVC8 with some > effort. Most of the changes necessary were very minor C++ usage issues; > for instance, VC8 can't deal with prototyping something that's really a > class as 'struct Foo;' or vice versa (it creates issues with matching > function signatures

Hello, I've managed to get LLVM 1.8 to build properly with MSVC8 with some effort. Most of the changes necessary were very minor C++ usage issues; for instance, VC8 can't deal with prototyping something that's really a class as 'struct Foo;' or vice versa (it creates issues with matching function signatures during linking.) Additionally, I had to do quite a few updates to the

Hi all! Does anyone successfully use the VC8/VS2005 command line tools (cl.exe and link.exe) with wine yet? I'm trying to setup VC8 in our cross compiling environment (which already works perfectly with VC7), but have some problems here. After some tries, I can now run cl.exe with wine to compile our sources (although some command line parameters cause the program to crash, but that's not

Hello Guys, I''m trying to get this working: t = Thread.new { while true puts "printing a line" sleep 2 end } gets t.exit puts "exiting" As you see, the idea is get multiple "printing a line" until a hit enter. The thing is this is a known problem for 1.8 on win32. I tried both mingw, VC6 and VC8 with the same results. Saw a post

https://bugzilla.mindrot.org/show_bug.cgi?id=1742 Sorin Sbarnea <sorin.sbarnea at gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sorin.sbarnea at gmail.com -- You are receiving this mail because: You are watching someone on the CC list

Ah, interesting, have not ran across that before (as I always strive to never use the same name as any scope previously), but rather interesting that GCC gets it wrong while VC++ gets it right, kind of a switch. And yes, that switch I mentioned is for VC6 style in VC7.1 (what I use), you have to switch it to make it conformant, nice to hear VC8 does it correctly by default now. On Thu, Oct 2,

>From: Paolo Invernizzi <arathorn at fastwebnet.it> >Date: Thu, 16 Sep 2004 11:18:00 +0200 >If VC6 is not doing something wrong with templates... ;-/ As far as I know is template handling a part of some C++ ISO standard. Then, MS should adhere to this... However, what you objects against is that MS didn't implement STL the way STL should be implemented. And the reason to

Hello, We found a problem that we are not sure who is responsible. Here is what we found: On some small file (around 1 sec) if we ask to compress the file at 128kb/s On an encoder compiled with Microsoft visual 7.1 it generate a file at 160kb/s (that is the behaviour we expect because of the short length of the file) On same encoder compiled with Microsoft visual 8.0 with the same parameter it

I was going through documentation and source lately, and I decided how to make llvm bytecode more compatible to C++: 1) thiscall sould be introduced, which would take N arguments and the first argument would always be the C++ "this" argument. This would abstract llvm compiler dependant C++ code emittion. 2) the ret instruction should be able to return structs (as Chris has already

On Tue, 21 Nov 2006, [ISO-8859-2] Žiga Osolin wrote: > I was going through documentation and source lately, and I decided how to > make llvm bytecode more compatible to C++: > 1) thiscall sould be introduced, which would take N arguments and the > first argument would always be the C++ "this" argument. This would > abstract llvm compiler dependant C++ code emittion. Sure.

I was going through documentation and source lately, and I decided how to make llvm bytecode more compatible to C++: 1) thiscall sould be introduced, which would take N arguments and the first argument would always be the C++ "this" argument. This would abstract llvm compiler dependant C++ code emition. 2) the ret instruction should be able to return structs (as Chris has already

I''m pretty new to Rails and now, in order to fully learn RoR, I''m trying to replicate a project developed in Java using Hibernate+Tapestry. Tapestry is based on components and you can really use objects mappings in views like: Example from the contact edit (view). <input jwcid="@TextField" value="ognl:contact.name" /> <input

Chris Lattner pravi: > On Tue, 21 Nov 2006, [ISO-8859-2] Žiga Osolin wrote: >> I was going through documentation and source lately, and I decided >> how to >> make llvm bytecode more compatible to C++: >> 1) thiscall sould be introduced, which would take N arguments and the >> first argument would always be the C++ "this" argument. This would >>

Hey Daniel, I''m trying to leave you a comment on this article you wrote: http://djberg96.livejournal.com/168403.html But since you disabled OpenID and anonyous, I''m not fond to register for another account just to reply your comments. Quoting your post: "" Unfortunately, I''ve slammed into the cold hard fact that FFI just isn''t the grand solution

Hi, Have you tried the new VC8 Beta? It's been out for less than 2 weeks: http://lab.msdn.microsoft.com/express/visualc/default.aspx It's supposed to have improved standards compliance. Regards, -Eugene Talagrand On Thu, 8 Jul 2004, Chris Lattner wrote: > Date: Thu, 08 Jul 2004 01:56:03 -0500 (CDT) > From: Chris Lattner <sabre at nondot.org> > Reply-To: llvmdev at

I am using Ubuntu 8.10 and Wine 1.1.8 and installed VC6 from a folder VC6 copied from the installation CD. I clicked the setup.exe file in the VC6 folder and the first page of the VC6 installation wizard showed, but when I clicked 'Next' the install failed with message: "ken at ken-desktop:~/Desktop/VC6$ wine setup.exe wine: Unhandled page fault on read access to 0x00000000 at

The current VC6 project file is set to use the single-threaded C library in Windows. This causes crashed when it hits the (temporary) fprintf's in the library. Since using multithreaded libraries in a single threaded program does no harm and will do away with these crashes in multithreaded programs, I suggest that the VC6 file should be changed to use the multi-threaded libs. I'm not a

Hi Kovacs, >subj. I can compile the library on vc6, but it seems that it doesn't >export anything. Has somebody similar experience? I've built it using VC6, though I didn't use the project files in the vorbis_vc6 subdirectory, so I can't comment on them. You should be building the library as a static library, and not a DLL -- if you want to build the library as a DLL,

On Fri, Oct 10, 2008 at 2:11 PM, Tanya M. Lattner <tonic at nondot.org> wrote: > > LLVMers, > > The 2.4 pre-release is available for testing: > http://llvm.org/prereleases/2.4/ > > If you have time, I'd appreciate anyone who can help test the release. > Please do the following: > > 1) Download/compile llvm source, and either compile llvm-gcc source or use

On Sep 15, 2004, at 8:40 AM, Henrik Bach wrote: > Hi, > > Has some one committed these patches into CVS? Not yet... checked 10 minutes ago... I'm attaching the cvs diff -u version of them (I've read Reid Spencer post about it) > Paolo, thanks for the patches. In the near future I'll try to compile > them. > > I've installed STLport 6.4.2 with vc6. May I