Thanks again, Elvis. I appreciate the input.

On a side note, I realized something.. that when you use externs , you should not be saying how big the array is, just use extern struct *name  and not somethign like Extern struct name[size];  I changed those lines where this was happening and hte compilation goes further. and not breaks in util.c

so I will have to dig through this and fix these issues. Hoepfully will have ffmpeg building in a few hours.  I'll try and push the changes back up into the source tree then.

Thanks for the help!
RIck


On Tue, Aug 11, 2009 at 11:41 AM, richard dorfner <rdorfner@gmail.com> wrote:


On Tue, Aug 11, 2009 at 11:30 AM, Elvis Dowson <elvis.dowson@mac.com> wrote:
Hi,

On Aug 11, 2009, at 7:20 PM, richard dorfner wrote:

NOTE: Running task 791 of 875 (ID: 102, /home/rickd/gumstix/gumstix-oe/org.openembedded.snapshot/packages/ffmpeg/ffmpeg_0.4.9-pre1.bb, do_compile)
NOTE: package ffmpeg-0.4.9-pre1: started
NOTE: package ffmpeg-0.4.9-pre1-r1: task do_compile: started
ERROR: function do_compile failed

It would appear that ffmpeg_0.4.9-pre1.bb is failing, due to a compilation error. 
Yup yup!  
ERROR: log data follows (/home/rickd/gumstix/gumstix-oe/tmp/work/armv5te-angstrom-linux-gnueabi/ffmpeg-0.4.9-pre1-r1/temp/log.do_compile.11066)

Could you open the log and send it across to me? 
Sure thing! Here you go.  Though it's not extraordinarily helpful, it mostly seems to say teh same thing as the previous synopsis, but with most information for the flags being used.
 
rickd@ZombyPony:~/gumstix/gumstix-oe/tmp/work/armv5te-angstrom-linux-gnueabi/ffmpeg-0.4.9-pre1-r1/temp$ more log.do_compile.11066

NOTE: make
make -C libavcodec all
make[1]: Entering directory `/home/rickd/gumstix/gumstix-oe/tmp/work/armv5te-ang
strom-linux-gnueabi/ffmpeg-0.4.9-pre1-r1/ffmpeg-0.4.9-pre1/libavcodec'
arm-angstrom-linux-gnueabi-gcc -march=armv5te -mtune=xscale -O3 -Wall -isystem/h
ome/rickd/gumstix/gumstix-oe/tmp/staging/arm-angstrom-linux-gnueabi/include -fex
pensive-optimizations -fomit-frame-pointer -frename-registers -Os -DHAVE_AV_CONF
IG_H -I.. -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_GNU_SOURCE -fPIC -DPIC -
c -o common.o common.c
In file included from avcodec.h:15,
                 from common.c:28:
common.h:69: error: array type has incomplete element type
common.h:71: error: array type has incomplete element type
make[1]: *** [common.o] Error 1
make[1]: Leaving directory `/home/rickd/gumstix/gumstix-oe/tmp/work/armv5te-angs

trom-linux-gnueabi/ffmpeg-0.4.9-pre1-r1/ffmpeg-0.4.9-pre1/libavcodec'
make: *** [lib] Error 2
FATAL: oe_runmake failed
rickd@ZombyPony:~/gumstix/gumstix-oe/tmp/work/armv5te-angstrom-linux-gnueabi/ffmpeg-0.4.9-pre1-r1/temp$

 

| NOTE: make
| make -C libavcodec all
| make[1]: Entering directory `/home/rickd/gumstix/gumstix-oe/tmp/work/armv5te-angstrom-linux-gnueabi/ffmpeg-0.4.9-pre1-r1/ffmpeg-0.4.9-pre1/libavcodec'
| arm-angstrom-linux-gnueabi-gcc -march=armv5te -mtune=xscale -O3 -Wall -isystem/home/rickd/gumstix/gumstix-oe/tmp/staging/arm-angstrom-linux-gnueabi/include -fexpensive-optimizations -fomit-frame-pointer -frename-registers -Os -DHAVE_AV_CONFIG_H -I.. -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_GNU_SOURCE -fPIC -DPIC -c -o common.o common.c
| In file included from avcodec.h:15,
|                  from common.c:28:
| common.h:69: error: array type has incomplete element type
| common.h:71: error: array type has incomplete element type

What you now need to do is to open common.h, and find out if some definitions are missing, and if you need to include some header files, or the paths to the header files have to be modified, or if the name of the original header files mentioned in common.h have changed.


What you now need to do is to run the following command:

bitbake -c clean ffmpeg-0.4.9-pre1
bitbake -i rebuild ffmpeg-0.4.9-pre1 -DD

the -i starts bitbake in interactive mode. Then -DD option enables detailed debugging. 

Best regards,

Elvis
Very good! I'll start on that path. Thank you!  I guess it's a bit odd to me, in that it seems like a lot of folks have already built vlc for the gumstix board, yes? and given the common use off  web cams with it and other attempts at streaming video from it, that vlc, ffmpeg and other such tools would already have been created and made to run with it.  At any rate, I guess this is where I get to dig in and perhaps contribute to the OE development. YAY!

Thanks for the input Elvis, muchly appreciated.

Rick
 



--
Say you can or say you can't, either way you will be right.
Computers are like old testament gods: Lots of rules and no mercy.



--
Say you can or say you can't, either way you will be right.
Computers are like old testament gods: Lots of rules and no mercy.