search for: mkpatches

The document: http://llvm.org/docs/DeveloperPolicy.html refers to using utils/mkpatch. However when using mkpatch it complains about directories no longer under version control. Specifically directories lib/Debugger and win32 in mkpatch's source line: svn diff -x -u >> "$NAME".patch.raw 2>&1 \ autoconf docs utils include lib/System lib/Support lib/VMCore

I've included a patch which does not remove mkpatch but does remove diff search directories which caused a failure because those directories were no longer in svn. I was uncomfortable removing mkpatch since I believe it helps document creating patches for beginners who do not use separate source and build (object) root directories. Its existence is also expected by readers of:

Hello, I hope that this is an appropriate for this list - please educate me if not. Having cloned the unstable repository and attempted to run "make mkpatches" I found that it failed because it couldn''t download linux.2.6.16-rc4.tar.bz2 from kernel.org. This is because it''s looking for it in /pub/linux/kernel/v2.6 when in fact it is to be found in /pub/linux/kernel/v2.6/testing/. I resolved this by editing [my hg repo]/buildconf...

Hello, The 0.9.9 2.4.10pre4 patch doesn't apply. There are 5 rejects. The first three are easy to fix, but the fourth in vmscan.c will be very difficult without being a developer. The fifth I am not sure about. This brings up the fact that many of us are using ext3 and have to patch every time a new kernel comes out. I really think we need to strong arm Linus or something and get

Here's the version of the unit test patch, incorporating the feedback I have received so far. Some notes on the patch: - This patch doesn't include googletest itself, that will need to be checked in separately. The source distribution will live in llvm/utils/unittest/googletest. (The reason for the extra directory level is so that the LLVM-specific makefiles can live in

2008/12/30 Talin <viridia at gmail.com> > Here's the version of the unit test patch, incorporating the feedback I > have received so far. > Looks good, a few comments below. > Some notes on the patch: > > - This patch doesn't include googletest itself, that will need to be > checked in separately. The source distribution will live in >

Hi Tanya, On Sun, 2007-07-01 at 19:38 -0700, Tanya M. Lattner wrote: > > The current SVN repository has several modules at the top level (llvm, > > test-suite, java, stacker, etc.). The modules contain the software that > > makes up the LLVM Project. However, there is nothing at the top level > > that explains any of this. So, I am considering doing the following at >

Hi all, A few things. Firstly, I've got a working implementation of the X86ThisCall calling convention, but I'm unsure how to go about submitting it. (I'm not really sure how to go about creating patch files etc, but would like to contribute to the project). Also, I'm using MS Visual C++ Express, and there are a few things that stop llvm1.9 (and the current CVS release) from

+++ unittests/TestMain.cpp (revision 0) +//===--- unittest.cpp - unittest driver -----------------------------------===// +++ unittests/ADT/DenseMapTest.cpp (revision 0) +//===- llvm/unittest/DenseMapMap.h - DenseMap unit tests --------*- C++ -*-===// You probably want to update these file headers to match their real names. 2008/12/30 Misha Brukman <brukman at gmail.com> >

Directly including ../tools breaks building in separate object tree, as well as building from mkpatch patch (I believe Rik hit that one). This puts xenstore headers in linux-public. Signed-off-by: Chris Wright <chrisw@osdl.org> --- a/linux-2.6-xen-sparse/drivers/xen/xenbus/Makefile Mon Aug 8 18:43:57 2005 +++ b/linux-2.6-xen-sparse/drivers/xen/xenbus/Makefile Mon Aug 8 15:15:06 2005 @@

Hi All; I can''t find any related discussion on list archives so i just want to learn could anybody tell me is there any specific reason not to upgrade xen-3.0.4-testing tree to for example 2.6.16.38 which fixes dozens of security related problems after .33, i know as a distro packager its my responsibility to sync/modify whatever is needed but as an end-user perspective i just want

Not sure if this is a pkg-xen issue or for the debian kernel people, trying here first since the patch I applied is created from the pkg-xen project % apt-get source xen-3.0 % cd xen-3.0-3.0.2+hg9646/ % make mkpatches % cd /usr/src/linux-source-2.6.16 % patch -p1 < ../linux-2.6-xen.patch % cp ../config-2.6.16-1-amd64-k8 .config % make-kpkg --append-to-version -1-xen-3.2.0-d0 binary /usr/bin/make EXTRAVERSION=-1-xen-3.2.0-d0 ARCH=x86_64 \ bzImage <snip> CC [M] net/ipv4/netfilter...

OK changes made and new patch attached. Comments below: On Tue, Dec 30, 2008 at 2:40 PM, Misha Brukman <brukman at gmail.com> wrote: > +++ unittests/TestMain.cpp (revision 0) > +//===--- unittest.cpp - unittest driver > -----------------------------------===// > > +++ unittests/ADT/DenseMapTest.cpp (revision 0) > +//===- llvm/unittest/DenseMapMap.h - DenseMap unit

On Thu, 2007-07-19 at 21:03 -0700, Chris Lattner wrote: > On Thu, 19 Jul 2007, Reid Spencer wrote: > > With the pending reorganization of the software, I have some questions > > about how developers set their PATH and LD_LIBRARY_PATH variables when > > working with LLVM. This is a bit long winded, but bear with me. > > ok :) > > > We're planning to break

Hi All, I have created a minimally functional Win32 COFF Exporter using the new MC framework. I made some minor changes to other libraries to allow me to plug it in without building it as part of the LLVM project. I wanted to share it but wasn't sure how to go about doing so, so I have attached the code to this message. Any feedback on would be appreciated. -------------- next part

Hi all, as proposed in http://lists.cs.uiuc.edu/pipermail/llvmdev/2009-February/020396.html I implemented the algorithm presented in [Ball94]. It only instruments the minimal number of edges necessary for edge profiling. The main changes introduced by this patch are: *) a interface compatible rewrite of ProfileInfo *) a cleanup of ProfileInfoLoader (some functionality in ProfileInfoLoader

I've just been trying to catch up with the posts already so figured I'd just start another thread as it seemed I would address things from multiple emails. I really need to get my sieve filter script updated to move the list emails into the proper folder now I guess :) We can play with the revision of the packaging during testing. One idea would be to use 3.0.1-0.YYYYMMDD for

> The current SVN repository has several modules at the top level (llvm, > test-suite, java, stacker, etc.). The modules contain the software that > makes up the LLVM Project. However, there is nothing at the top level > that explains any of this. So, I am considering doing the following at > the top level of the repository (i.e. in > http://llvm.org/svn/llvm-project): > >

On Thu, 19 Jul 2007, Reid Spencer wrote: > With the pending reorganization of the software, I have some questions > about how developers set their PATH and LD_LIBRARY_PATH variables when > working with LLVM. This is a bit long winded, but bear with me. ok :) > We're planning to break the "llvm" module up into three modules: > > * support - lib/Support,

All, The current SVN repository has several modules at the top level (llvm, test-suite, java, stacker, etc.). The modules contain the software that makes up the LLVM Project. However, there is nothing at the top level that explains any of this. So, I am considering doing the following at the top level of the repository (i.e. in http://llvm.org/svn/llvm-project): 1. /README.html Just a short