From: Brian S. <min...@br...> - 2007-01-09 22:12:46
|
I'm trying to build evolution from source on Windows 2000. I have mingw installed in C:\Program Files\msys\1.0\mingw\ In the course of building, I see messages like: "Can't open Files\msys\1.0\mingw\bin\as for reading: No such file or directory" but the build continues. At first glance, that seems like a pretty serious problem, but based on the fact that the build ignores it, and based on my poking around the .libs directories, I'm starting to suspect it's not really a problem. Is this a problem? Is this behavior documented somewhere? Are there workarounds besides moving my mingw installation somewhere else? |
From: Tim S. <sta...@hi...> - 2007-01-09 22:27:24
|
Brian Sammon wrote: > I'm trying to build evolution from source on Windows 2000. > I have mingw installed in C:\Program Files\msys\1.0\mingw\ > In the course of building, I see messages like: > "Can't open Files\msys\1.0\mingw\bin\as for reading: No such file > or directory" > but the build continues. > > At first glance, that seems like a pretty serious problem, but based on the fact that the build ignores it, and based on my poking around the .libs directories, I'm starting to suspect it's not really a problem. > > Is this a problem? Is this behavior documented somewhere? Are there workarounds besides moving my mingw installation somewhere else? It is NOT recommended to install minGW to a path that contains spaces. I would reinstall minGW/MSys to a path without spaces and see if the error goes away. Tim S |
From: Brian S. <min...@br...> - 2007-01-09 23:39:40
|
On Tue, 9 Jan 2007 22:26:36 +0000 (UTC) Tim Stahlhut <sta...@hi...> wrote: > Brian Sammon wrote: > > > I'm trying to build evolution from source on Windows 2000. > > I have mingw installed in C:\Program Files\msys\1.0\mingw\ > > In the course of building, I see messages like: > > "Can't open Files\msys\1.0\mingw\bin\as for reading: No such file > > or directory" > > but the build continues. > > > > At first glance, that seems like a pretty serious problem, but based on the fact that the build ignores it, and based on my poking around the .libs directories, I'm starting to suspect it's not really a problem. > > > > Is this a problem? Is this behavior documented somewhere? Are there workarounds besides moving my mingw installation somewhere else? > > It is NOT recommended to install minGW to a path that contains spaces. > I would reinstall minGW/MSys to a path without spaces and see if the > error goes away. > Tim S I'm sorry. I should have mentioned that I knew that the problem was related to the space in the file name. I'm hoping I can figure out a way to be stubborn about this. Like maybe I can convince it it's installed in "c:\progra~1\msys\1.0\mingw\". I guess what I'm asking is--has anyone looked into this beyond the "stuff breaks when there's a space in the directory name" level? Also, it seems that a bugreport/feature request posted against binutils (or something else?) wouldn't be out of line (I'd keep in mind that a fix isn't high priority for most of the people involved) |
From: Julien L. <ju...@fa...> - 2007-01-10 11:57:00
|
Brian Sammon wrote: > I'm sorry. I should have mentioned that I knew that the problem was > related to the space in the file name. I'm hoping I can figure out a way > to be stubborn about this. Like maybe I can convince it it's installed > in "c:\progra~1\msys\1.0\mingw\". The simplest way to trick any build system that it's installed in a path with no spaces is to create a fake drive with the windows `subst' command. In your autoexec.bat (for example, but you could also use the msys.bat file, or the group policies startup scripts); you type something like: subst M: "C:\Program Files\msys\1.0\mingw" All you have to do is now have "M:\bin" in your path, and remove the full path with spaces from it. Julien |
From: Earnie B. <ea...@us...> - 2007-01-10 14:41:17
|
Quoting Brian Sammon <min...@br...>: > Also, it seems that a bugreport/feature request posted against > binutils (or something else?) wouldn't be out of line (I'd keep in > mind that a fix isn't high priority for most of the people involved) I would think that for any of the current people involved that this would have zero interest. A feature request without a patch to back it would be closed; both here and at binutils. Earnie |
From: Brian D. <br...@de...> - 2007-01-09 23:45:23
|
Brian Sammon wrote: > I guess what I'm asking is--has anyone looked into this beyond the "stuff breaks when there's a space in the directory name" level? > Also, it seems that a bugreport/feature request posted against binutils (or something else?) wouldn't be out of line (I'd keep in mind that a fix isn't high priority for most of the people involved) Usually that kind of thing is due to insufficient quoting in shell scripts. But with a large project using lots of autoconf macros there can literally be thousands of lines of shell script to go over, not to mention shell fragments embedded in Makefiles, so good luck sorting that out. You can rule out the tools themselves by verifying that compiling a simple hello world and invoking gcc directly should work OK. Brian |