At Thu, 25 Sep 2003 06:00:10 +0300, Andrei Boros wrote: > > Takashi Iwai wrote: > > > > hmm, check whether depcomp file at the top directory is empty. > > if so, try to remove depcomp. > > it must come from automake, but the combination of the old automake > > and the new libtool can be problematic. > > removed an empty depcomp and problem solved. Thanks. > > > > anyway, the best way would be to upgrade (or even downgrade) the all > > GNU auto-tools to the sane combination. i'm not sure which version > > combinations are correct, though. > > > > upgrading them to the latest version would be fine for ALSA, but it > > might not work on others occasionally. sigh. > > I don't know, I just upgraded severla weeks ago the compiler, gnu auto*, > libtool, make to the versions required to compile glibc-2.2.5, so they > are all pretty new.
well... it's not so new nowadays :) on my system: % automake --version automake (GNU automake) 1.7.6 % autoconf --version autoconf (GNU Autoconf) 2.57 % libtool --version ltmain.sh (GNU libtool) 1.5 (1.1220.2.1 2003/04/14 22:48:00) IIRC, at least, the libtool 1.4.x is problematic for creating versioned symbols. (we have workarounds, but not perfect.) Takashi ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
