Hi,
I'm new to this list so please excuse me if this question does not
belong to this list.
My problem is the following:
I have a set of sources split into to directories, client and server,
from which I want to create one shared library. My approach has been to try
to make a convenience library
Title: RE: Problems using libtool, suns c++ compiler and convenience libraries
Erik,
If you are using CVS Libtool, then the problem is with
your Compiler. If not, then CVS Libtool may fix it.
HTH,
Robert
-Original Message-
From: Erik Assum [mailto:[EMAIL PROTECTED]]
Sent: Frid
Using cvs libtool from just now, which passed everything :-), I tried
bootstraping sasl, and found that the libtool generated died at
progname=`$echo "$0" | ${SED} 's%^.*/%%'`
modename="$progname"
because SED was empty - where should SED be defined? (Adding SED=sed just
before the above had it wo
Title: RE: SED ?
Patrick,
Yes something is wrong here, I'm currently working on fixing this
but I didn't know it was broken in CVS Libtool. The problem I'm
having is that $SED needs to be set earlier than it currently is,
so the resulting libtool is attempting to operate with untested
"sed"
On Fri, Dec 13, 2002 at 12:37:14AM -0600, Robert Boehne wrote:
> I'm seeing this sed invocation spitting out complaints
> on any platform not using GNU sed, i.e. OS X, FreeBSD, IRIX, Tru64
> to name a few. Any idea why?
>
> lt_compile=`echo "$ac_compile" | sed \
>-e 's:.*FLAGS\}\? :&$lt_comp
