Michael Riepe wrote: > Hi! > > David Coe wrote: >> Michael Riepe wrote: >> >>> Hi 'cutters, >>> >>> David Coe wrote: >>> >>>> Hi list! >>>> >>>> Every so often I compile up dvbcut under Windows MinGW rather than rely >>>> on Ralph Glastetter's builds. Recently (somewhere after r154 I think) my >>>> compilation has failed with a missing "C:/MingW/include/stdlib.h". >>>> >>>> This has been hard-wired into dvbcut's version in /import/stdlib.h and >>>> will only suit the writer's own MinGW installation. Might it be better >>>> to have this as "/mingw/include/stdlib.h"? This is, at least, is the >>>> canonical location for the mingw compiler suite. >>> actually, there's a better fix: use gcc's #include_next feature. That >>> will load MinGW's version of the file no matter where it is installed. >>> The gcc dependency shouldn't be a problem because we're not using any >>> other compiler on Windows anyway. >>> >>> Welcome to r162, >> >> Nope .. that doesn't work :-(. I'm getting bombs on undeclared 'malloc' >> and 'free', which means the system stdlib.h isn't being picked up. > > Did you perhaps run "./configure; make"? I'm afraid that doesn't work > because ffmpeg isn't configured correctly this way. Please use the > mingw.sh script, as explained in README.MingGW, or cd into the src > directory and run "make -f Makefile.w32" manually.
Either build method behaves identically with respect to picking up stdlib.h (or not). Both produce working binaries (at least to my untutored eye) but I take on board about the incorrect ffmpeg configuration. I'd better take a closer look at some of the 20 or 30 DVDs made over the past few months :-(. >> As I understand it, #include_next traverses down the include directory >> list looking for the named file. For dvbcut this is: >> >> -I../import -I/usr/local/include -I/home/david/dvbcut/ffmpeg/include >> -I/home/david/dvbcut/ffmpeg/include/ffmpeg -I/usr/local/qt3/include -I. >> >> so it would only work if the (idiosyncratic) /mingw/include were added >> to make's include list. > > Actually, the list is longer. It contains the compiler's default > directories at the end (which should include /mingw/include in this > case). If it doesn't, the compiler is broken (or maybe not installed > correctly). The toolchain installation is the MinGW/MSYS default (apart from being on G: rather than C:) and has survived (inter alia) building the qt3, mad, a52 and mpeg2 dependencies. Hopefully, therefore, there is nothing fundamentally wrong. Maybe, however, it is broken as far as #include_next is concerned. Is there any chance you might check this out on your MinGW, Ralph? I'm not sure if you compile natively or on a linux cross-compiler. Many thanks one and all. -- David ------------------------------------------------------------------------------ _______________________________________________ DVBCUT-user mailing list DVBCUT-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dvbcut-user
