All right it looks like at some point I had ln -s glibtoolize libtoolize in my /usr/bin, however I had a newer version of glibtoolize in /opt/local/bin from MacPorts. And I'm using autoconf/automake from /opt/local/bin. All is fine now that I'm using the newer glibtoolize

On 5/2/07, Brian Gerkey <> wrote:

On May 2, 2007, at 2:02 PM, Kevin Barry wrote:

>  Sorry I meant to include the error in the last email:
> $ make
> ...
> /bin/sh ../libtool --tag=CC   --mode=link gcc  -I /opt/local/
> include -L/opt/local/lib   -o  dummy.lo   -lpthread -
> lcrypto  -lz -lltdl -ldl -ljpeg
> ar cru .libs/libreplace.a .libs/dummy.o~ranlib .libs/libreplace.a
> ar: .libs/dummy.o~ranlib: No such file or directory

Looks like two separate commands (ar and ranlib) got concatenated.
Or rather, were never separated as they should have been.  I've seen
some libtool scripts that use ~ as a item separator (and manipulate
IFS accordingly).

It's odd, and something I've never seen before.  I'm pretty sure
we're using the autotools correctly, so this might be a bug to report
to the libtool maintainers.


This email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
Playerstage-developers mailing list