Re: [Ecls-list] Help needed: autoconf with spaces in names
On 10/08/2010 07:36 PM, Daniel Herring wrote: So it appears that spaces in directory names are strongly discouraged. An authoritative answer would have to come from the autoconf list. Its possible this changed in the recently released autoconf 2.68, but I doubt it. You might find it interesting to read the thread I started on the automake list over six years ago: http://www.mail-archive.com/autom...@gnu.org/msg08152.html Note especially this message: http://www.mail-archive.com/autom...@gnu.org/msg08163.html I'm afraid I haven't what has happened with this issue since then. --Jim Amundson -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb ___ Ecls-list mailing list Ecls-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ecls-list
Re: [Ecls-list] Help needed: autoconf with spaces in names
Daniel Herring dherr...@tentpost.com writes: On Sun, 3 Oct 2010, Juan Jose Garcia-Ripoll wrote: It seems that configure does not work when one of the directories contains a space in the name. Is this a known limitation? Here's output from a recent GNU package's configure script. # ../a\ space/libtool-2.4/configure ../a space/libtool-2.4/configure: line 2668: ../a: No such file or directory ## --- ## ## Configuring libtool 2.4 ## ## --- ## checking for a BSD-compatible install... /usr/bin/ginstall -c checking whether build environment is sane... configure: error: unsafe srcdir value: `../a space/libtool-2.4' # echo $? 1 # head ../a\ space/libtool-2.4/configure #! /bin/sh # Guess values for system-dependent variables and create Makefiles. # Generated by GNU Autoconf 2.67 for GNU Libtool 2.4. # # Report bugs to bug-libt...@gnu.org. # # # Copyright (C) 1992, 1993, 1994, 1995, 1996, 1998, 1999, 2000, 2001, # 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010 Free Software # Foundation, Inc. So it appears that spaces in directory names are strongly discouraged. An authoritative answer would have to come from the autoconf list. Its possible this changed in the recently released autoconf 2.68, but I doubt it. In any case, it would be quite interesting to test all the scripts and programs in a unix installation to have some statistics on how they deal with spaces in paths. But if autoconf still tries to avoid them, my bet is that quite a proportion of essential tools still don't deal with them nicely. -- __Pascal Bourguignon__ http://www.informatimago.com/ -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb ___ Ecls-list mailing list Ecls-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ecls-list
Re: [Ecls-list] Help needed: autoconf with spaces in names
On Sun, 3 Oct 2010, Juan Jose Garcia-Ripoll wrote: It seems that configure does not work when one of the directories contains a space in the name. Is this a known limitation? Here's output from a recent GNU package's configure script. # ../a\ space/libtool-2.4/configure ../a space/libtool-2.4/configure: line 2668: ../a: No such file or directory ## --- ## ## Configuring libtool 2.4 ## ## --- ## checking for a BSD-compatible install... /usr/bin/ginstall -c checking whether build environment is sane... configure: error: unsafe srcdir value: `../a space/libtool-2.4' # echo $? 1 # head ../a\ space/libtool-2.4/configure #! /bin/sh # Guess values for system-dependent variables and create Makefiles. # Generated by GNU Autoconf 2.67 for GNU Libtool 2.4. # # Report bugs to bug-libt...@gnu.org. # # # Copyright (C) 1992, 1993, 1994, 1995, 1996, 1998, 1999, 2000, 2001, # 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010 Free Software # Foundation, Inc. So it appears that spaces in directory names are strongly discouraged. An authoritative answer would have to come from the autoconf list. Its possible this changed in the recently released autoconf 2.68, but I doubt it. - Daniel -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb ___ Ecls-list mailing list Ecls-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ecls-list
Re: [Ecls-list] Help needed: autoconf with spaces in names
On 3 October 2010 22:41, Juan Jose Garcia-Ripoll
juanjose.garciarip...@googlemail.com wrote:
On Sun, Oct 3, 2010 at 10:31 PM, Samium Gromoff
_deepf...@feelingofgreen.ru wrote:
On Sun, 3 Oct 2010 22:16:21 +0200, Juan Jose Garcia-Ripoll
juanjose.garciarip...@googlemail.com wrote:
It seems that configure does not work when one of the directories
contains
a space in the name. Is this a known limitation?
I have never /ever/ tried to run configure with --prefix having spaces
in it.
On Linux due to cultural reasons.
On Windows -- because MinGW strongly encourages one to install itself at
disc:/MinGW, and one would have to be pressed hard to --prefix a package
into outside of MinGW's /.
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.
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 ;-)
I've just tried with curl, since I have the sources on my machine and
it uses autoconf. I copied it to '/tmp/some where' and then ran
'./configure --prefix=/tmp/some path'.
The configure step worked without complaint, as did the compile.
make install died, though:
/tmp/some where/curl$ make install
Making install in lib
make[1]: Entering directory `/tmp/some where/curl/lib'
make[2]: Entering directory `/tmp/some where/curl/lib'
test -z /tmp/some path/lib || /bin/mkdir -p /tmp/some path/lib
/bin/bash ../libtool --mode=install /usr/bin/install -c
'libcurl.la' '/tmp/some path/lib/libcurl.la'
libtool: install: /usr/bin/install -c .libs/libcurl.so.4.2.0 /tmp/some
path/lib/libcurl.so.4.2.0
/usr/bin/install: target `path/lib/libcurl.so.4.2.0' is not a directory
make[2]: *** [install-libLTLIBRARIES] Error 1
make[2]: Leaving directory `/tmp/some where/curl/lib'
make[1]: *** [install-am] Error 2
make[1]: Leaving directory `/tmp/some where/curl/lib'
make: *** [install-recursive] Error 1
So it doesn't seem like configure is necessarily broken when there's a
space in the directory containing the source tree.
Then I tried sshguard and there was no problem, even with the install.
This patch gets past the issue with the top level configure:
--- a/configure
+++ b/configure
@@ -34,6 +34,6 @@ if ( echo $* | grep guess-host-cflags ); then
fi
cd ${buildir}
-${srcdir}/configure --srcdir=${srcdir} $@
+${srcdir}/configure --srcdir=${srcdir} $@
echo Configuration complete. To build ECL, issue 'make' in this directory.
but then you get:
configure: error: cannot run /bin/bash /tmp/some where/ecl/src/gmp/config.sub
I tried for a bit to fix that, but it's past my bed time :)
--
Michael Wood esiot...@gmail.com
--
Virtualization is moving to the mainstream and overtaking non-virtualized
environment for deploying applications. Does it make network security
easier or more difficult to achieve? Read this whitepaper to separate the
two and get a better understanding.
http://p.sf.net/sfu/hp-phase2-d2d
___
Ecls-list mailing list
Ecls-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ecls-list
Re: [Ecls-list] Help needed: autoconf with spaces in names
On Mon, Oct 4, 2010 at 12:09 AM, Michael Wood esiot...@gmail.com wrote: I've just tried with curl, since I have the sources on my machine and it uses autoconf. I copied it to '/tmp/some where' and then ran './configure --prefix=/tmp/some path'. The configure step worked without complaint Packages should be configurable from _outside_ the sources. Indeed, most of the times sources may be read-only and the compilation directory a read/write one. Or one may have one set of sources and many different builds. Try the same from a different directory, like /path/to/ecl/with a space/in/it/configure --prefix= Juanjo -- Instituto de Física Fundamental, CSIC c/ Serrano, 113b, Madrid 28006 (Spain) http://juanjose.garciaripoll.googlepages.com -- Virtualization is moving to the mainstream and overtaking non-virtualized environment for deploying applications. Does it make network security easier or more difficult to achieve? Read this whitepaper to separate the two and get a better understanding. http://p.sf.net/sfu/hp-phase2-d2d___ Ecls-list mailing list Ecls-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ecls-list
Re: [Ecls-list] Help needed: autoconf with spaces in names
Juan Jose Garcia-Ripoll juanjose.garciarip...@googlemail.com writes: It seems that configure does not work when one of the directories contains a space in the name. Is this a known limitation? Allowing spaces in pathnames would require an effort superior to that of the correction of the Y2K bug. At least, the Y2K bug was limited to the handling of dates. Handling spaces in pathnames would impact absolutely ALL the programs and scripts ever written (plus the endoctrinement required to prevent further writing of bad scripts, it would probably be easier to try to replace all the shells with ones who would avoid the problem in the first place, which is almost impossible). -- __Pascal Bourguignon__ http://www.informatimago.com/ -- Virtualization is moving to the mainstream and overtaking non-virtualized environment for deploying applications. Does it make network security easier or more difficult to achieve? Read this whitepaper to separate the two and get a better understanding. http://p.sf.net/sfu/hp-phase2-d2d ___ Ecls-list mailing list Ecls-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ecls-list
Re: [Ecls-list] Help needed: autoconf with spaces in names
On Mon, 04 Oct 2010 01:52:45 +0200 p...@informatimago.com (Pascal J. Bourguignon) wrote: Juan Jose Garcia-Ripoll juanjose.garciarip...@googlemail.com writes: It seems that configure does not work when one of the directories contains a space in the name. Is this a known limitation? Allowing spaces in pathnames would require an effort superior to that of the correction of the Y2K bug. At least, the Y2K bug was limited to the handling of dates. Handling spaces in pathnames would impact absolutely ALL the programs and scripts ever written (plus the endoctrinement required to prevent further writing of bad scripts, it would probably be easier to try to replace all the shells with ones who would avoid the problem in the first place, which is almost impossible). Heh. But I admit part of this is true, and personally avoid special characters (as well as space) in file names to avoid the hell of untagged encodings and character escaping/quoting madness in every script (or at the CLI, which I use a lot)... But sorry for replying without suggesting a working solution other than renaming the faulty files. It is likely that one of the scripts is missing explicit quotes around the use of a variable, or that it should use the special option a processing command might support, such as -X option to grep for piping through xargs, etc. -- Matt -- Virtualization is moving to the mainstream and overtaking non-virtualized environment for deploying applications. Does it make network security easier or more difficult to achieve? Read this whitepaper to separate the two and get a better understanding. http://p.sf.net/sfu/hp-phase2-d2d ___ Ecls-list mailing list Ecls-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ecls-list
Re: [Ecls-list] Help needed: autoconf with spaces in names
On Sun, 3 Oct 2010 20:22:13 -0400 Matthew Mondor mm_li...@pulsar-zone.net wrote: use the special option a processing command might support, such as -X option to grep for piping through xargs, etc. Err, I meant -print0 option to find, perl -0, sort -z, grep -Z etc. -- Matt -- Virtualization is moving to the mainstream and overtaking non-virtualized environment for deploying applications. Does it make network security easier or more difficult to achieve? Read this whitepaper to separate the two and get a better understanding. http://p.sf.net/sfu/hp-phase2-d2d ___ Ecls-list mailing list Ecls-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ecls-list
Re: [Ecls-list] Help needed: autoconf with spaces in names
On Sun, Oct 3, 2010 at 3:16 PM, Juan Jose Garcia-Ripoll juanjose.garciarip...@googlemail.com wrote: It seems that configure does not work when one of the directories contains a space in the name. Is this a known limitation? Juanjo Hmm, I don't understand what you mean... But, I usually invoke the configure script with a relative path to avoid troubles. By the way, ECL's configure would refuse to configure outside the source directory, so it was already not working :-) -- Gaby -- Virtualization is moving to the mainstream and overtaking non-virtualized environment for deploying applications. Does it make network security easier or more difficult to achieve? Read this whitepaper to separate the two and get a better understanding. http://p.sf.net/sfu/hp-phase2-d2d ___ Ecls-list mailing list Ecls-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ecls-list
