similar to: [LLVMdev] Building the llvm runtime: 'Can't destroy file:Theprocess cannot access the fi

>From: Jeff Cohen Date: Wed, 26 Jan 2005 19:47:44 -0800 > >Fixed. Yes, now it isn't the path. I've recorded this trace: ------------------------- llvm[3]: Building Debug Bytecode Archive libc.bca /bin/rm -f /C/projects/build/MinGW/llvm-4-1/Debug/lib/libc.bca /C/projects/build/MinGW/llvm-4-1/Debug/bin/llvm-ar rcsf /C/projects/build/MinGW/llvm-4-1/Debug/lib/libc.bca

The mapped files weren't being closed at all; they were only being unmapped. It's now fixed. Reid Spencer wrote: >On Thu, 2005-01-27 at 13:16, Henrik Bach wrote: > > >>c:\projects\build\MinGW\llvm-4-1\Debug\bin\llvm-ar.exe: >>c:/projects/build/MinGW/llvm-4-1/Debug/lib/libc.bca-000000: Can't destroy >>file (hb:2): The process cannot access the file

On Thu, 2005-01-27 at 13:16, Henrik Bach wrote: > c:\projects\build\MinGW\llvm-4-1\Debug\bin\llvm-ar.exe: > c:/projects/build/MinGW/llvm-4-1/Debug/lib/libc.bca-000000: Can't destroy > file (hb:2): The process cannot access the file because it is being used by > another process. > make[3]: *** [/C/projects/build/MinGW/llvm-4-1/Debug/lib/libc.bca] Error 2 >

>From: Reid Spencer Date: Wed, 26 Jan 2005 12:23:49 -0800 > >Nope, unless "make" is an alias for "make -j 4" (like I have) make is make for me. > >Could you try using TOOL_VERBOSE=1 with make to get more output ? I've attached an output. Henrik. >Did you try just running the llvm-ar command by itself ? >If not, could you and give it the V (capital

Hi Reid, I don't think I've initiated a parallel build by this command: ------------------------ make TOOLLINKOPTSB+=-ldbghelp TOOLLINKOPTSB+=-lpsapi LDFLAGS+='-Wl,--no-keep-memory' -r VERBOSE=1 ------------------------ Henrik. >From: Reid Spencer Date: Wed, 26 Jan 2005 12:05:51 -0800 > >It looks like what you're getting is a sharing violation. Although, I

Hi Anton, You're already a part of the llvm development team by participating actively on the llvm development list :) If you wish we can put you on: http://llvm.cs.uiuc.edu/Developers.html Great to have you on the team, welcome! We (Jeff, Morten, Paolo, the rest of the team and I) are looking forward to cooperate with you and to push win32 and mingw versions even further to stable and

Hello, Henrik. You wrote Friday, May 13, 2005, 5:52:11 PM: HB> However, me and others will try to help you to compile the cfe. Please HB> submit your compiling errors on this mailing list. I've compiled CFE on cygwin this winter without any problems. I really didn't change anything to let it work. -- With best regards, Anton mailto:asl at math.spbu.ru

Hello, Henrik. You wrote Tuesday, July 12, 2005, 3:49:07 PM: B> Are the MASM backend compatible with the MS version of MASM or other not so HB> license restrictive versions of or similar to MS MASM? Btw, maybe, it will be fine, if this backend will be tested for work with YASM? (http://www.tortall.net/projects/yasm/). It seems, that YASM grows fast during last months. It also supports

Hello, Henrik. You wrote Thursday, May 11, 2006, 5:13:06 AM: HB> Thanks Anton. Nice Job. There was at least one thing I miss in the description: In the step 3 you should unpack runtime libraries from mingw32 distribution into "prefix" (say, w32api and mingw-runtime) before starting configure for GCC. BTW, maybe it will be better just use patched bash (with "pwd" builtin

Hello, all. Just found this file in my e-mail atchive, hope it will be useful for somebody. ===cut=here=== Some small rules: 1) No blankspace in the paths to the top-level directories. 2) Add paths to binaries to your system PATH variable. 3) Use short paths to top-level directories. 1. Some checks & preparations. 1) Be sure, that you're using right make version: $ make

Hello, Jeff. You wrote Saturday, April 29, 2006, 10:45:02 PM: JC> Yes, I know mingw doesn't support dbghelp. I can still rant about it :) ;) Well. Maybe this library will be included in some next versions of mingw's win32api package. Anyway, we can make such library just "on-fly" from the corresponding .dll. JC> This is what's already there. What changed? Maybe

Hello, Oscar. You wrote Sunday, April 23, 2006, 8:31:14 PM: OF> Forward works ok with MinGW. Back slashes can be interpreted as escape OF> sequences by MSYS/Cygwin tools. I've succeeded in building CFE in Mingw at some 1.3-1.4 release. After, I just don't have enough time to play with LLVM. I've sent my instructions to Henrik Bach <henrik_bach_llvm at hotmail.com>, maybe

Hello, Jeff. You wrote Saturday, April 29, 2006, 7:35:46 PM: JC> Bison 1.875 is known to have problems building LLVM. Please upgrade to JC> a newer version (at least 1.875d). The current version is 2.1. Hmm.. I haven't found any problem building LLVM with that bison. ;) The problem, when ld crashed compiling llc is much more serious. It seems to be linker bug. -- With best regards,

Hello, Jeff. You wrote Saturday, April 29, 2006, 10:50:08 PM: JC> You will. You haven't gotten that far yet. It shows up as a crash JC> running gccas. Ok. Switched to 2.1 JC> As for ld crashing, I have no suggestions. It seems to be bug in bfd/cofflink.c file of libbfd. I can even name the function, where weird thing happens. But it's out of my possibilities to debug this

Hello, Aaron. You wrote Sunday, April 30, 2006, 12:01:10 AM: AG> The Cygwin LLVM release (OPTIMIZED_ENABLED) version triggers a bug in LD AG> (BFD binutils) this may well be common to MinGW as well. Seems so, since debug version of llc.exe builds smoothly. Do you have more information about this issue? -- With best regards, Anton mailto:asl at math.spbu.ru

Hello, Aaron. You wrote Sunday, April 30, 2006, 1:34:16 AM: AG> I traced the code its easy enough to find the error message in the bfd code. Hmm. This seems to be another bug. I've just got access to null address in linker and it's crashed. No error message at all. -- With best regards, Anton mailto:asl at math.spbu.ru Sunday, April 30, 2006 1:48:15 AM

Hello, Greg. You wrote Saturday, May 13, 2006, 11:12:26 PM: GP> The problem is that it can't find some symbols: (SymSetOptions, GP> SymInitialize, SymGetModuleBase, SymFunctionTableAccess, etc.) GP> I looked on the Web and these functions are in Dbghelp.lib. GP> Are they also in libimagehlp.a? Yes, they are. At least im mingw-runtime 3.9 (I'm using this version). GP>

Hello, Greg. You wrote Saturday, May 6, 2006, 10:24:16 PM: GP> If anyone has any insight I'd love to hear it. GP> Meanwhile, I'll continue to investigate... Currently I'm working on bootstrapping llvm-gcc4 on mingw32 platform. There are some serious miscompartibilities preventing build. I'll let know the results. Anyway, it's common knowledge, that msys itself have

Hello, Everyone. All blackmagic (playing with pwd, etc) in my build description has gone with patched bash (pwd builtin was just hardly disabled). It's not good, I myself prefer modifying libstdc++ configure script to use PWD_CMD environmental variable as main gcc ones. I'm working on this feature. -- With best regards, Anton mailto:asl at math.spbu.ru

How can a frontend tell LLVM to put a function argument on stack/register/etc? On Thu, Oct 4, 2012 at 5:08 PM, Anton Korobeynikov <asl at math.spbu.ru> wrote: >> Ah, got it. >> Sounds like we might need to introduce CC_X86_Win32_MSVC_ThisCall then?.. > No, we should not. It should be properly expanded in frontend. > > -- > With best regards, Anton Korobeynikov >