Re: "~" in builddirs caused libtool to fail

[Kurt Roeckx]

On Sun, Sep 24, 2006 at 03:32:26PM +0200, Elimar Riesebieter wrote:
> On Sun, 24 Sep 2006 the mental interface of
> Kurt Roeckx told:
> > 
> > The current version in Debian unstable has:
> > ltmain.sh (GNU libtool) 1.5.22 (1.1220.2.365 2005/12/18 22:14:06)
> > 
> > The patch mentioned in the mail says it's last modified 2003-03-24,
> > I've tried building with a ~ in the path and it worked, so I have no
> > idea what's wrong.
> > 
> > Elimar, could you check what version of libtool you're using,
> > and what happens exactly?  Are you sure this is a libtool problem?
> 
> # libtool --version
> ltmain.sh (GNU libtool) 1.5.22 Debian 1.5.22-4 (1.1220.2.365 2005/12/18 
> 22:14:06)

That's what you have installed in /usr/bin, try:
./ld10k1/libtool --version

> Trying to build alsa-tools-1.0.12~rc1:
> 
> ranlib /source/alsa/svn-pkg-alsa/tarballs/alsa-tools-1.0.12
> ranlib: '/source/alsa/svn-pkg-alsa/tarballs/alsa-tools-1.0.12': No such file
> rc1/debian/tmp/usr/lib/liblo10k1.a
> ../libtool: line 5985: rc1/debian/tmp/usr/lib/liblo10k1.a: No such file or 
> directory
> 
> The builddir is indeed
> /source/alsa/svn-pkg-alsa/tarballs/alsa-tools-1.0.12~rc1

I get:
ranlib /usr/src/alsa-tools-1.0.12~rc1/debian/tmp/usr/lib/liblo10k1.a

Which seems to be working perfectly.  I don't get any errors at all.

What shell are you using, and what is /bin/sh pointing to?

(Note that I've just renamed the alsa-tools-1.0.12 to
alsa-tools-1.0.12~rc1, this isn't really an rc1.)


Kurt