similar to: breakage? when using --ignore-times with --link-dest

https://bugzilla.samba.org/show_bug.cgi?id=5644 Summary: Option to recheck basis dirs for existing dest files Product: rsync Version: 3.1.0 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy:

I''m attempting to assign ActiveRecord Observers to some of my models, specified in config/environment.rb like so, config.active_record.observers = :presentation_observer, :asset_observer, :tag_observer My models use plugins which extend ActiveRecord::Base, including Sebastian Kanthak''s file_column Attempting to boot mongrel yields:

Been playing around with Samba as a domain controller a lot lately, with a rather nice setup. Latest samba and openldap backend, running on hardware SATA raid 5, with for the moment the only shares on XFS /home partition ontop of LVM running XFS quotas. It's all nice and spangley, expect for one thing.. It completely breaks when saving the roaming profile at logoff, and the quota is reached.

Hi, src/unix/Rscript.c on R trunk stopped building with a compiler error of "unknown not defined/declared" on line 160-ish, where R_SVN_REVISION is , on my system. I see trunk r60972, trunk r60975 changes R_SVN_REVISION to a number - if it can be found, from being a string. The thing is, I track R development with git's svn support (which IMHO works far better). So svn info cannot

The getpwd() function in dash assumed than getcwd(0, 0) will allocate the buffer dynamically using malloc(); however, this glibc extension is not implemented by klibc. Make getpwd() use a temporary buffer and invoke savestr() itself instead of relying on a nonstandard extension. Signed-off-by: Sergey Vlasov <vsu at altlinux.ru> --- Alternatively, you may pull from the following git repo

There are three sets of changes that would benefit stable/7. Namely, there are 1. Improvements for the UFS unmount or rw->ro remount, that perform suspension during the operation. The changes depend on the the suspension mechanism path, that introduced the suspension owner, and added new VFS OP into the mount method table. This might also fix the hangs with gjournal or

Hello, I've sent a similar query before, but didn't receive any answers. When upgrading from 9.1 to 9-STABLE, the buildworld fails with: ===> usr.bin/xinstall (all) cc -O2 -pipe -I/usr/src/usr.bin/xinstall/../../contrib/mtree -I/usr/src/usr.bin/xinstall/../../lib/libnetbsd -I/usr/src/usr.bin/xinstall/../../lib/libmd -std=gnu99 -fstack-protector -Wsystem-headers -Werror -Wall

After installing 6.4-RELEASE on my secondary KDC I decided to test the secondary KDC. When trying kinit I get this error: jcw@w17 ~ $ kinit jcw@STRADAMOTORSPORTS.COM's Password: kinit: krb5_get_init_creds: Key size is incompatible with encryption type One post on the net says that Heimdal changed the key format to add some padding or somesuch. I haven't gone about fixing the problem

hello, klibc/include/signal.h include asm/signal.h which prefixes the __sighandler_t definition with a __user annotation. __user not being defined previously leads to a compilation breakage. It's the only occurrence for now, so the following dirty work-around works here : add a "#define __user" at klibc/include/signal.h head. regards, -- christophe varoqui

Hi, I've already submitted the attached patch to the Debian BTS: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=480994 Basically it fixes the argument parsing when running something like "mount -t ext3,ext2...". If that is fixed, I assume that "-t auto" could also be faked by replacing auto with a long list of fs types (or running "fstype" in the

Got the following trying to build git master: gcc -std=gnu99 -m32 -fno-stack-protector -mregparm=3 -DREGPARM=3 -march=i386 -Os -W -Wall -march=i386 -fomit-frame-pointer -D__COM32__ -nostdinc -iwithprefix include -I../../com32/libutil/include -I../../com32/include -c -o chain.o chain.c ld -m elf_i386 -T ../../com32/lib/com32.ld -o chain.elf chain.o ../../com32/libutil/libutil_com.a

The following function produces a segv when the begin() is taken from vmap, the ScalarMap... bool StaticMemAnalysis::isSingleMalloc(DSGraph* theGraph,DSNode* theNode) { int count = 0; std::map<Value*, DSNodeHandle>& vmap = theGraph->getScalarMap(); for (std::map<Value*, DSNodeHandle>::iterator i = vmap.begin(); i != vmap.end(); ++i) { if(i->second.getNode() ==

> The following function produces a segv when the begin() is taken from > vmap, the ScalarMap... > int count = 0; > std::map<Value*, DSNodeHandle>& vmap = theGraph->getScalarMap(); Are you sure "theGraph" is not null at this point? -Chris > for (std::map<Value*, DSNodeHandle>::iterator i = vmap.begin(); i > != vmap.end(); ++i) { >

On Thu, 28 Nov 2002, Chris Lattner wrote: > > > The following function produces a segv when the begin() is taken from > > vmap, the ScalarMap... > > int count = 0; > > std::map<Value*, DSNodeHandle>& vmap = theGraph->getScalarMap(); > > Are you sure "theGraph" is not null at this point? yes... that call returns sucessfully. the segfault

> > > The following function produces a segv when the begin() is taken from > > > vmap, the ScalarMap... > > > int count = 0; > > > std::map<Value*, DSNodeHandle>& vmap = theGraph->getScalarMap(); > > > > Are you sure "theGraph" is not null at this point? > yes... that call returns sucessfully. the segfault occurs after...

> This is close to a showstopper for integrating an llvm-gcc bootstrap > into the nightly tester. The llvm-gcc ./configure needs to be called > very differently from the llvm ./configure, and keeping two sets of > options is Not Worth The Trouble, at least IMHO. So you didn't like the suggestion of having the configure for llvm-gcc set via an environment variable? That avoids

Hello, Joachim > Hm. For some reason, ld kept searching the wrong (64-bit) library paths > when trying to link the 32-bit results. Hrm. This looks like to be old story about 'lib vs lib32 vs lib64' directories in different distributions. Almost every of them patch gcc inside their packages to provide valid library paths. Look for example, here:

All, The following patch fixes the build breakage on FreeBSD/powerpc: Index: lib/Target/PowerPC/PPCJITInfo.cpp =================================================================== --- lib/Target/PowerPC/PPCJITInfo.cpp (revision 51432) +++ lib/Target/PowerPC/PPCJITInfo.cpp (working copy) @@ -72,7 +72,7 @@ extern "C" void PPC64CompilationCallback(); #if (defined(__POWERPC__) ||

On Wed, Jul 30, 2008 at 03:06:54PM -0700, Julien Lerouge wrote: > On Wed, Jul 30, 2008 at 11:32:18AM -0700, Bill Wendling wrote: > > On Jul 30, 2008, at 11:17 AM, Julien Lerouge wrote: > >> ../../../llvm-gcc4.2-src/gcc/libgcc2.c:2095: error: conflicting types > >> for 'VirtualProtect' > >> > >>

> Rev 54193 seems to cause that failure doing a non bootstrap build on > MingW. > +#ifdef __i386__ > +extern int VirtualProtect (char *, int, int, int *) __attribute__((stdcall)); > +#endif Do we need this stuff at all? afair, I deleted the whole lines in r47684 to sync libgcc2.c with mainline gcc. -- WBR, Anton Korobeynikov