test programs created incorrectly when cross compiling using MinGW

Bug #285822 reported by Erik de Castro Lopo
2
Affects Status Importance Assigned to Milestone
libtool (Ubuntu)
Fix Released
Medium
Unassigned

Bug 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.

Tags: libtool mingw
description: updated
Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote :

Marking fixed since 2.2.6b is in lucid

Changed in libtool (Ubuntu):
status: New → Confirmed
importance: Undecided → Medium
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.