socketCan build fails
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
Quoted 56 lines · Gabriel Manriquez
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
Quoted 1 line
Any ideas on what could be causing this??
Yes.
Quoted 1 line
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
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
Quoted 80 lines · Oliver Hartkopp
Quoted 56 lines · Gabriel Manriquez
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 2Quoted 1 line
Any ideas on what could be causing this??
Yes.
Quoted 1 line
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.6directory 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.6path?SocketCAN is already included in your Debian Lenny kernel.
Do you need a specific CAN driver?
Regards,
Oliver
Quoted 7 lines · Gabriel Manriquez
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! :-)
Quoted 2 lines
I'm trying to use socketcan in conjuction with can driver :
peak-linux-driver-7.4 which I already installed.
Then you are done.
Quoted 2 lines
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.
Quoted 2 lines
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.
Quoted 1 line
I hope what I'm saying makes sense. Otherwise please ask.
Yes. Everything makes sense.
You're on the right way :-)
Regards,
Oliver
Oliver,
Thank you very much for your help.
I will go ahead and start testing.
-Gabriel
Quoted 35 lines · Oliver Hartkopp
Quoted 7 lines · Gabriel Manriquez
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! :-)
Quoted 2 lines
I'm trying to use socketcan in conjuction with can driver :
peak-linux-driver-7.4 which I already installed.Then you are done.
Quoted 2 lines
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.
Quoted 2 lines
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.
Quoted 1 line
I hope what I'm saying makes sense. Otherwise please ask.
Yes. Everything makes sense.
You're on the right way :-)
Regards,
Oliver
Hi,
Quoted 2 lines
The content of the
kernel/2.6directory 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?
Signature · 3 lines
Mit freundlichen Grüßen / Regards Steffen Rose emtas - your embedded solution partner
Hi Steffen,
Quoted 6 lines · Steffen Rose
Hi,
Quoted 2 lines
The content of the
kernel/2.6directory 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).
Quoted 3 lines
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.
Quoted 3 lines
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.
Quoted 2 lines
Is there a "TAG" in our repository to see, which software state was copied to which kernel version?
No, see above.
Wolfgang.