Jim Grosbach
2011-Sep-21 17:31 UTC
[LLVMdev] ../llvm/configure fails in Cygwin with space character in path name?
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 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 > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
Csaba Raduly
2011-Sep-22 12:31 UTC
[LLVMdev] ../llvm/configure fails in Cygwin with space character in path name?
On Wed, Sep 21, 2011 at 7:31 PM, Jim Grosbach wrote:> 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.GNU Make doesn't handle embedded spaces: $ cat Makefile all: foo\ bar foo\ bar: foo\ bar.o $ ls foo bar.c Makefile $ make make: *** No rule to make target `foo bar.o', needed by `foo bar'. Stop. Make seems unable to find the link from "foo bar.c" to "foo bar.o" Shell quoting with ' ' does not apply. It's probably best to avoid spaces in filenames from the outset. Csaba -- GCS a+ e++ d- C++ ULS$ L+$ !E- W++ P+++$ w++$ tv+ b++ DI D++ 5++ The Tao of math: The numbers you can count are not the real numbers. Life is complex, with real and imaginary parts. "Ok, it boots. Which means it must be bug-free and perfect. " -- Linus Torvalds "People disagree with me. I just ignore them." -- Linus Torvalds
Joachim Durchholz
2011-Sep-22 18:20 UTC
[LLVMdev] ../llvm/configure fails in Cygwin with space character in path name?
Am 22.09.2011 14:31, schrieb Csaba Raduly:> GNU Make doesn't handle embedded spaces:Actually it does. It's just not pretty. See http://www.cmcrossroads.com/index2.php?option=com_content&id=7859 (Google it as "GNU Make meets file names with spaces in them", including the quotes.) Note that the more obscure techniques can be reliably used in an LLVM context, since LLVM relies on GNU Make anyway. I do not know whether this will stay so in the future; I guess that's for the LLVM team to answer.> $ cat Makefile > all: foo\ bar > > foo\ bar: foo\ bar.oThe above URL tells me you need to double the backslashes. I.e. your Makefile should look like this: all: foo\\ bar foo\\ bar: foo\\ bar.o (Disclaimer: I haven't tested this.)> It's probably best to avoid spaces in filenames from the outset.That's actually the strategy that the above-linked text recommends. (It's also a shame.) Regards, Jo
Possibly Parallel Threads
- [LLVMdev] ../llvm/configure fails in Cygwin with space character in path name?
- [LLVMdev] ../llvm/configure fails in Cygwin with space character in path name?
- [LLVMdev] Test failures
- [LLVMdev] Executable file size comparison
- [LLVMdev] Executable file size comparison