error: `WEOF' undeclared

Questions that occur when trying to compile FFmpeg.
thatshowifeel
Posts: 4
Joined: Mon Oct 29, 2012 4:36 pm

error: `WEOF' undeclared

Post by thatshowifeel »

So I'm trying to use "make" to build the make file, but I'm getting a huge list of errors:

Code: Select all

$ make
CC      libavdevice/alldevices.o
CC      libavdevice/avdevice.o
CC      libavdevice/dshow.o
In file included from /usr/lib/gcc/i686-pc-cygwin/3.4.4/../../../../include/w32a   pi/dshow.h:33,
                 from libavdevice/dshow_capture.h:31,
                 from libavdevice/dshow.c:27:
/usr/lib/gcc/i686-pc-cygwin/3.4.4/../../../../include/w32api/strsafe.h: In funct   ion `StringGetsExWorkerW':
/usr/lib/gcc/i686-pc-cygwin/3.4.4/../../../../include/w32api/strsafe.h:1851: err   or: `WEOF' undeclared (first use in this function)
/usr/lib/gcc/i686-pc-cygwin/3.4.4/../../../../include/w32api/strsafe.h:1851: err   or: (Each undeclared identifier is reported only once
/usr/lib/gcc/i686-pc-cygwin/3.4.4/../../../../include/w32api/strsafe.h:1851: err   or: for each function it appears in.)
libavdevice/dshow.c: In function `dshow_cycle_devices':
libavdevice/dshow.c:285: error: structure has no member named `vt'
libavdevice/dshow.c:290: error: structure has no member named `bstrVal'
libavdevice/dshow.c: In function `dshow_cycle_formats':
libavdevice/dshow.c:341: warning: dereferencing type-punned pointer will break s   trict-aliasing rules
libavdevice/dshow.c: In function `dshow_set_audio_buffer_size':
libavdevice/dshow.c:486: warning: dereferencing type-punned pointer will break s   trict-aliasing rules
libavdevice/dshow.c:496: warning: dereferencing type-punned pointer will break s   trict-aliasing rules
libavdevice/dshow.c: In function `dshow_cycle_pins':
libavdevice/dshow.c:566: warning: dereferencing type-punned pointer will break s   trict-aliasing rules
libavdevice/dshow.c: In function `dshow_read_header':
libavdevice/dshow.c:900: warning: dereferencing type-punned pointer will break s   trict-aliasing rules
libavdevice/dshow.c:908: warning: dereferencing type-punned pointer will break s   trict-aliasing rules
libavdevice/dshow.c:959: warning: dereferencing type-punned pointer will break s   trict-aliasing rules
common.mak:48: recipe for target `libavdevice/dshow.o' failed
make: *** [libavdevice/dshow.o] Error 1

I'm pretty new to the whole compiling software scene, but I couldn't find anything from a google search. Help?

rogerdpack
Posts: 1882
Joined: Fri Aug 05, 2011 9:56 pm

Re: error: `WEOF' undeclared

Post by rogerdpack »

what compiler are you using?
recommend mingw-w64...
or cross compile (https://github.com/rdp/ffmpeg-windows-build-helpers would be useful if you went that route).

thatshowifeel
Posts: 4
Joined: Mon Oct 29, 2012 4:36 pm

Re: error: `WEOF' undeclared

Post by thatshowifeel »

I'm using cygwin and now when I'm trying to install mingGW I get these errors:

Code: Select all

make[2]: *** [add_n.lo] Error 1
make[2]: *** Waiting for unfinished jobs....
 gcc -std=gnu99 -c -DHAVE_CONFIG_H -I. -I../../source/gmp-5.0.5/mpn -I.. -D__GMP_WITHIN_GMP -I../../source/gmp-5.0.5 -DOPERATION_sub_n -fexceptions -m32 -O2 -pedantic -fomit-frame-pointer -mtune=pentiumpro -march=pentiumpro tmp-sub_n.s -o sub_n.o
tmp-sub_n.s: Assembler messages:
tmp-sub_n.s: Warning: end of file not at end of a line; newline inserted
tmp-sub_n.s:1: Error: junk at end of line, first unrecognized character is `!'
Makefile:1023: recipe for target `sub_n.lo' failed
make[2]: *** [sub_n.lo] Error 1
libtool: compile:  gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I../../source/gmp-5.0.5/mpn -I.. -D__GMP_WITHIN_GMP -I../../source/gmp-5.0.5 -DOPERATION_neg -fexceptions -m32 -O2 -pedantic -fomit-frame-pointer -mtune=pentiumpro -march=pentiumpro -c neg.c -o neg.o
libtool: compile:  gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I../../source/gmp-5.0.5/mpn -I.. -D__GMP_WITHIN_GMP -I../../source/gmp-5.0.5 -DOPERATION_com -fexceptions -m32 -O2 -pedantic -fomit-frame-pointer -mtune=pentiumpro -march=pentiumpro -c com.c -o com.o
make[2]: Leaving directory `/cygdrive/c/Users/Jared/builder/sandbox/packages/gcc/packages/gmp/build/mpn'
Makefile:924: recipe for target `all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/cygdrive/c/Users/Jared/builder/sandbox/packages/gcc/packages/gmp/build'
Makefile:659: recipe for target `all' failed
make: *** [all] Error 2

rogerdpack
Posts: 1882
Joined: Fri Aug 05, 2011 9:56 pm

Re: error: `WEOF' undeclared

Post by rogerdpack »

you're trying to install mingw using cygwin? mingw should have its own downloads available...

anyway this might help:
http://stackoverflow.com/questions/4711 ... it-windows
and recommend mingw-w64 or mingw-w64 cross compile.
-roger-

thatshowifeel
Posts: 4
Joined: Mon Oct 29, 2012 4:36 pm

Re: error: `WEOF' undeclared

Post by thatshowifeel »

I'm on a 64 bit machine. Will cross compile only build on 32 bit machines?

rogerdpack
Posts: 1882
Joined: Fri Aug 05, 2011 9:56 pm

Re: error: `WEOF' undeclared

Post by rogerdpack »

if you're on windows, you'll need a linux VM. And it can be either 32 or 64 bit. With a cross compiler basically you either build a "32 bit windows cross compiler" or a "64 bit windows cross compiler" but both of them can live/run in a 32 bit VM. HTH.

thatshowifeel
Posts: 4
Joined: Mon Oct 29, 2012 4:36 pm

Re: error: `WEOF' undeclared

Post by thatshowifeel »

Well dang. The whole point of this adventure was to figure out how to do it on a Windows machine, but I suppose I can live with this.

rogerdpack
Posts: 1882
Joined: Fri Aug 05, 2011 9:56 pm

Re: error: `WEOF' undeclared

Post by rogerdpack »

there is mingw-w64 for windows too

ramiro
Posts: 157
Joined: Tue May 10, 2011 12:56 am

Re: error: `WEOF' undeclared

Post by ramiro »

it can be done on windows using msys. it's just not worth it. it's faster to install a linux vm and cross-compile

riemann
Posts: 1
Joined: Sat Dec 08, 2012 3:32 am

Re: error: `WEOF' undeclared

Post by riemann »

Dear thatshowifeel, i account the same problem as you (error: `WEOF' undeclare), can you help me to fix the problem? Thank you in advance.
thatshowifeel wrote:Well dang. The whole point of this adventure was to figure out how to do it on a Windows machine, but I suppose I can live with this.

Post Reply