building driver with non-xilinx compiler fails

Description

when trying to build the dataplane driver for zynq with the arm-none-linux-gnueabi compiler we get the following error:

[embedded@localhost opencpi]$ make driver
make -C adapt/os/ocpios/linux/driver
OCPI_KERNEL_DIR was specified, we are now using: KERNELDIR=/home/embedded/ocpi/opencpi/platforms/zed/release/kernel-headers ARCH=arm CROSS_COMPILE=/opt/CodeSourcery/Sourcery_G++_Lite/bin/arm-none-linux-gnueabi-
make[1]: Entering directory `/home/embedded/ocpi/opencpi/adapt/os/ocpios/linux/driver'
Building kernel module target-linux-zynq-arm/opencpi.ko
make -C /home/embedded/ocpi/opencpi/platforms/zed/release/kernel-headers M=/home/embedded/ocpi/opencpi/adapt/os/ocpios/linux/driver modules
make[2]: Entering directory `/home/embedded/ocpi/opencpi/platforms/zed/release-2013.4/kernel-headers-xilinx-v2013.4'
CC [M] /home/embedded/ocpi/opencpi/adapt/os/ocpios/linux/driver/opencpi.o
/tmp/ccQ7Sgps.s: Assembler messages:
/tmp/ccQ7Sgps.s:923: Error: garbage following instruction – `dmb ish'
/tmp/ccQ7Sgps.s:934: Error: garbage following instruction – `dmb ish'
/tmp/ccQ7Sgps.s:2188: Error: garbage following instruction – `dmb ish'
/tmp/ccQ7Sgps.s:2201: Error: garbage following instruction – `dmb ish'
/tmp/ccQ7Sgps.s:2266: Error: garbage following instruction – `dmb ish'
/tmp/ccQ7Sgps.s:2279: Error: garbage following instruction – `dmb ish'
make[3]: *** /home/embedded/ocpi/opencpi/adapt/os/ocpios/linux/driver/opencpi.o Error 1
make[2]: *** [module/home/embedded/ocpi/opencpi/adapt/os/ocpios/linux/driver] Error 2
make[2]: Leaving directory `/home/embedded/ocpi/opencpi/platforms/zed/release-2013.4/kernel-headers-xilinx-v2013.4'
make[1]: *** [target-linux-zynq-arm/opencpi.ko] Error 2
make[1]: Leaving directory `/home/embedded/ocpi/opencpi/adapt/os/ocpios/linux/driver'
make: *** [driver] Error 2

this is not the standard opencpi compiler used but it is a valid compiler that is widely used and in theory this should work.

Environment

None

Activity

Show:
James Kulp
March 25, 2015, 3:33 PM

Was the entire opencpi build done with this compiler?
Was the kernel built with this compiler?

I imagine that the prebuilt zynq release was built using the Xilinx compiler.

Is this compiler used by other zynq kernels?

Chris Hinkey
March 25, 2015, 3:38 PM

yes complete build was done with the other compiler. I was just unable to compile the driver using the provided headers. I was able to compile using the complete build tree that i was using before to build the kernel.

James Kulp
March 25, 2015, 3:40 PM

On 3/25/15 11:39 AM, chris hinkey (JIRA) wrote:
Message Title

[1]chris hinkey commented on [2]OCPI-61

 

[3]Re: building driver with non-xilinx compiler fails

yes complete build was done with the other compiler. I was just unable to compile the driver using the provided headers. I was able to compile using the complete build tree that i was using before to build the kernel.

[4] [5]Add Comment
 

This message was sent by Atlassian JIRA (v6.4-OD-16-005#64014-sha1:3f74600)

Let's remember to try this next week by generating the kernel-headers with this compiler.

---------------------------------------------------------------------------------------- [1] https://opencpi.atlassian.net/secure/ViewProfile.jspa?name=chinkey
[2] https://opencpi.atlassian.net/browse/OCPI-61
[3] https://opencpi.atlassian.net/browse/OCPI-61
[4] https://opencpi.atlassian.net/browse/OCPI-61#add-comment
[5] https://opencpi.atlassian.net/browse/OCPI-61#add-comment

James Kulp
April 3, 2015, 2:24 PM

We need to find the original reason why there were linking problems against the prebuilt OpenCPI libraries.

James Kulp
April 12, 2017, 12:05 PM

This is too stale.

Won't Fix

Assignee

Chris Hinkey

Reporter

Chris Hinkey

Labels

None

Components

Priority

Minor
Configure