Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com From: "Daniel Glassey" To: cygwin AT cygwin DOT com Date: Tue, 12 Feb 2002 12:41:00 -0000 MIME-Version: 1.0 Subject: libtool problem Reply-to: Daniel Glassey Message-ID: <3C690D5C.4109.5B3BC04@localhost> X-mailer: Pegasus Mail for Windows (v4.01) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body Hi, I'm new to the list so I hope I haven't missed this being discussed already. I've tried libtoolizing a project with the latest libtool-devel (20020202-1), but after running configure;make it aborts with the following error. /bin/sh ../libtool --mode=compile g++ -DGLOBCONFPATH=\"/usr/local/etc/sword.conf\" - DUNIX -I. -I../../lib -I.. -I../../include -g -O0 -Werror -finstrument-functions -g -c -o swkey.lo `test -f ../../src/keys/swkey.cpp || echo '../../lib/'`../../src/keys/swkey.cpp s%^.*/%%: not found -e: not found -e: not found -e: not found -e: not found -e: not found -e: not found -e: not found -e: not found -e: not found -e: not found -e: not found -e: not found -e: not found -e: not found -e: not found : compile: cannot determine name of library object from `' make[2]: *** [swkey.lo] Error 1 This appears to be because the variable SED is undefined even though it is used in a few places in the generated libtool. A workaround is to set SED myself. This definitely cygwin specific because a diff of ltmain.sh against the one in libtool cvs shows that "sed" has been replaced with "${SED}" all over the place. Thanks, Daniel P.S. Please cc me on replies _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/