similar to: What does SPEEX_SET_COMPLEXITY do?

Hi Reid, Looking closer at the build process, I find that Path.cpp doesn't get compiled, even if it is a newer version than its *.o file. That's probaly the reason the error still exists. I've zipped and attached the trace after the point the new Path.cpp was updated by cvs. It clearly shows that it newer gets compiled and now shows that it is the dependencies in the makefile

This is one of the reasons I'm getting rid of the "platform" link. I'm not sure what platform you're working on, but on Cygwin it causes problems. Cygwin doesn't like .. through a soft link and generates incorrect file names. I imagine this is what is happening to the dependencies. In any event, the "platform" link will be gone before the new year. Sorry for

Henrik. ============================================================= Henrik Bach Open Source Developer e-mail: henrik_bach_llvm at hotmail.com ============================================================= Got Freedom? Software Freedom Day 2004 - 28th of August http://www.softwarefreedomday.org/ =============================================================

Hi Reid, Looking closer at the build process, I find that Path.cpp doesn't get compiled, even if it is a newer version than its *.o file. That's probaly the reason the error still exists. I've zipped and attached the trace after the point the new Path.cpp was updated by cvs. It clearly shows that it newer gets compiled and now shows that it is the dependencies in the makefile

I have no problems... Henrik Bach wrote: > Henrik. > > ============================================================= > Henrik Bach > Open Source Developer > > e-mail: henrik_bach_llvm at hotmail.com > ============================================================= > Got Freedom? > Software Freedom Day 2004 - 28th of August > http://www.softwarefreedomday.org/ >

Hi Reid, The error still exists. However, looking on the function in Win32/Path.cpp: -------------- void sys::CopyFile(const sys::Path &Dest, const sys::Path &Src) { if (!::CopyFile(Src.c_str(), Dest.c_str(), false)) ThrowError("Can't copy '" + Src.toString() + "' to '" + Dest.toString() + "'"); } -------------- I

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

No, although its declared in the Path.h file, its actually not in the Path class. Have a look. Not sure why you're still seeing that problem. The same change to Unix/Path.cpp fixed the same problem on Cygwin and Linux. Reid. On Thu, 2004-12-23 at 15:48, Henrik Bach wrote: > Hi Reid, > > The error still exists. However, looking on the function in Win32/Path.cpp: > --------------

It looks like what you're getting is a sharing violation. Although, I don't understand why. The llvm-ar.exe when its building an archive file always builds it in a temporary. Only when that is complete does it remove the old one and rename the temporary. Perhaps this is a result of doing parallel build and the "lib3.tmp" file (that name looks wrong to me) is being accessed by

But breaks VC++. The problem is, Windows.h defines "CopyFile" as a macro that's either "CopyFileA" or "CopyFileW". Path.h is included before Windows.h, so the declaration has the name "CopyFile" while the definition has "CopyFileA". Instant compilation error. Not sure what the best way to fix it is, but I'll check it in as soon as I

Hi Jeff and others, When building the llvm runtime, I always get this error message: 'Can't destroy file: The process cannot access the file because it is being used by another process.' The file is destoyed anyway. I think that the the real error is the path for the file (*/\file.tmp). However, I can't find the bug in the source. Do you have any clue?:

Hi, When I compile FileUtilities.cpp I get this error: ---------------- llvm[1]: Compiling FileUtilities.cpp for Debug build c:/projects/src/llvm-1/llvm/lib/Support/FileUtilities.cpp: In destructor `llvm::FDHandle::~FDHandle()': c:/projects/src/llvm-1/llvm/lib/Support/FileUtilities.cpp:79: error: `close' undeclared (first use this function) ---------------- Shouldn't function close

Hi Jeff, It seems that the above project isn't committed into cvs. Henrik. ============================================================= Henrik Bach Open Source Developer e-mail: henrik_bach_llvm at hotmail.com ============================================================= Got Freedom? Software Freedom Day 2004 - 28th of August http://www.softwarefreedomday.org/

Hi, Is there an easy way to test whether an llvm-tool is functioning properly? Henrik. ============================================================= Henrik Bach LLVM Open Source Developer e-mail: henrik_bach_llvm at hotmail.com ============================================================= No Software patents - Thank you Poland: http://www.nosoftwarepatents.com/en/m/intro/app0411.html Got

Hi, Can anyone tell me why CopyFile is the only undefined reference from Path.cpp? --------------- llvm[2]: Linking Debug executable gccld c:/projects/build/MinGW/llvm-1-1/tools/gccld/Debug/gccld.o(.text+0x439): In function `Z15EmitShellScriptPPc': c:/projects/src/llvm-1/llvm/tools/gccld/gccld.cpp:127: undefined reference to `llvm::sys::CopyFile(llvm::sys::Path const&, llvm::sys::Path

============================================================= Henrik Bach LLVM Open Source Developer e-mail: henrik_bach_llvm at hotmail.com ============================================================= 'Nothing is impossible; The impossible just takes longer time :)' - Inventor of a new energy saver light bulp from Denmark. No software patents! Got Freedom? Software Freedom Day - 10th

Replace __time_t with time_t in my question. I've compiled function: std::string TimeValue::toString() const { // Alas, asctime is not re-entrant on Windows... //hb: __time64_t ourTime = this->toEpochTime(); time_t ourTime = this->toEpochTime(); //hb: char* buffer = ::asctime(::_localtime64(&ourTime)); char* buffer = ::asctime(::localtime(&ourTime)); std::string

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

Hi, Now, I've build the tools and the cfe. However, 'make check' gave me the attached results. Summarized as follows: # of expected passes 1081 # of unexpected failures 26 # of expected failures 32 I configured llvm with following options: '--prefix=/home/hb/llvm/ --enable-targets=host-only'. I used gcc version 3.4.2 to build the tools and cfe. The cfe is version:

And I had just fixed VC++ so that it *did* handle the dependencies with platform correctly... This means that each file in System you change to eliminate the #include from platform will require a corresponding change to System.vproj. I'd appreciate it if you got it over with all at once, otherwise VC++ support will be broken more often than not. Reid Spencer wrote: >This is one of