Re: [Discuss-gnuradio] anyone else having trouble compiling fusb_linux.cc?

[Eric Blossom]

On Thu, Sep 08, 2005 at 11:04:33AM -0700, Larry Doolittle wrote:
> I asked -
> 
> > Something about debian sid broke compilation of fusb_linux.cc
> > badly.  My guess is that something subtle but important changed
> > about the kernel/user header boundary. [chop]
> > I'm researching the problem now, but would appreciate any hints
> > from people who have already seen this.  It works fine in debian
> > sarge.
> 
> I have my code compiling, but it required major surgery.
> I haven't tested its operation yet, but I'm optimistic.
> 
> The libusb folks maintain a libusb/linux.h that parallels
> the kernel-space linux/usbdevice_fs.h, but is designed to
> be used by user-space programs.  So I grabbed a copy of
> that (and called it libusb_linux.h), and #include it instead.
> Then I had to work around differences in name space.  My quick
> hack added a half-dozen #defines to fusb_linux.cc.  A proper
> renaming in fusb_linux.h and fusb_linux.cc would touch 61 lines.
> 
> Complete patch appended.  Comments?
> 
>       - Larry

Which kernel did this stuff blow up on?

Although I'm all for solving the problem, importing an uninstalled
file from libusb into the gnuradio code base that "better" defines the
user/kernel interface seem like a path to future fragility.  Not that
I'm sooo pure that I wouldn't do this to fix the problem ;)

It seems like the right answer is a fix to the kernel header, or
create a supported user-space include that ships with the kernel and
defines the ioctl interface.

Can we make the problem go away by (conditionally) including some
other kernel include file before linux/usbdevice_fs.h? (Yes, I know
it's spreading evil...)

Comments?

Eric