From: Brian G. <br...@ge...> - 2006-08-29 18:05:53
|
On Aug 29, 2006, at 9:57 AM, Sean Verret wrote: > Well I think I figured out the boost related errors, so that is > nice. I > had remnants of an older boost still in my include path and apparently > they were being used. So the boost related issues are now all solved. Great. > The wavefront issue in 2.0.1 doesn't present itself in 2.0.2 so I'll > assume it has been fixed, Yep, it was discussed here: http://sourceforge.net/mailarchive/message.php?msg_id=15210516 And fixed prior to 2.0.2. > which leaves only with the 1394 issues that > all versions seem to have, which makes me think it has to do with the > 1394 packages I have installed I would guess that your version of libdc1394 is not supported. There is some logic in Player's configure script to test for at least 3 known libdc1394 APIs; perhaps it's not working correctly. So -- disable-camera1394 is the way to go. If you post your config.log (zip it up first to get in under the 40K limit on this list), we can try to debug that issue. > and the python error in the current CVS > version. This was in building the python bindings to libplayerc, right? My first guess is that you have an old version of SWIG. Try 'swig - version'; you need >= 1.3. In any case, the workaround would be to -- disable-libplayerc-py. brian. |