Activity log for bug #285822

Date Who What changed Old value New value Message
2008-10-19 09:48:46 Erik de Castro Lopo bug added bug
2008-10-19 10:04:04 Erik de Castro Lopo description I have been cross compiling libogg from SVN for some time using the MinGW cross compiler tools (mingw, mingw32-binutils and mingw32-runtime packages) and running the test suite under Wine. I have just upgraded from Hardy (where this worked perfectly) to Intrepid. On Intrepid, the whole thing builds but the libtool generated test binaries fail with error code 127. After much investigation I found that the main difference between Hardy and Intrepid was that Hardy uses libtool 1.5.26 and Intrepid uses libtool 2.2.4. On a hunch I downloaded the libtool 2.2.6a sources and installed them. After re-running the autogen.sh script with the new libtool everything worked as it should. I have been cross compiling libogg from SVN for some time using the MinGW cross compiler tools (mingw, mingw32-binutils and mingw32-runtime packages) and running the test suite under Wine. I have just upgraded from Hardy (where this worked perfectly) to Intrepid. On Intrepid, the whole thing builds but the libtool generated test binaries fail with error code 127. After much investigation I found that the main difference between Hardy and Intrepid was that Hardy uses libtool 1.5.26 and Intrepid uses libtool 2.2.4. On a hunch I downloaded the libtool 2.2.6a sources and installed them. After re-running the autogen.sh script with the new libtool everything worked as it should.
2010-04-22 01:15:04 Scott James Remnant (Canonical) libtool (Ubuntu): status New Confirmed
2010-04-22 01:15:07 Scott James Remnant (Canonical) libtool (Ubuntu): importance Undecided Medium
2010-04-22 01:15:24 Scott James Remnant (Canonical) libtool (Ubuntu): status Confirmed Fix Released