similar to: [LLVMdev] Bugs in Getting Started Guide

> (*) The �Getting Started Quickly� section describes commands using gunzip; > the binaries are distributed using bzip2 instead. > > (*) The directory structure after step 4 doesn�t have a �llvm-3.4� or > �platform� directory; no such command �fixheaders� can be found. These two sections have been fixed. Thanks! > (*) The docs aren�t clear as to which �source code� is needed

(*) The “Getting Started Quickly” section describes commands using gunzip; the binaries are distributed using bzip2 instead. (*) The directory structure after step 4 doesn’t have a “llvm-3.4” or “platform” directory; no such command ‘fixheaders’ can be found. (*) The docs aren’t clear as to which “source code” is needed for step 5: the LLVM source code, or one of the GCC front-end source

Hello, Everyone. Now I have some spare time and I've decided to build LLVM on Mingw. I've grab the latest 1.7 release (not CVS snapshot). Here are some issues fixed during the build. Now I'm preparing gcc build. So, I think, there will some other "parts" 1. Prerequisites 1.1 GCC 3.4.5 from mingw.org site. $ gcc --version gcc.exe (GCC) 3.4.5 (mingw special) Copyright (C)

Hello, Everyone. This is just brief description on building llvm-gcc4 with mingw32. It's definitely non error-free and contains many "hacks", which should be eliminated in the future. 1. Prerequisites We're building in the folowing configuration: 1.1 GCC 3.4.5: gcc -v Reading specs from f:/research/mingw/bin/../lib/gcc/mingw32/3.4.5/specs Configured with:

I have found an unwanted feature of rsync 2.5.5. It has to do with soft links and the --delete option in archive mode. The following shows how to reproduce the error. Provide a soft link that refers to a parent directory. %> /bin/ls -lR /tmp/src /tmp/src: total 16 16 drwxrwxr-x 2 wke sys_admin 239 Sep 17 16:18 dir1/ /tmp/src/dir1: total 32 16 lrwxrwxrwx 1 wke

Hello, I'm totally new to this list, so I hope I don't break all the rules. :) I've looked through the archives (and google), and I really can't find the answer to my question. I'm trying out the 'detect-renamed'-patch, and I've encountered some odd behavior. I've applied the patch to both rsync-2.6.9 and rsync-3.0.0pre7, and it's the same behavior.

Hello, I would like to have a full repository, say, holding files full/a.txt (version 1) full/b.txt (version 1) full/c.txt (version 1) and a repository of updates, for example new/b.txt (version 2 - newer) Then, I would like to call rsync [flags] new/ full/ destination to get destination/a.txt (v.1) destination/b.txt (v.2) destination/c.txt (v.1) This simple case works

When I do rsync -av --backup --backup-dir=/dir1/dir2/Backup \ /dir1/dir2/dir3 machine:/dir1/dir2/dir3 I get /dir1/dir2/Backup/dir3/... /Backup/dir3/dir4/... i.e. the tree under 'dir3' (my source tree) gets created under .../Backup. This is fine. But when I do the same thing with a single file like rsync -av --backup --backup-dir=/dir1/dir2/Backup \ /dir1/dir2/file

On 24 Nov 2003, Dirk Pape <pape@inf.fu-berlin.de> wrote: > Dear Martin Pool, > > I tried to ask via the rsync-mailing list but never got an answer. So I > contact you directly. > > I refer to the rsync syntax > > rsync [OPTION]... SRC [SRC]... DEST > > with more than one SRC, which is mentioned in the man-pages. > We use this form to "overlay"

I have noticed that the contents of per-directory .cvsignore files apply outside their subtrees when using --cvs-exclude in rsync 2.6.0. In the results below, notice how dir1/.cvsignore is applying to a file in dir2. There is no ~/.cvsignore, and the CVSIGNORE variable is unset. % ls -AFR .: dir1/ dir2/ ./dir1: .cvsignore file1 ./dir2: file2.foo % cat dir1/.cvsignore *.foo % /usr/bin/rsync

Hi, I'm running rsync-3.0.4 on my UNIX system. I've just updated from rsync-2.6.9. I'm facing a general problem with the execution of files during a transfer process. The situation: 2 Directories (dir1 and dir2) on one machine with a some files in dir1 which shall be translated to dir2. rsync does not correctly recognize dir1 and dir2 as directories. It tries to transfer dir1 as a

Hi, I'm using the following command to move files from a to b: rsync -avvvv --remove-source-files --ignore-existing /path/to/dir1/ /path/to/dir2 >> logfile dir2 isn't empty so I only move files from dir1 to dir2 that don't exist already. Every so often rsync stops in the middle and doesn't continue with the result that I have to kill it. The last time it happened, rsync had

My systems: rh61, 2.2.14 + smbfs-nls.patch. I refer to 2.0.7pre3 as 2.0.7 === 1) "ls" of an empty dir 1a) 1.9.18 doing "ls" to an empty samba dir: smb: \> ls 49550 blocks of size 16384. 33754 blocks available 1b) 2.0.7 doing "ls" to an empty samba dir: smb: \> ls ERRDOS - ERRbadfile (File not found.) listing \* <=======

Hi all!! I'm experimenting a set of problems when trying to connect Samba client to windows. I don't have admin rights on the windows side, so I should trust all my winSA admin is telling me. Windows side (server): In the server Side (win2k3), the SA defined a shared resource. The share-permissions tab the "domain users" group has typical permissions, and in the security

Guys, I'm bumping into some stupid problem, really need some fresh ideas. Samba version samba-client-2.2.7-3.7.2 samba-2.2.7-3.7.2 samba-swat-2.2.7-3.7.2 samba-common-2.2.7-3.7.2 The goal is to upload all *.gz files only from dir* dirs. I do mask *.gz recurse mput dir* See the detailed output below But mput keeps grabbing non *.gz files ignoring the mask *.gz command. Am I doing

Guys, I really need some help. Samba version samba-client-2.2.7-3.7.2 samba-2.2.7-3.7.2 samba-swat-2.2.7-3.7.2 samba-common-2.2.7-3.7.2 I'm trying to upload all *.gz files only from dir* dirs. I do mask *.gz recurse mput dir* See the detailed output below But mput keeps grabbing non *.gz files IGNORING the mask *.gz command. Am I doing something stupid here? Thanks, Ruslan. [root at

Hi List, hope this is not too offtopic, but this bothers me and my backup. My backups are tar jobs in cron, eg: 20 23 * * * tar -zcf /mnt/backupInternalHosts/backup/backup.tar.gz /etc /root /home && touch /tmp/state_backup-backup This always sends me an unwanted email with: tar: Removing leading `/' from member names I consider this a bug because this informal message is

Hello All, I have an off topic question about rsync and was wondering if i can get some kind person help with it. I have two servers with each server have three same directories on them /dir1/ /dir2/ /dir3/ . How would i achieve this by using rsync? I have tried rsync -avrt --delete server_ip:/dir1/ /dir2/ /dir3/ /dir1/ /dir2/ /dir3/ this does not do anything except give errors. Someone on IRC

Hi mabi, Some questions: -Did you by any chance change the cluster.quorum-type option from the default values? -Is filename.shareKey supposed to be any empty file? Looks like the file was fallocated with the keep-size option but never written to. (On the 2 data bricks, stat output shows Size =0, but non zero Blocks and yet a 'regular empty file'). -Do you have some sort of a

Hello, > > (*) I understand it uses the MinGW toolchain—does LLVM thus need to be > > installed in the same directory structure as MinGW? No, it shouldn't. It can be configured and built in any directory. > > I guess, in general, I’m just looking for a simple “this is how to get > > LLVM going on a Win32 box”, and I’m not finding it. Well, there is nothing special of