Evening all. Cygwin creates a home directory based on the user name of the Windows user (/home/Ken\ Sharp for example). Unfortunately the space screws up the creation of Makefile.in after running a configure - indeed it is not created at all, but there is no error from configure. Creating a new directory with no spaces in the path seems to solve this (/home/ken). [At this point I'm not sure if having configure in the directory with spaces is the problem, or the compile directory having spaces is the problem - I will check this but it is incredibly slow.] This may be a Cygwin bug, and may be well known, but I cannot find any details on this. Can anyone help? Is this a bug? Should configure be making sure Makefile.in is created before claiming to complete successfully?
On Sat, 2011-10-22 at 12:41 -0500, KenSharp wrote:> Cygwin creates a home directory based on the user name of the Windows > user (/home/Ken\ Sharp for example). > > Unfortunately the space screws up the creation of Makefile.in after > running a configure - indeed it is not created at all, but there is no > error from configure. Creating a new directory with no spaces in the > path seems to solve this (/home/ken). >That sounds like a problem in configure to me: IIRC configure is a shell script and this is a common problem in shell scripts that are not explicitly written to handle names with spaces in them. Check the cygwin bugs register and/or ask them about it: nobody else is likely to know whether they use a standard 'configure' shell script or if its one of their own. Martin
KenSharp wrote:> Cygwin creates a home directory based on the user name of the Windows user (/home/Ken\ Sharp for example). > > Unfortunately the space screws up the creation of Makefile.in after running a configure - indeed it is not created at all, but there is no error from configure. Creating a new directory with no spaces in the path seems to solve this (/home/ken).Look inside configure.log for the place which fails. Find it in configure or even better in configure.ac and put double quotes around the path variable(s). Then send a patch in.
Alexandre Julliard wrote:> Looks fine to me, what makes you think that files are missing?I assumed the folders would be created along with the makefiles. If not, then that's fine - I'm not used to seeing a clean directory! Ignore that bit then, the missing Makefile.in is the problem. I would like to reiterate that running configure in a directory structure with no spaces does not have a problem.