search for: requare

...e/wanderer/pkg/build/llvm/src/llvm/include/Support/Casting.h, line 197. I propose add assert assert(Ptr && Ptr->getType()->getTypeID()==llvm::Type::PointerTyID && "Ptr must have pointer type.") in llvm::StroreInst::init and llvm::LoadInst::init functions This is requared including llvm/Type.h or moving init function definitions to iMemory.cpp. I don't known more acceptable variant and then sending as attachment both versions: iMemory.patch1 and iMemory.patch2 . Vladimir -------------- next part -------------- A non-text attachment was scrubbed... Name: iMemo...

...kay? It's either one or the other, for example why is MS Office 2007 rated platinum for? You need native dll's and not wines versions to run it, yet in games that use secu-rom or other copy protections that are not implemented in WINE the highest it can achieve is a gold rating, because it requares a fixed exe both need extra files therefore both should be rated GOLD. It's almost has if the rating system is controlled by favoritism.

...LLVM broken at FreeBSD: In file included from Path.cpp:27: platform/Path.cpp:26: error: no `bool llvm::sys::Path::isvalid() const' member function declared in class `llvm::sys::Path' gmake[1]: *** [/usr/home/wanderer/pkg/build/llvm/night/build/llvm/lib/System/Debug/Path.o] Error 1 and requare patch for llvm/lib/System/FreeBSD/Path.cpp : -Path::isvalid() const { +Path::isValid() const { Vladimir

On Thu, 3 Feb 2005, Vladimir Merzliakov wrote: >> Doing it this way >> allows you to re-use the LLVM build system, as opposed to building your >> own set of Makefiles. > I have pre-LLVM projects in C++ with often used at Unix C++ source file > extention .cc > I modify LLVM build system (original LLVM Makefile.rules already partly > support .cc extention, > for

> Doing it this way > allows you to re-use the LLVM build system, as opposed to building your > own set of Makefiles. I have pre-LLVM projects in C++ with often used at Unix C++ source file extention .cc I modify LLVM build system (original LLVM Makefile.rules already partly support .cc extention, for example, in Sources and FakeSources make vars setup code). Is attached patch

...patch) some >> modification for simplify used common Makefile.rules in LLVM projects and >> non-LLVM project (guarding some LLVM specific parts by ifdef >> LLVM_OBJ_ROOT/LLVM_SRC_ROOT vars). At this moment I am test ability use installed LLVM version to build project instead requare have builded LLVM object dir. And i have problem with installed LLVM include dir. Makefile.rules install only $(PROJ_SRC_ROOT)/include (including *.in files) and ignore headers in $(PROJ_OBJ_ROOT)/include As result installed LLVM does't have all headers for building external projects, for e...

On Mon, 2005-02-14 at 20:53, Chris Lattner wrote: > On Mon, 14 Feb 2005, Reid Spencer wrote: > > > Personally, I don't think LLVM projects should need much in the way of > > autoconf stuff. They certainly don't need to replicate things like > > install-sh and mkinstalldirs. I'd vote for taking these out of the > > projects rather than making the makefiles

On Mon, 14 Feb 2005, Reid Spencer wrote: > Personally, I don't think LLVM projects should need much in the way of > autoconf stuff. They certainly don't need to replicate things like > install-sh and mkinstalldirs. I'd vote for taking these out of the > projects rather than making the makefiles deal with them. I think in > most cases these are just historical artifacts