From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kurt Van Dijck Subject: Re: iproute2-j1939 Date: Fri, 9 Dec 2011 10:48:56 +0100 Message-ID: <20111209094856.GC325@e-circ.dyndns.org> References: <20111207145032.GE373@e-circ.dyndns.org> <20111208123004.GA964@e-circ.dyndns.org> <20111208133213.GB964@e-circ.dyndns.org> <20111208151917.GE964@e-circ.dyndns.org> <20111209080726.GA325@e-circ.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Return-path: Received: from gate.eia.be ([194.78.71.18]:34161 "EHLO mail.eia.be" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752944Ab1LIJtH (ORCPT ); Fri, 9 Dec 2011 04:49:07 -0500 Content-Disposition: inline In-Reply-To: Sender: linux-can-owner@vger.kernel.org List-ID: To: Wolfgang Cc: linux-can@vger.kernel.org On Fri, Dec 09, 2011 at 09:02:53AM +0000, Wolfgang wrote: > > can.h got updated (struct can_addr extended), but I'm not sure > > exactly which paths must be updated. > > OK, so do you think I have to replace the existing can.h with the can.h from > can-j1939-modules? Yes, I think so. > > Or is it possible that the af_can.h (found in can-j1939-modules/net/can) > has to be included in the utils.c file (utils.c:518: error: 'AF_CAN'\ > undeclared (first use in this function), it's just an idea? No, you don't need CAN. the macro AF_CAN for userspace applications is in bits/socket.h (of the toolchain), included by sys/socket.h. If AF_CAN is unknown, even when "#include ", you need to modify bits/socket.h IMO. "#include " would work, but feels a bit dirty. You can safely add "#define AF_CAN 29" and "#define AF_CAN PF_CAN" in "sys/socket.h" Kurt