The changes introduced in June to deal with "canopy" being picked up
by CANusb interface, introduced a problem:
./pcap-canusb-linux.c:260:20: error: 'struct canusb_t' has no member named 'src'
make: *** [pcap-canusb-linux.o] Error 1
this occurs on a debian testing desktop system, x86_64.
I ran
On Mon, Sep 03, 2012 at 02:34:02PM -0400, Michael Richardson wrote:
> The changes introduced in June to deal with "canopy" being picked up
> by CANusb interface, introduced a problem:
>
> ./pcap-canusb-linux.c:260:20: error: 'struct canusb_t' has no member named
> 'src'
> make: *** [pcap-canusb-l
> "Jakub" == Jakub Zawadzki writes:
Jakub> On Mon, Sep 03, 2012 at 02:34:02PM -0400, Michael Richardson
Jakub> wrote:
>> The changes introduced in June to deal with "canopy" being picked
>> up by CANusb interface, introduced a problem:
>>
>> ./pcap-canusb-linux.c:260:
On Sep 3, 2012, at 2:35 PM, Michael Richardson wrote:
> okay, so as I understand it, basically you have keeping the name that
> was in the library in a structure in lib cap.
No, the name was never in a library; "struct canusb_t" is a structure in the
pcap-canusb-linux.c module. The field was r
Wesley, is fopen("/dev/stdin") really the most portal way to
get a reference to stdin? I'd have thought that doing:
VFile=stdin;
was the best way?
Other than that, I think your patch is the best way to implement
this I'd like if we could also handle multiple -r files in
exactly the same
