Vorbis dev - Oct 2004 - Vorbis with SDL_mixer and mingw32

Hi,
  I've been trying to build a copy of libSDL_mixer under mingw32. The
compile/link stage goes OK, but if I try and load an application that's been
linked against SDL_mixer, I get a Windows error box with the following text:

mixer1.exe: entry point not found
The procedure entry point vorbis_synthesis_halfrate could not be located in
the dynamic link library vorbis.dll.

  Are the .lib files in the Vorbis SDK (v1.0.1) suitable for linking with
mingw? The libvorbisfile samples seem to work, but for some reason SDL_mixer
insists there's a missing entrypoint.

  Also, does anyone know what the difference between the "normal"
library
files (e.g. libogg.lib/dll) and the library files with the "_d" suffix
(e.g.
libogg_d.lib/dll) is?

Thanks.
-- 
Phil.                              | Acorn Risc PC600 Mk3, SA202, 64MB, 6GB,
philpem@philpem.me.uk              | ViewFinder, 10BaseT Ethernet, 2-slice,
http://www.philpem.me.uk/          | 48xCD, ARCINv6c IDE, SCSI
... I'm writing a book. I've got the page numbers done.

Philip Pemberton wrote:
>Hi,
>  I've been trying to build a copy of libSDL_mixer under mingw32. The
>compile/link stage goes OK, but if I try and load an application that's
been
>linked against SDL_mixer, I get a Windows error box with the following text:
>
>mixer1.exe: entry point not found
>The procedure entry point vorbis_synthesis_halfrate could not be located in
>the dynamic link library vorbis.dll.
>  
>
Sounds to me like the dll you have has been compiled without that entry 
poiont - it should be there.
>  Are the .lib files in the Vorbis SDK (v1.0.1) suitable for linking with
>mingw? The libvorbisfile samples seem to work, but for some reason SDL_mixer
>insists there's a missing entrypoint.
>
>  Also, does anyone know what the difference between the "normal"
library
>files (e.g. libogg.lib/dll) and the library files with the "_d"
suffix (e.g.
>libogg_d.lib/dll) is?
>
>Thanks.
>  
>
The libs with the "_d" suffix are the debug libs.

John