"David H. Peyton" wrote: [] > /usr/bin/install -c -m 755 > /sw/src/freetype2-2.0.8-4/freetype-2.0.8/builds/unix/freetype-config \ > /sw/bin/freetype-config > mv /sw/src/root-freetype2-2.0.8-4/sw/lib/libfreetype.6*dylib > /sw/src/root-freetype2-shlibs-2.0.8-4/sw/lib > usage: mv [-fi] source target > mv [-fi] source ... directory > ### mv failed, exit code 1 > Failed: installing freetype2-shlibs-2.0.8-4 failed
It is now becoming clear that the problem David and Thomas are seeing is a manifestation of the "dot-in-PATH" bug. It appears if you have "." before /usr/bin in your PATH environment variable. The problem is the "install" script in the freetype2 source directory. Whereas the Makefile uses the complete pathname "/usr/bin/install" at most places (see the output snippet above), it also sometimes uses simply "install", and if this runs "./install" instead of /usr/bin/install, you get the wrong behavior they observed. The libraries get installed directly into /sw/lib instead of the usual /sw/src/root-freetype2-*/sw/lib directory, and the mv command breaks. -- Martin _______________________________________________ Fink-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-users
