Hi!
David Coe wrote:
I'd like though to establish whether #include_next works in your own
build environment.
Well, if you refuse to believe me...
$ cd dvbcut
$ echo '#include stdlib.h' | gcc -E -
# 1 stdin
# 1 built-in
# 1 command line
# 1 stdin
# 1
Am Montag, 29. Juni 2009 schrieb Michael Riepe:
[...]
I could try again if it works now with this #include_next ... guess
anyhow it's time to bild a new binary with this help stuff included...
;-)
Save yourself the trouble and stick to mingw.sh, please.
OK, you convinced me... ;-)
Just
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
Hi!
David Coe wrote:
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
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
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
