<br><br><div class="gmail_quote">On Sun, Oct 3, 2010 at 10:31 PM, Samium Gromoff <span dir="ltr"><_<a href="mailto:deepfire@feelingofgreen.ru">deepfire@feelingofgreen.ru</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Sun, 3 Oct 2010 22:16:21 +0200, Juan Jose Garcia-Ripoll <<a href="mailto:juanjose.garciaripoll@googlemail.com">juanjose.garciaripoll@googlemail.com</a>> wrote:<br>
> It seems that "configure" does not work when one of the directories contains<br>
> a space in the name. Is this a known limitation?<br>
<br>
</div>I have never /ever/ tried to run configure with --prefix having spaces<br>
in it.<br>
<br>
On Linux due to cultural reasons.<br>
<br>
On Windows -- because MinGW strongly encourages one to install itself at<br>
disc:/MinGW, and one would have to be pressed hard to --prefix a package<br>
into outside of MinGW's /.</blockquote><div><br></div><div>I am not even talking about "prefix", which seems to work fine, but about the location of sources. If ECL's source tree is say in "/home/jjgarcia/some path/ecl/" then "configure" refuses to run because /bin/bash refuses to execute files (config.sub) which are located in paths with spaces. That seems like a bug in autoconf to me.</div>
<div><br></div><div>BTW, the fact that you have not ever done it does not mean that people haven't tried and been bitten by it... and complained ;-)</div><div><br></div><div>Juanjo</div></div><br>-- <br>Instituto de Física Fundamental, CSIC<br>
c/ Serrano, 113b, Madrid 28006 (Spain) <br><a href="http://juanjose.garciaripoll.googlepages.com">http://juanjose.garciaripoll.googlepages.com</a><br>