similar to: R CMD build with mingw and msys (PR#9766)

The following is a patch (svn diff) for the R CMD build script that calculates exclude patterns after the tar/untar step rather than before. The perl find() function, used in the calculation of the exclude patterns, ignores symlinks, which meant that directory symlinks were not considered for exclusion. Since the tar/untar step resolves (copies) symlinks, this works around that limitation.

Full_Name: Byron Ellis Version: R 1.9.0 (and 2.0.0) OS: Linux (Redhat Fedora Core) Submission from: (NULL) (140.247.241.197) It appears that `R CMD build` cannot handle spaces in the path when building packages for distribution. For instance: [ellis@net-78815 ~/Bayesian Networks]$ R CMD build bnsl * checking for file 'bnsl/DESCRIPTION' ... OK * preparing 'bnsl': * cleaning src *

R developers, I've been happily building packages, under windows, for some time now and upgraded to R 2.1.0 and now when I attempt to build a package, I get the following errors... C:\conifers>rcmd build Rconifers * checking for file 'Rconifers/DESCRIPTION' ... OK * preparing 'Rconifers': * checking DESCRIPTION meta-information ... OK * cleaning src * checking whether

Hi, Gordon Smyth brought the following problem to my attention. PROBLEM/"BUG": Using R v1.9.0 alpha for Windows and the latest Rtools from Brian Ripley you get the following problem trying to R CMD build a package (or a bundle); >R CMD build R.basic * checking for file 'R.basic/DESCRIPTION' ... OK * preparing 'R.basic': * checking whether 'INDEX' is

Hi, I use rsync 3.0.2 for daily incremental backups: rsync -aAzHRxby -f '. -' --numeric-ids --delete-during --delete-excluded \ --suffix='' --backup-dir=$BACKUP_ROOT/$BACKUP_HOST/${TODAY} \ ${DESTINATION}$BACKUP_ROOT/$BACKUP_HOST/current <<< $EXCLUDE_PATTERNS Sometimes I add a new item to $EXCLUDE_PATTERNS but then the excluded files are backed up in

Under Linux the cleanup script (if it exists) is run at the end, before the package archive is created, and this prevents intermediate files that are no longer needed from being written to the archive. Unfortunately, this does not happen under Windows when there is a cleanup.win. That is, cleanup.win is not run before the archive is created. Here is the code in build.pl that checks for cleanup

as part of building python2.5.2 under msys under wine on linux using mingw, i thought i'd try building _msi.pyd just for kicks. of course, that required having an msi.lib import library, and associated header files. so, purely as an experiment, i've documented the process by which it is possible to take wine 1.1.13 (current development release) source code, modify the header files for

folks, hi, this is a fairly important issue for python development interoperability - martin mentioned that releases of mingw-compiled python, if done with a non-interoperable version of msvcrt, would cause much mayhem. well, compiling python on mingw with msvcr80 _can_ be done; using it can also be a simple matter of creating a python.exe.manifest file, but i can't actually do any testing

hi folks, i promised i'd get python built under wine - and i'm happy to report that this goal has been successfully achieved. http://bugs.python.org/issue4954 if anyone's interested. what has been achieved is that a python.exe, libpython2.5.dll, an implib libpython2.5.dll.a and a python2.5.def have all been successfully created using an entirely free software toolchain, along with the

Óscar Fuentes wrote: > Kenneth Boyd <zaimoni at zaimoni.com> writes: > > [snip] > >> My internal priority for that CMake patch is low, as I need only minimal >> patching to use the autoconf-generated configure script to build LLVM. >> Right now it's just llvm.config.in.in that needs patching (the failsafed >> GenLibDeps.pl script went in

Óscar Fuentes wrote: > Kenneth Boyd <zaimoni at zaimoni.com> writes: > >> * I am seeing desynchronization between the configure-generated >> Makefiles and the CMakeFile.txt files. [e.g., llc; makefile doesn't >> have asmprinter, CMakeFile.txt does]. That much I should be able to >> construct a patch for "blind", if no-one gets to it first.

Óscar Fuentes wrote: > The CMake devteam is very responsive about bug reports. They will > certainly appreciate your bug report, no patch required. > I still don't think I have enough detail to file a bug report (not sure exactly what they need to know about my system configuration to make it testable). I did go ahead (just now) and ask the main CMake mailing list which files I

Hello, Bob > download the latest from the head of the trunk, then ran 'configure' under > msys and received the following....  has anyone done this under msys on a > windows pc?? Msys works fine for me. What is the version of msys you're using? What is the version of bash? -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State

Hello, Bob > i running msys 1.0 it appears; the bash sh is 2.04.0(1) Hrm... This seems to be pretty ancient and buggy. :) Consider reading http://blogs.tedneward.com/2008/02/24/Building+LLVM+On+Windows+Using+MinGW32.aspx it can provide necessary sources of different tools requires. Some versions noted there might be already out-of-date, but otherwise the text looks good. -- With best

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> <font size="-1"><font face="Verdana">hi anton,<br> <br> i upgrade my

-- 此致 礼 罗勇刚 Yours sincerely, Yonggang Luo -------------- next part -------------- A non-text attachment was scrubbed... Name: llvm.patch Type: application/octet-stream Size: 14374 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20090805/4328d661/attachment.obj>

I had Strawberry Perl, which was the problem. I installed the Perl from the MSYS distribution and it now works. I've enclosed a patch for the Getting Started page. Thanks for pointing me in the right direction. -John >On Wed, Aug 5, 2009 at 5:36 PM, Kenneth Boyd <zaimoni at zaimoni.com> wrote: > John Thompson wrote: > > Hi, > > > > I'm trying to build

Thank you > 2. As for error - try to disable threads during llvm/llvm-gcc builds. This resolved the build errors for llvm-gcc, however the llvm-gcc.exe, llvm-g++.exe, llvm-gcov.exe were not built only the llc.exe, llvm-as.exe ... tools from the llvm build bin directory are in the llvm-gcc install bin directory. > 1. Why do you need build llvm-gcc by yourself? I would like to write an

Thank you > 2. As for error - try to disable threads during llvm/llvm-gcc builds. This resolved the build errors for llvm-gcc, however the llvm-gcc.exe, llvm-g++.exe, llvm-gcov.exe were not built only the llc.exe, llvm-as.exe ... tools from the llvm build bin directory are in the llvm-gcc install bin directory. > 1. Why do you need build llvm-gcc by yourself? I would like to write an

Hello, Charles >> 2. As for error - try to disable threads during llvm/llvm-gcc builds. > > This resolved the build errors for llvm-gcc, however the llvm-gcc.exe, > llvm-g++.exe, llvm-gcov.exe were not built only the llc.exe, llvm-as.exe ... > tools  from the llvm build bin directory are in the llvm-gcc install bin > directory. Then something is completely broken on your side