Hi Chris! On Fri, Feb 27, 2015 at 12:11 AM, Chris Bagwell <ch...@cnpbagwell.com> wrote: > Nothing jumps out at me other to to verify you reran autoreconf since I > notice you've shown verbose output and now you have to go out of your way > with 'make V=1' to see that libtool line.
I did go out of my way as I was trying to figure out what's going on. And yes, I have ran "autoreconf -i" before calling "make -j4 V=1 clean all". > lsx_error is referenced by that flac.lo and symbol should be in libsox.la > (from format_i.o) that is listed right after it... so sounds like a badly > generated libsox. Hmm.. I'll have to carefully check again. Trying from a clean git clone on one of my works machine, compilation also fails at the very same place. Are you able to reproduce the error on your end as well? > The only new compiler option I recall is that -fstack-protector but that > should affect symbols references. Nope, that shouldn't be related. -Pascal -- Homepage (http://organact.mine.nu) Debian GNU/Linux (http://www.debian.org) COMunité/LACIME: École de technologie supérieure (http://www.comunite.ca) ISIP Laboratory: McGill (http://www.isip.ece.mcgill.ca) ------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ SoX-devel mailing list SoX-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sox-devel
