Le lun 25/11/2002 à 19:23, Elizabeth Barham a écrit : > Xavier Bestel <xavier.bestel@free.fr> writes: > > > I had some problem (crashes) on my computer (debian/unstable), and as a > > result I think some system files got corrupted. Now the crash cause is > > fixed, but libtoolize is broken: whenever I run libtoolize, the libtool > > it generates has syntax errors in it. But when I simply copy > > /usr/bin/libtool over the generated one, then the build works. > > I've tried reinstalling a bunch of packages (libtool, all auto*, and a > > load of others) but it didn't do anything. As I need my machine to > > develop, I want to get this fixed but can't totally reinstall that. > > > > Anyone knows how libtoolize generates libtool, what packages are needed > > to get back to a working system ? > > m4? > > You can always download the latest (CVS if you want) versions of > libtool and the autotools as well. > > What errors exactly are you receiving? /bin/sh ../libtool --mode=link gcc -O2 -g -Wall -Wall -o gimp-remote-1.3 gimp-remote.o -Wl,--export-dynamic -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgdk_pixbuf-2.0 -lm -lpangoxft-1.0 -lpangox-1.0 -lpango-1.0 -lgobject-2.0 -lgmodule-2.0 -ldl -lglib-2.0 -L/usr/X11R6/lib -lSM -lICE -lX11 -lXmu -lXt ../libtool: line 4947: syntax error near unexpected token `done' ../libtool: line 4947: ` done' I have attached the generated libtool; there's effectively something really messed up inside, but I don't know why it's been born dead.
Attachment:
libtool.gz
Description: GNU Zip compressed data