On Thu, 2004-01-29 at 00:08, Earnie Boyd wrote:
> Good luck with fixing the white space problems in every process that
> reads arguments and uses white space as a delimiter of some sort.
Earnie has a very good point - GNU Arch faces the same problem with a
limited set of tools - patch, diff and t
Scott James Remnant wrote:
It should also be noted that Libtool suffers heavily from this problem
also. The shell uses spaces as separators, which means Libtool isn't
even able to install to a directory containing a space:
dependency_libs="-L/mnt/Program Files/unix/lib -lfoo"
comes out as three a
On Tue, 2004-01-27 at 19:27, Russ Allbery wrote:
> James Amundson <[EMAIL PROTECTED]> writes:
>
> > As far as I can tell, it is impossible to get automake to work with
> > pathnames containing spaces. The canonical example is
> > ./configure --prefix="/c/
On Tue, 2004-01-27 at 17:07, Alexandre Duret-Lutz wrote:
> In fact there is two different problems. One is that we cannot
> support spaces in source filenames.
Right. I wasn't even thinking about that, but I definitely see your
point. I don't suppose colons in source filename would be work ver
>>> "James" == James Amundson <[EMAIL PROTECTED]> writes:
James> Wait a minute... You were joking, right? An important
James> piece of infrastructure like automake shouldn't have
James> amateurish mistakes like forgetting to properly quote
James> pathnames in scripts and makefiles.
James> Su
> "Russ" == Russ Allbery <[EMAIL PROTECTED]> writes:
Russ> make uses a space as a separator, and getting it to accept spaces in file
Russ> names is extremely difficult or impossible depending on the version of
Russ> make that you're using.
Yeah, and the problem is made worse because quoting f
On Tue, 27 Jan 2004, Earnie Boyd wrote:
> > Surely the automake maintainers realize that this is a bug, don't they?
> >
>
> No, it is not an automake or autoconf bug. Autoconf and Automake are
> about portability and spaces in path names are not portable.
Which platforms does automake run on whe
Earnie Boyd wrote:
> No, it is not an automake or autoconf bug. Autoconf and Automake are
> about portability and spaces in path names are not portable.
Explain that to some ported-to-unix programs that create
files with spaces in them. It is a matter of custom. On Unix,
the custom is to not d
James Amundson wrote:
On Tue, 2004-01-27 at 06:21, Earnie Boyd wrote:
The usual response to this problem is
_don't_use_path_names_with_spaces_.
Heh heh.
There are different ways to modify
what you are doing that it is not worth modifying the autotools to
handle the space in path name probl
James Amundson <[EMAIL PROTECTED]> writes:
> As far as I can tell, it is impossible to get automake to work with
> pathnames containing spaces. The canonical example is
> ./configure --prefix="/c/Program Files"
> make install
> which will cause make t
On Tue, 2004-01-27 at 06:21, Earnie Boyd wrote:
> The usual response to this problem is
> _don't_use_path_names_with_spaces_.
Heh heh.
> There are different ways to modify
> what you are doing that it is not worth modifying the autotools to
> handle the space in path name problem.
Wait a mi
n wrote:
As far as I can tell, it is impossible to get automake to work with
pathnames containing spaces. The canonical example is
./configure --prefix="/c/Program Files"
make install
which will cause make to choke because install will be called with
unquoted pathnames. I d
As far as I can tell, it is impossible to get automake to work with
pathnames containing spaces. The canonical example is
./configure --prefix="/c/Program Files"
make install
which will cause make to choke because install will be called with
unquoted pathnames. I don
13 matches
Mail list logo
