Re: How to specify a version script?

[Josh Huber]

"Howard Chu" <address@hidden> writes:

> Yes, this is a nagging problem, the Cyrus folks seem to be mired in
> a swamp of out-of-date build tools and for whatever reasons are
> constrained not to update themselves. I've raised this issue with
> them before. So far we've been able to work around this by replacing
> their bundled libtool with libtool 1.4.2 in our own builds, which
> works a lot better on the variety of platforms we deal with.

I'm having one other issue that perhaps you know the solution for.
I've replaced the libtool with 1.4.2 in my build, but libtool
(automake?) doesn't seem to be finding sed:

../libtool: line 1: s%^.*/%%: No such file or directory
../libtool: line 1: -e: command not found
../libtool: line 1: -e: command not found
../libtool: line 1: -e: command not found
../libtool: line 1: -e: command not found
../libtool: line 1: -e: command not found
../libtool: line 1: -e: command not found
../libtool: line 1: -e: command not found
../libtool: line 1: -e: command not found
../libtool: line 1: -e: command not found
../libtool: line 1: -e: command not found
../libtool: line 1: -e: command not found
../libtool: line 1: -e: command not found
../libtool: line 1: -e: command not found
../libtool: line 1: -e: command not found
../libtool: line 1: -e: command not found
../libtool: line 1: -e: command not found
: compile: cannot determine name of library object from `'
make: *** [auxprop.lo] Error 1


Issuing "export SED=/bin/sed" fixes the problem, but I'd like to know
what the real cause of the problem is.

Thanks for your help,

-- 
Josh Huber