similar to: [LLVMdev] ../llvm/configure fails in Cygwin with space character in path name?

I don't think autoconf build scripts would be tolerant of whitespace pathname. To build tools and liibs, I recommend you should build them on desired tree. Anyway, I think it might be a little problematic if built tools did not accept whitespace pathnames. Then, please file a bug. ...Takumi

Why shouldn't they accept paths with spaces in them? *nix supports that, generally. So long as the paths are properly escaped in any input, things should work. If they don't, it's a bug. On Sep 21, 2011, at 3:51 AM, NAKAMURA Takumi wrote: > I don't think autoconf build scripts would be tolerant of whitespace pathname. > To build tools and liibs, I recommend you should build

Hi,     I just downloaded Xen4.0 from:     http://www.xen.org/products/xen_source.html     Trying=0A to build:     Create xen entries under /sys/hypervisor =0A(XEN_SYS_HYPERVISOR) [Y/n/?] y     #     # configuration written to =0A.config     #     make-3.79.1-p7[3]: Leaving directory =0A`/foo/xen40/xen-4.0.0/linux-2.6-pvo=     ps.git''     make-3.79.1-p7 -C

libFLAC have three SSE-accelerated functions FLAC__lpc_compute_autocorrelation_asm_ia32_sse_lag_N (N = 4, 8, 12). They require lpc_order less than N. The best compression preset (flac -8) uses lpc_order up to 12; it means that during encoding FLAC also uses unaccelerated C function. I'm not very familiar with asm so I took FLAC__lpc_compute_autocorrelation_asm_ia32_sse_lag_12, changed it and

So here is quick patch solving the problem, now it should be PIC. -- Miroslav Lichvar lichvarm@phoenix.inf.upol.cz -------------- next part -------------- --- lpc_asm.nasm.orig Wed Jul 18 02:23:40 2001 +++ lpc_asm.nasm Sat Nov 17 21:09:46 2001 @@ -59,10 +59,10 @@ ; ALIGN 16 cident FLAC__lpc_compute_autocorrelation_asm_ia32 - ;[esp + 24] == autoc[] - ;[esp + 20] == lag - ;[esp + 16] ==

Dear developers, I am trying to run some C/ Fortran code in R. Although I have experience with that in Windows (Vista) 32 bit, I could not succeed in 64 bit. I downloaded the following: - R 2.12.0 - Rtools 212 - miktex 2.9 - inno setup 5 -Afterwards, I changed the path as: ?C:\Program Files\R\R-2.12.0\bin;C:\Rtools\bin;C:\Rtools\MinGW64\bin;C:\Program Files\HTML Help Workshop;C:\Program Files

Hi All, I've been fooling around NVIDIA CUDA (the new architecture for parallel general-purpose computing on their latest video cards such as the GeForce 8800 series). In my opinion, these devices promise to be the perfect acceleration platform for FLAC. They offer massive SIMD-type parallelism for floating-point processing, with two available kinds of batching (thread blocks vs. grids)

I am trying to write an LLVM pass on Windows using Cygwin. When I "make" the project, a dll gets created in the Release/bin directory instead of a .so file in the Release/lib directory. The latter is what is shown in the LLVM documentation. When I try to load this dll using the -load flag to opt, nothing happens. $opt -load ../../../Release/bin/Pass.dll -help The pass that I am trying

Hi all, LLVM+clang builds fine under Cygwin 1.7, but "make check-all" fails to run because lit doesn't find the freshly built clang. The reason is as follows: in llvm/utils/lit/lit/Util.py, in the "which" method, there's 66: # Get suffixes to search. 67: pathext = os.environ.get('PATHEXT', '').split(os.pathsep) The problem is, PATHEXT is imported

Good evening, Csaba! I think rather, Cygwin does not need to know what PATHEXT would be. A patch(0001) is attached. Another patch is for unittests. Lit does not find *Tests.exe in unittests on ToT. 2010/12/24 Csaba Raduly <rcsaba at gmail.com>: > P.S. > With the above change, "make check-all" starts to run. Estimated run > time: 40 hours on my 1.8GHz single-core

Arjun, please try "configure --enable-shared" and link your dll to cygLLVM*.dll . With --enable-shared, you may build cygLLVMHello.dll manually, "make -C lib/Transforms/Hello" . (You can see cygBugpointPasses.dll, too) ...Takumi

On Wed, Feb 9, 2011 at 9:40 AM, NAKAMURA Takumi <geek4civic at gmail.com>wrote: > Anand, > > > I have not tried building llvm-gcc, though, ... > > Please show me "/path/to/config.status --version". > [Anand] Here is the config.status output taken from '/cygdrive/c/llvm-2.8': ./config.status --version llvm config.status 2.8 configured by

(sorry for the cross post, but this issue effects lots of people) Takumi diagnosed a problem when Zach switched LLVM to use compile-time multithreading, but it actually has little to do with the multithreading decisions. LLVM is rapidly moving to use more C++11 library features and more multithreading features. I think this is a good thing. However, we're hitting a specific issue on cygwin

I've built LLVM/Clang from svn under Cygwin on Windows 7. I'd like to build on the LLVMHello pass example, however, when I try: $ cd $LLVM/lib/Transforms/Hello $ make I receive a large number of errors which start with: llvm[0]: Linking Debug+Asserts Loadable Module LLVMHello.dll /cygdrive/c/Users/Graham/home/projects/llvm_cygwin/lib/Transforms/Hello/Debug+Asserts/Hello.o: In function

Hi, I followed the build instructions at http://www.aarongray.org/LLVM/BuildingLLVMonCygwin.html to build LLVM and LLVM GCC. Everything went fine except for the 'make install' step of llvm. At this step, I am getting a big list of files which are under /cygdrive/c/llvm-2.8/include/llvm and /cygdrive/c/llvm-2.8/include/llvm-c. The error I am getting is: /usr/bin/install:

On Fri, Dec 24, 2010 at 10:32 AM, NAKAMURA Takumi wrote: > me2. I don't know why too slow. I know now. It was a debug build (enable-optimized=no) created only for trying out your patch on Util.py. Doh! -- GCS a+ e++ d- C++ ULS$ L+$ !E- W++ P+++$ w++$ tv+ b++ DI D++ 5++ Life is complex, with real and imaginary parts. "Ok, it boots. Which means it must be bug-free and perfect. "

Anand, I have not tried building llvm-gcc, though, ... Please show me "/path/to/config.status --version". I doubt you did configure with "--prefix= /cygdrive/c/llvm-2.8" and you were trying to build llvm on /cygdrive/c/llvm-2.8 , ... it would be wrong. In common sense, build directory must be under your home directory or temporary directory. ...Takumi

Graham, good morning. To build LLVMHello on cygming, you should configure llvm with --enable-shared . Even with enable-shared, you might build lib/Transforms/Hello manually. (yeah, on cygming, LLVMHello should depend on tools/llvm-shlib) And, you'd be better to build with --enable-optimized. With enable-shared, llvm-shlib tends to fail with too many debug symbols. HTH, ...Takumi

Thankyou Takumi, Without --enable-optimized I get a"File too big" error from the linker: ... llvm[1]: Linking all LLVMLibs together for LLVM-3.0svn /usr/lib/gcc/i686-pc-cygwin/4.5.3/../../../../i686-pc-cygwin/bin/ld: /cygdrive/c/Users/Graham/home/projects/llvm_cygwin3/tools/llvm-shlib/Debug+Asserts/LLVM-3.0svn.a.o: too many sections (59747)

Hello, I understand that question is probably stupid, but ... I have data (polity IV index) "country","year","democ","autoc","polity","polity2" "1","Afghanistan ",1800,1,7,-6,-6 "2","Afghanistan ",1801,1,7,-6,-6 "3","Afghanistan