Did you run ./autogen.sh on your trunk checkout? It sounds like you
didn't. Then again, you have a 'configure', so you must have.
It may be libtool 1.6 that's the problem... most of us use libtool
1.4.3, and libtool 1.5 is known not to work with svn. I've never even
heard of libtool 1.6! Can someone comment on this?
On Mon, 2003-12-29 at 02:53, Florian Weimer wrote:
> It's probably a local configuration error (this is a Debian/sid system),
> but I can't figure out what's going on.
>
> After invoking ./configure, I get the following errors:
>
> config.status: executing libtool commands
> config.status: creating libtool
> sed: can't read /ltmain.sh: No such file or directory
> mv: cannot stat `libtoolT': No such file or directory
> cp: cannot stat `libtoolT': No such file or directory
> chmod: failed to get attributes of `libtool': No such file or directory
>
> It seems as if the path to ltmain.sh is not correctly detected. Any
> ideas? I'm running autoconf 2.58 and libtool 1.6.
>
> Now I'm using the prepackaged source tarball, which doesn't have this
> problem.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Dec 29 17:20:20 2003