building in directory with SPC

Hi!  Building libtool v2.2 and running 'make check' in a directory path
containing SPC fails, see output below.

This was reported some time ago, see:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=193163
http://lists.gnu.org/archive/html/bug-libtool/2003-11/msg00002.html

The debian bug report also contains a patch.

Is the patch the right thing?

Would it be difficult to fix this?

I am sorry if you already replied to this, I couldn't find any replies
in the mailing list archive, but I only checked a few months after the
post.  There were a lot of spam in the archives so I could have missed
it.

Thanks,
/Simon

jas <at> mocca:~/src/foo bar/libtool-2.2$ make check
make  check-recursive
make[1]: Entering directory `/home/jas/src/foo bar/libtool-2.2'
make[2]: Entering directory `/home/jas/src/foo bar/libtool-2.2'
make  check-TESTS check-local
make[3]: Entering directory `/home/jas/src/foo bar/libtool-2.2'
PASS: tests/link.test
PASS: tests/link-2.test

Re: building in directory with SPC

Hello Simon,

Thanks for the report.

* Simon Josefsson wrote on Tue, Apr 01, 2008 at 12:11:32PM CEST:
> Hi!  Building libtool v2.2 and running 'make check' in a directory path
> containing SPC fails, see output below.

Libtool is not supported in a directory path containing a space.

> This was reported some time ago, see:
> 
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=193163
> http://lists.gnu.org/archive/html/bug-libtool/2003-11/msg00002.html
> 
> The debian bug report also contains a patch.

90% of the patch are needless and thus useless noise, the 3 remaining
hunks touch but 1% of the real issues that libtool has with spaces.

> Would it be difficult to fix this?

Yes, a correct and thorough fix would require to rewrite large portions
of libtool and quite likely make it much slower than it is today.

Cheers,
Ralf

Re: building in directory with SPC

Ralf Wildenhues <Ralf.Wildenhues <at> gmx.de> writes:

> Hello Simon,
>
> Thanks for the report.

Hi Ralf.  Thanks for prompt reply!

> * Simon Josefsson wrote on Tue, Apr 01, 2008 at 12:11:32PM CEST:
>> Hi!  Building libtool v2.2 and running 'make check' in a directory path
>> containing SPC fails, see output below.
>
> Libtool is not supported in a directory path containing a space.

Ok.

>> This was reported some time ago, see:
>> 
>> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=193163
>> http://lists.gnu.org/archive/html/bug-libtool/2003-11/msg00002.html
>> 
>> The debian bug report also contains a patch.
>
> 90% of the patch are needless and thus useless noise, the 3 remaining
> hunks touch but 1% of the real issues that libtool has with spaces.
>
>> Would it be difficult to fix this?
>
> Yes, a correct and thorough fix would require to rewrite large portions
> of libtool and quite likely make it much slower than it is today.

Re: building in directory with SPC

On Tue, 1 Apr 2008, Ralf Wildenhues wrote:
>
>> Would it be difficult to fix this?
>
> Yes, a correct and thorough fix would require to rewrite large portions
> of libtool and quite likely make it much slower than it is today.

It should be very fast if it was re-written in Python, Perl, Ruby, or 
even Guile.  Using a more capable implementation language would help 
avoid many problems caused by using a Unix shell.

From time to time it is useful to re-assess original assumptions.

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

Re: building in directory with SPC

On 1 Apr 2008, at 11:13, Bob Friesenhahn wrote:
> On Tue, 1 Apr 2008, Ralf Wildenhues wrote:
>>
>>> Would it be difficult to fix this?
>>
>> Yes, a correct and thorough fix would require to rewrite large  
>> portions
>> of libtool and quite likely make it much slower than it is today.
>
> It should be very fast if it was re-written in [[...]] Perl [[...]]

I quit!

Cheers,
	Gary
--

-- 
   ())_.              Email me: gary <at> gnu.org
   ( '/           Read my blog: http://blog.azazil.net
   / )=         ...and my book: http://sources.redhat.com/autobook
`(_~)_

_______________________________________________
Bug-libtool mailing list
Bug-libtool <at> gnu.org
http://lists.gnu.org/mailman/listinfo/bug-libtool

Re: building in directory with SPC

On Tue, 1 Apr 2008, Gary V. Vaughan wrote:
>>> Yes, a correct and thorough fix would require to rewrite large portions
>>> of libtool and quite likely make it much slower than it is today.
>> 
>> It should be very fast if it was re-written in [[...]] Perl [[...]]
>
> I quit!

April Fools!

Perl is not really a good choice as an implementation language since 
its complex syntax could make the result almost as obtuse as libtool 
is today.  Perl code does not have to be difficult to read, but it 
often turns out that way.

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

Re: building in directory with SPC

Hi Bob,

If I might be permitted to selectively quote you...

On 1 Apr 2008, at 21:21, Bob Friesenhahn wrote:
>
> Perl is not really a good [[...]] language

Since we agree so thoroughly, I'll stay a while longer.

Cheers,
	Gary
--

-- 
   ())_.              Email me: gary <at> gnu.org
   ( '/           Read my blog: http://blog.azazil.net
   / )=         ...and my book: http://sources.redhat.com/autobook
`(_~)_

_______________________________________________
Bug-libtool mailing list
Bug-libtool <at> gnu.org
http://lists.gnu.org/mailman/listinfo/bug-libtool

Re: building in directory with SPC

On Tue, 1 Apr 2008, Gary V. Vaughan wrote:
>> 
>> Perl is not really a good [[...]] language
>
> Since we agree so thoroughly, I'll stay a while longer.

I am glad to hear that. 

When porting "libtool" to a new scripting language, there is the 
little problem that much of "libtool" is actually part of the 
configure script.  That part of the code inherits everything which is 
good and bad with legacy Unix scripting, including the challenge of 
dealing with spaces.

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

[libtool 2.2.2] testsuite: 8 failed

_______________________________________________
Bug-libtool mailing list
Bug-libtool <at> gnu.org
http://lists.gnu.org/mailman/listinfo/bug-libtool

$echo left undefined in libtool script

Running libtool 2.2.2.

I was rebuilding the build system on an autotools
package with libtool 2.2.2.  The make now fails. The
command line where the fail occurs was a compile
command.

/bin/sh ../../libtool --tag=CC  --mode=compile gcc
-std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -Wall -g -O2
-MT libguile_gucu_curses_v_0_la-curs_func.lo -MD -MP
-MF .deps/libguile_gucu_curses_v_0_la-curs_func.Tpo -c
-o libguile_gucu_curses_v__la-curs_func.la `test -f
'curs_func.c' || echo './'`curs_func.c

The first error was

../../libtool: line 818: X--tag=CC: command not found

The line of the libtool script in question was

case $arg in
-*=*) optarg=`$echo "X$arg" | $Xsed -e
's/[-_a-zA-Z0-]*=//'` ;;

Obviously, $echo is not getting set.

A workaround that makes it compile is to prepend the
line with echo=echo

echo=echo /bin/sh ../../libtool --tag=CC 

Thanks,

Mike Gran