On Sat, 9 Dec 2006, Stan Gammons wrote:
> What all tools in mjpegtools use lav_file_t ? Just lavtools?
That would seem to be the case.
find . -name '*.c' | xargs grep lav_file_t
only shows files in lavtools/
> using the old way. What effect will it have if the other tools compiled
> Ok with GCC 4.1.1?
SHould work OK. AND you can, if you want, simply change that
one structure member back to 'void *'. Nothing'll break and
it will show up as 'M' when you do a cvs update later but that just
means the file's been modified locally.
> Wonder what they changed/broke from 4.1.0 to 4.1.1 that causing the error?
No idea.
FC6 didn't ship with an older libquicktime that might be conflicing
some how, did it?
> I'm still staying away from the 64 bit stuff. Too much of a pain in the
> rear getting everything from the 32 bit world to work on 64 bit.
Really? It "all just worked" for me - no trouble at all for the
last couple years on the dual Opteron system. Ine or two
minor shared library build issues with programs but that's all.
> IF you mess with the 64 bit version of FC6, I'd like to know if you get
> the same or similar compile error.
I'm backing up a couple files off the FC4 disc and get the
base FC6 installed tonight. Not sure how much more will get done
this weekend.
Steven Schultz
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Mjpeg-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mjpeg-users
