libraw1394 struct layouts, i386 vs. x86_64
Michael ODonnell
michael.odonnell at comcast.net
Wed Jan 7 16:00:52 EST 2009
> I have no clue offhand what's up, but of curiosity, which firewire
> is this? The (really crappy) old ieee1394 stack, or the newer
> firewire stack?
The app in question is a 32bit-compiled app that links with
libraw1394 so I guess that means it's the (really crappy) old
ieee1394 stack. We intend to rebuild it as a 64bit app but that's
not an option at the moment, and we heard good things about the 32bit
compatibility of the x86_64 versions of Linux, so here we are...
> Hrm. I frequent most of the firewire mailing lists out there and
> haven't heard of this either, that I can recall.
Assuming this problem is what I believe it to be (32bit-compiled apps
and libs disagree w/the 64bit-compiled kernel module [raw1394.ko,
the one that implements /dev/raw1394] about the layout of certain
data structures) then it should be easy to reproduce this problem on
RHEL5 or CentOS5 by trying to run any 32bit apps that link against
/usr/lib/libraw1394* - they should choke pretty much immediately
as they can't even complete the initialization phase. There aren't
many but I think Kino is one such app.
--M
More information about the gnhlug-discuss
mailing list