GNU bug report logs - #21910
libtool should check that directory names do not contain spaces

Previous Next

To reply to this bug, email your comments to 21910 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Vincent Lefevre <vincent <at> vinc17.net>
To: bug-libtool <at> gnu.org
Subject: libtool should check that directory names do not contain spaces
Date: Fri, 13 Nov 2015 17:09:46 +0100

libtool doesn't support directory names with spaces, and this will
not be fixed (at least in the near future). In order to avoid obscure
error messages (because internally, such paths get split and so on),
libtool should generate code to make sure that such directory names
are detected as soon as possible and to output a clear error message.

-- 
Vincent Lefèvre <vincent <at> vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Message #8 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Earnie <earnie <at> users.sourceforge.net>
To: bug-libtool <at> gnu.org
Subject: Re: bug#21910: libtool should check that directory names do not
 contain spaces
Date: Mon, 16 Nov 2015 15:32:02 -0500

On 11/13/2015 11:09 AM, Vincent Lefevre wrote:
> libtool doesn't support directory names with spaces, and this will
> not be fixed (at least in the near future). In order to avoid obscure
> error messages (because internally, such paths get split and so on),
> libtool should generate code to make sure that such directory names
> are detected as soon as possible and to output a clear error message.
> 

Why not support all characters allowed in the file system?  Any ASCII
character or now-a-days UNICODE file names are supported in the OS.  Yes
the user needs to be careful with executing a script with white space
and special characters in the file name but not allowing it at all is a
bit fallacious.

-- 
Earnie

Message #11 received at 21910 <at> debbugs.gnu.org (full text, mbox):

From: Bob Friesenhahn <bfriesen <at> simple.dallas.tx.us>
To: Earnie <earnie <at> users.sourceforge.net>
Cc: 21910 <at> debbugs.gnu.org, bug-libtool <at> gnu.org
Subject: Re: bug#21910: libtool should check that directory names do not
 contain spaces
Date: Mon, 16 Nov 2015 20:09:28 -0600 (CST)

On Mon, 16 Nov 2015, Earnie wrote:

> On 11/13/2015 11:09 AM, Vincent Lefevre wrote:
>> libtool doesn't support directory names with spaces, and this will
>> not be fixed (at least in the near future). In order to avoid obscure
>> error messages (because internally, such paths get split and so on),
>> libtool should generate code to make sure that such directory names
>> are detected as soon as possible and to output a clear error message.
>>
>
> Why not support all characters allowed in the file system?  Any ASCII
> character or now-a-days UNICODE file names are supported in the OS.  Yes
> the user needs to be careful with executing a script with white space
> and special characters in the file name but not allowing it at all is a
> bit fallacious.

The problem is that libtool is a portable shell script and arguments 
need to be passed to the utilities it executes, with all that that 
entails (e.g. argument splitting and handling of special quote 
characters).  If libtool was a binary, then this problem would be 
gone.

A future issue is that libtool is configured via an autoconf configure 
script which may be a 1MB portable shell script, which also needs to 
survive the torture-test.

Somehow this still usually manages to run under MSYS. :-)

Bob
-- 
Bob Friesenhahn
bfriesen <at> simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.