* socketCan build fails
@ 2012-02-23 15:02 Gabriel Manriquez
2012-02-23 17:21 ` Oliver Hartkopp
0 siblings, 1 reply; 7+ messages in thread
From: Gabriel Manriquez @ 2012-02-23 15:02 UTC (permalink / raw)
To: linux-can
Hello,
I'm trying to install the socketcan package for the first time. I just
checked out the package today.
I'm following the instructions in the README file but when I issue the
command:
make CC=gcc-4.3
I get errors. See output below:
host:~/socketCan/kernel/2.6# make CC=gcc-4.3
make -C /lib/modules/2.6.35.11/build M=/root/socketCan/kernel/2.6
modules TOPDIR=/root/socketCan/kernel/2.6
make[1]: Entering directory `/usr/src/linux-2.6.35.11'
CC [M] /root/socketCan/kernel/2.6/drivers/net/can/vcan.o
CC [M] /root/socketCan/kernel/2.6/drivers/net/can/slcan.o
CC [M] /root/socketCan/kernel/2.6/drivers/net/can/dev.o
LD [M] /root/socketCan/kernel/2.6/drivers/net/can/can-dev.o
CC [M] /root/socketCan/kernel/2.6/drivers/net/can/esd_pci331.o
CC [M] /root/socketCan/kernel/2.6/drivers/net/can/mcp251x.o
CC [M] /root/socketCan/kernel/2.6/drivers/net/can/cc770/cc770.o
CC [M] /root/socketCan/kernel/2.6/drivers/net/can/cc770/cc770_isa.o
CC [M] /root/socketCan/kernel/2.6/drivers/net/can/sja1000/sja1000.o
CC [M] /root/socketCan/kernel/2.6/drivers/net/can/sja1000/sja1000_isa.o
CC [M]
/root/socketCan/kernel/2.6/drivers/net/can/sja1000/sja1000_platform.o
CC [M] /root/socketCan/kernel/2.6/drivers/net/can/sja1000/ems_pci.o
CC [M] /root/socketCan/kernel/2.6/drivers/net/can/sja1000/ems_104m.o
CC [M] /root/socketCan/kernel/2.6/drivers/net/can/sja1000/esd_pci.o
CC [M] /root/socketCan/kernel/2.6/drivers/net/can/sja1000/ixxat_pci.o
CC [M] /root/socketCan/kernel/2.6/drivers/net/can/sja1000/plx_pci.o
CC [M] /root/socketCan/kernel/2.6/drivers/net/can/sja1000/peak_pci.o
CC [M] /root/socketCan/kernel/2.6/drivers/net/can/sja1000/pipcan.o
CC [M] /root/socketCan/kernel/2.6/drivers/net/can/sja1000/kvaser_pci.o
CC [M] /root/socketCan/kernel/2.6/drivers/net/can/usb/ems_usb.o
/root/socketCan/kernel/2.6/drivers/net/can/usb/ems_usb.c: In function
`ems_usb_write_bulk_callback':
/root/socketCan/kernel/2.6/drivers/net/can/usb/ems_usb.c:525: error:
implicit declaration of function `usb_buffer_free'
/root/socketCan/kernel/2.6/drivers/net/can/usb/ems_usb.c: In function
`ems_usb_start':
/root/socketCan/kernel/2.6/drivers/net/can/usb/ems_usb.c:623: error:
implicit declaration of function `usb_buffer_alloc'
/root/socketCan/kernel/2.6/drivers/net/can/usb/ems_usb.c:624: warning:
assignment makes pointer from integer without a cast
/root/socketCan/kernel/2.6/drivers/net/can/usb/ems_usb.c: In function
`ems_usb_start_xmit':
/root/socketCan/kernel/2.6/drivers/net/can/usb/ems_usb.c:790: warning:
assignment makes pointer from integer without a cast
make[4]: *** [/root/socketCan/kernel/2.6/drivers/net/can/usb/ems_usb.o]
Error 1
make[3]: *** [/root/socketCan/kernel/2.6/drivers/net/can/usb] Error 2
make[2]: *** [/root/socketCan/kernel/2.6/drivers/net/can] Error 2
make[1]: *** [_module_/root/socketCan/kernel/2.6] Error 2
make[1]: Leaving directory `/usr/src/linux-2.6.35.11'
make: *** [modules] Error 2
Any ideas on what could be causing this??
I'm running on Linux (Lenny) kernel version 2.6
Thanks in advance.
-Gabriel
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: socketCan build fails
2012-02-23 15:02 socketCan build fails Gabriel Manriquez
@ 2012-02-23 17:21 ` Oliver Hartkopp
2012-02-23 17:33 ` Gabriel Manriquez
2012-02-27 9:12 ` Steffen Rose
0 siblings, 2 replies; 7+ messages in thread
From: Oliver Hartkopp @ 2012-02-23 17:21 UTC (permalink / raw)
To: Gabriel Manriquez; +Cc: linux-can
On 23.02.2012 16:02, Gabriel Manriquez wrote:
> Hello,
>
> I'm trying to install the socketcan package for the first time. I just
> checked out the package today.
> I'm following the instructions in the README file but when I issue the command:
>
> make CC=gcc-4.3
>
> I get errors. See output below:
>
> host:~/socketCan/kernel/2.6# make CC=gcc-4.3
> make -C /lib/modules/2.6.35.11/build M=/root/socketCan/kernel/2.6 modules
> TOPDIR=/root/socketCan/kernel/2.6
> make[1]: Entering directory `/usr/src/linux-2.6.35.11'
> CC [M] /root/socketCan/kernel/2.6/drivers/net/can/vcan.o
> CC [M] /root/socketCan/kernel/2.6/drivers/net/can/slcan.o
> CC [M] /root/socketCan/kernel/2.6/drivers/net/can/dev.o
> LD [M] /root/socketCan/kernel/2.6/drivers/net/can/can-dev.o
> CC [M] /root/socketCan/kernel/2.6/drivers/net/can/esd_pci331.o
> CC [M] /root/socketCan/kernel/2.6/drivers/net/can/mcp251x.o
> CC [M] /root/socketCan/kernel/2.6/drivers/net/can/cc770/cc770.o
> CC [M] /root/socketCan/kernel/2.6/drivers/net/can/cc770/cc770_isa.o
> CC [M] /root/socketCan/kernel/2.6/drivers/net/can/sja1000/sja1000.o
> CC [M] /root/socketCan/kernel/2.6/drivers/net/can/sja1000/sja1000_isa.o
> CC [M] /root/socketCan/kernel/2.6/drivers/net/can/sja1000/sja1000_platform.o
> CC [M] /root/socketCan/kernel/2.6/drivers/net/can/sja1000/ems_pci.o
> CC [M] /root/socketCan/kernel/2.6/drivers/net/can/sja1000/ems_104m.o
> CC [M] /root/socketCan/kernel/2.6/drivers/net/can/sja1000/esd_pci.o
> CC [M] /root/socketCan/kernel/2.6/drivers/net/can/sja1000/ixxat_pci.o
> CC [M] /root/socketCan/kernel/2.6/drivers/net/can/sja1000/plx_pci.o
> CC [M] /root/socketCan/kernel/2.6/drivers/net/can/sja1000/peak_pci.o
> CC [M] /root/socketCan/kernel/2.6/drivers/net/can/sja1000/pipcan.o
> CC [M] /root/socketCan/kernel/2.6/drivers/net/can/sja1000/kvaser_pci.o
> CC [M] /root/socketCan/kernel/2.6/drivers/net/can/usb/ems_usb.o
> /root/socketCan/kernel/2.6/drivers/net/can/usb/ems_usb.c: In function
> `ems_usb_write_bulk_callback':
> /root/socketCan/kernel/2.6/drivers/net/can/usb/ems_usb.c:525: error: implicit
> declaration of function `usb_buffer_free'
> /root/socketCan/kernel/2.6/drivers/net/can/usb/ems_usb.c: In function
> `ems_usb_start':
> /root/socketCan/kernel/2.6/drivers/net/can/usb/ems_usb.c:623: error: implicit
> declaration of function `usb_buffer_alloc'
> /root/socketCan/kernel/2.6/drivers/net/can/usb/ems_usb.c:624: warning:
> assignment makes pointer from integer without a cast
> /root/socketCan/kernel/2.6/drivers/net/can/usb/ems_usb.c: In function
> `ems_usb_start_xmit':
> /root/socketCan/kernel/2.6/drivers/net/can/usb/ems_usb.c:790: warning:
> assignment makes pointer from integer without a cast
> make[4]: *** [/root/socketCan/kernel/2.6/drivers/net/can/usb/ems_usb.o] Error 1
> make[3]: *** [/root/socketCan/kernel/2.6/drivers/net/can/usb] Error 2
> make[2]: *** [/root/socketCan/kernel/2.6/drivers/net/can] Error 2
> make[1]: *** [_module_/root/socketCan/kernel/2.6] Error 2
> make[1]: Leaving directory `/usr/src/linux-2.6.35.11'
> make: *** [modules] Error 2
>
>
> Any ideas on what could be causing this??
Yes.
> I'm running on Linux (Lenny) kernel version 2.6
I assume that's a 2.6.32 then right?
The content of the kernel/2.6 directory is mainly needed for older Kernels
that do not have SocketCAN support (which was introduced in 2.6.25).
Therefore not all drivers are maintained (e.g. the EMS USB driver is already
in the mainline Kernel).
Why do you need to compile these kernel/2.6 path?
SocketCAN is already included in your Debian Lenny kernel.
Do you need a specific CAN driver?
Regards,
Oliver
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: socketCan build fails
2012-02-23 17:21 ` Oliver Hartkopp
@ 2012-02-23 17:33 ` Gabriel Manriquez
2012-02-23 17:48 ` Oliver Hartkopp
2012-02-27 9:12 ` Steffen Rose
1 sibling, 1 reply; 7+ messages in thread
From: Gabriel Manriquez @ 2012-02-23 17:33 UTC (permalink / raw)
To: Oliver Hartkopp; +Cc: linux-can
Hi Oliver,
I'm running kernel version 2.6.35.11.
I was just following the README file which says to compile
kernel/<version> ... so since you're saying that I don't need to then
can I just go ahead and compile the utilities and test programs?
I'm trying to use socketcan in conjuction with can driver :
peak-linux-driver-7.4 which I already installed.
At this point I just need to test communication to and from my CAN
device via usb and I thought I needed the socketcan utiliites/test
programs to do that.
The peak-linux-driver-7.4 driver comes with receive and transmit test
utilities but they're not suitable for my type of driver install "NETDEV"
I hope what I'm saying makes sense. Otherwise please ask.
Thanks,
-Gabriel
On 2/23/2012 12:21 PM, Oliver Hartkopp wrote:
> On 23.02.2012 16:02, Gabriel Manriquez wrote:
>
>> Hello,
>>
>> I'm trying to install the socketcan package for the first time. I just
>> checked out the package today.
>> I'm following the instructions in the README file but when I issue the command:
>>
>> make CC=gcc-4.3
>>
>> I get errors. See output below:
>>
>> host:~/socketCan/kernel/2.6# make CC=gcc-4.3
>> make -C /lib/modules/2.6.35.11/build M=/root/socketCan/kernel/2.6 modules
>> TOPDIR=/root/socketCan/kernel/2.6
>> make[1]: Entering directory `/usr/src/linux-2.6.35.11'
>> CC [M] /root/socketCan/kernel/2.6/drivers/net/can/vcan.o
>> CC [M] /root/socketCan/kernel/2.6/drivers/net/can/slcan.o
>> CC [M] /root/socketCan/kernel/2.6/drivers/net/can/dev.o
>> LD [M] /root/socketCan/kernel/2.6/drivers/net/can/can-dev.o
>> CC [M] /root/socketCan/kernel/2.6/drivers/net/can/esd_pci331.o
>> CC [M] /root/socketCan/kernel/2.6/drivers/net/can/mcp251x.o
>> CC [M] /root/socketCan/kernel/2.6/drivers/net/can/cc770/cc770.o
>> CC [M] /root/socketCan/kernel/2.6/drivers/net/can/cc770/cc770_isa.o
>> CC [M] /root/socketCan/kernel/2.6/drivers/net/can/sja1000/sja1000.o
>> CC [M] /root/socketCan/kernel/2.6/drivers/net/can/sja1000/sja1000_isa.o
>> CC [M] /root/socketCan/kernel/2.6/drivers/net/can/sja1000/sja1000_platform.o
>> CC [M] /root/socketCan/kernel/2.6/drivers/net/can/sja1000/ems_pci.o
>> CC [M] /root/socketCan/kernel/2.6/drivers/net/can/sja1000/ems_104m.o
>> CC [M] /root/socketCan/kernel/2.6/drivers/net/can/sja1000/esd_pci.o
>> CC [M] /root/socketCan/kernel/2.6/drivers/net/can/sja1000/ixxat_pci.o
>> CC [M] /root/socketCan/kernel/2.6/drivers/net/can/sja1000/plx_pci.o
>> CC [M] /root/socketCan/kernel/2.6/drivers/net/can/sja1000/peak_pci.o
>> CC [M] /root/socketCan/kernel/2.6/drivers/net/can/sja1000/pipcan.o
>> CC [M] /root/socketCan/kernel/2.6/drivers/net/can/sja1000/kvaser_pci.o
>> CC [M] /root/socketCan/kernel/2.6/drivers/net/can/usb/ems_usb.o
>> /root/socketCan/kernel/2.6/drivers/net/can/usb/ems_usb.c: In function
>> `ems_usb_write_bulk_callback':
>> /root/socketCan/kernel/2.6/drivers/net/can/usb/ems_usb.c:525: error: implicit
>> declaration of function `usb_buffer_free'
>> /root/socketCan/kernel/2.6/drivers/net/can/usb/ems_usb.c: In function
>> `ems_usb_start':
>> /root/socketCan/kernel/2.6/drivers/net/can/usb/ems_usb.c:623: error: implicit
>> declaration of function `usb_buffer_alloc'
>> /root/socketCan/kernel/2.6/drivers/net/can/usb/ems_usb.c:624: warning:
>> assignment makes pointer from integer without a cast
>> /root/socketCan/kernel/2.6/drivers/net/can/usb/ems_usb.c: In function
>> `ems_usb_start_xmit':
>> /root/socketCan/kernel/2.6/drivers/net/can/usb/ems_usb.c:790: warning:
>> assignment makes pointer from integer without a cast
>> make[4]: *** [/root/socketCan/kernel/2.6/drivers/net/can/usb/ems_usb.o] Error 1
>> make[3]: *** [/root/socketCan/kernel/2.6/drivers/net/can/usb] Error 2
>> make[2]: *** [/root/socketCan/kernel/2.6/drivers/net/can] Error 2
>> make[1]: *** [_module_/root/socketCan/kernel/2.6] Error 2
>> make[1]: Leaving directory `/usr/src/linux-2.6.35.11'
>> make: *** [modules] Error 2
>>
>>
>> Any ideas on what could be causing this??
>
> Yes.
>
>> I'm running on Linux (Lenny) kernel version 2.6
>
> I assume that's a 2.6.32 then right?
>
> The content of the kernel/2.6 directory is mainly needed for older Kernels
> that do not have SocketCAN support (which was introduced in 2.6.25).
>
> Therefore not all drivers are maintained (e.g. the EMS USB driver is already
> in the mainline Kernel).
>
> Why do you need to compile these kernel/2.6 path?
>
> SocketCAN is already included in your Debian Lenny kernel.
>
> Do you need a specific CAN driver?
>
> Regards,
> Oliver
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: socketCan build fails
2012-02-23 17:33 ` Gabriel Manriquez
@ 2012-02-23 17:48 ` Oliver Hartkopp
2012-02-24 13:46 ` Gabriel Manriquez
0 siblings, 1 reply; 7+ messages in thread
From: Oliver Hartkopp @ 2012-02-23 17:48 UTC (permalink / raw)
To: Gabriel Manriquez; +Cc: linux-can
On 23.02.2012 18:33, Gabriel Manriquez wrote:
> Hi Oliver,
>
> I'm running kernel version 2.6.35.11.
>
> I was just following the README file which says to compile kernel/<version>
> ... so since you're saying that I don't need to then can I just go ahead and
> compile the utilities and test programs?
Yep! :-)
> I'm trying to use socketcan in conjuction with can driver :
> peak-linux-driver-7.4 which I already installed.
Then you are done.
> At this point I just need to test communication to and from my CAN device via
> usb and I thought I needed the socketcan utiliites/test programs to do that.
Yes - using the can-utils is the easiest way to start with SocketCAN.
> The peak-linux-driver-7.4 driver comes with receive and transmit test
> utilities but they're not suitable for my type of driver install "NETDEV"
That's right.
> I hope what I'm saying makes sense. Otherwise please ask.
Yes. Everything makes sense.
You're on the right way :-)
Regards,
Oliver
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: socketCan build fails
2012-02-23 17:48 ` Oliver Hartkopp
@ 2012-02-24 13:46 ` Gabriel Manriquez
0 siblings, 0 replies; 7+ messages in thread
From: Gabriel Manriquez @ 2012-02-24 13:46 UTC (permalink / raw)
To: Oliver Hartkopp; +Cc: linux-can
Oliver,
Thank you very much for your help.
I will go ahead and start testing.
-Gabriel
On 2/23/2012 12:48 PM, Oliver Hartkopp wrote:
> On 23.02.2012 18:33, Gabriel Manriquez wrote:
>
>> Hi Oliver,
>>
>> I'm running kernel version 2.6.35.11.
>>
>> I was just following the README file which says to compile kernel/<version>
>> ... so since you're saying that I don't need to then can I just go ahead and
>> compile the utilities and test programs?
>
> Yep! :-)
>
>> I'm trying to use socketcan in conjuction with can driver :
>> peak-linux-driver-7.4 which I already installed.
>
> Then you are done.
>
>> At this point I just need to test communication to and from my CAN device via
>> usb and I thought I needed the socketcan utiliites/test programs to do that.
>
> Yes - using the can-utils is the easiest way to start with SocketCAN.
>
>> The peak-linux-driver-7.4 driver comes with receive and transmit test
>> utilities but they're not suitable for my type of driver install "NETDEV"
>
> That's right.
>
>> I hope what I'm saying makes sense. Otherwise please ask.
>
> Yes. Everything makes sense.
>
> You're on the right way :-)
>
> Regards,
> Oliver
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: socketCan build fails
2012-02-23 17:21 ` Oliver Hartkopp
2012-02-23 17:33 ` Gabriel Manriquez
@ 2012-02-27 9:12 ` Steffen Rose
2012-02-27 9:32 ` Wolfgang Grandegger
1 sibling, 1 reply; 7+ messages in thread
From: Steffen Rose @ 2012-02-27 9:12 UTC (permalink / raw)
To: linux-can; +Cc: Oliver Hartkopp, Gabriel Manriquez
Hi,
> The content of the kernel/2.6 directory is mainly needed for older Kernels
> that do not have SocketCAN support (which was introduced in 2.6.25).
differ the kernel socketCAN path from our used socketCAN?
Of course, I know, this both are different repositories. But I was the meaning,
that at the first the changes comes in our repository and later our patches are
copied to the kernel.
Additional question:
Are there a Kernel list with information, which socketCAN feature is included
(e.g. 3.2 - gateway functionality)?
Is there a "TAG" in our repository to see, which software state was copied to
which kernel version?
--
Mit freundlichen Grüßen / Regards
Steffen Rose
emtas - your embedded solution partner
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: socketCan build fails
2012-02-27 9:12 ` Steffen Rose
@ 2012-02-27 9:32 ` Wolfgang Grandegger
0 siblings, 0 replies; 7+ messages in thread
From: Wolfgang Grandegger @ 2012-02-27 9:32 UTC (permalink / raw)
To: Steffen Rose; +Cc: linux-can, Oliver Hartkopp, Gabriel Manriquez
Hi Steffen,
On 02/27/2012 10:12 AM, Steffen Rose wrote:
> Hi,
>
>> The content of the kernel/2.6 directory is mainly needed for older Kernels
>> that do not have SocketCAN support (which was introduced in 2.6.25).
>
> differ the kernel socketCAN path from our used socketCAN?
Yes, if "our used socketCAN" means the out-of-tree "SocketCAN
repository" (formerly at BerliOS and now at gitorious.rog).
> Of course, I know, this both are different repositories. But I was the meaning,
> that at the first the changes comes in our repository and later our patches are
> copied to the kernel.
Unfortunately, that's not the case. The main focus is on providing
support for the mainline kernel. The intention is that patches/fixes are
backported from the kernel tree but also that did not always happen.
Both trees are not in full sync, sorry.
> Additional question:
> Are there a Kernel list with information, which socketCAN feature is included
> (e.g. 3.2 - gateway functionality)?
"$ git log drivers/net/can" should provide that information.
> Is there a "TAG" in our repository to see, which software state was copied to
> which kernel version?
No, see above.
Wolfgang.
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2012-02-27 9:32 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-02-23 15:02 socketCan build fails Gabriel Manriquez
2012-02-23 17:21 ` Oliver Hartkopp
2012-02-23 17:33 ` Gabriel Manriquez
2012-02-23 17:48 ` Oliver Hartkopp
2012-02-24 13:46 ` Gabriel Manriquez
2012-02-27 9:12 ` Steffen Rose
2012-02-27 9:32 ` Wolfgang Grandegger
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).