On Mar 2, 2014, at 8:48 PM, Werner LEMBERG <w...@gnu.org> wrote: > > Some weeks ago I wrote: > >> I've now found out that it *is* a libtool problem: >> >>> libtool: link: \ >>> (cd >>> /Users/wl/harfbuzz-0.9.26/src/.libs/libharfbuzz.lax/libhb-ucdn.a/unfat-91266/libhb-ucdn.a-i386 >>> \ >>> && ar x "libhb-ucdn.a") >>> libtool: link: \ >>> (cd >>> /Users/wl/harfbuzz-0.9.26/src/.libs/libharfbuzz.lax/libhb-ucdn.a/unfat-91266/libhb-ucdn.a-x86_64 >>> \ >>> && ar x "libhb-ucdn.a") >>> find: warning: \ >>> Unix filenames usually don't contain slashes (though pathnames do). \ >>> That means that '-name `unfat-91266/libhb-ucdn.a-i386/ucdn.o'' \ >>> will probably evaluate to false all the time on this system. ... >> >> This warning message caused by this line in `libtool', in function >> `func_extract_archives': >> >> darwin_files=`find unfat-$$ -name $darwin_file -print | sort | $NL2SP` >> >> It searches for file names in the directory `unfat-$$'. However, if >> the value of `foo_LIBADD' contains a subdirectory, as in >> >> libharfbuzz_la_LIBADD = hb-ucdn/libhb-ucdn.la >> >> this fails, since `$darwin_file' now contains something with slashes. > > Is there anyone on the list who could confirm the analysis, or > probably even fix it in libtool in case the analysis is correct?
I think your analysis is probably correct. If you have a patch that’d be awesome. Peter > > > Werner > > _______________________________________________ > https://lists.gnu.org/mailman/listinfo/libtool _______________________________________________ https://lists.gnu.org/mailman/listinfo/libtool
