Jan Stary <h...@stare.cz> writes: > On Aug 24 13:27:00, m...@mansr.com wrote: >> Jan Stary <h...@stare.cz> writes: >> >> >> It all works fine on my VM with this environment and no configure options: >> >> AUTOCONF_VERSION=2.69 >> >> AUTOMAKE_VERSION=1.16 >> >> CC=cc >> >> C_INCLUDE_PATH=/usr/local/include >> >> LIBRARY_PATH=/usr/local/lib >> > >> > I see you have changed the install instructions in the INSTALL file >> > (slapping them onto the Aug 14 commit without mentioning it or >> > reflecting it in the commit message). There is a few problems: >> > >> > 1. >> > On some systems, in particular OpenBSD, the autoreconf insists >> > that 'libtool' is the GNU libtool (of course). So the requirement >> > to have autoconf, automake and autoconf-archive probably needs to >> > be augmented with GNU libtool; otherwise, >> >> Is there any other libtool? > > http://cvsweb.openbsd.org/src/usr.bin/libtool/ > http://man.openbsd.org/libtool > > Relative -L paths are put before absolute ones. > This fixes many (but not all, unfortunately) issues > when software links to libraries already installed > instead of those just built because, for example, > "-L/usr/local/lib" comes before "-L../libfoo". > > That seems to be precisely the problem we are seeing > with the GNU libtool if SoX is already installed.
Why doesn't someone from OpenBSD get it fixed in GNU libtool? -- Måns Rullgård _______________________________________________ SoX-devel mailing list SoX-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sox-devel
