Re: Build error

Amit Kumar <free.amit.kumar@xxxxxxxxx> · Sun, 29 Jan 2017 08:32:58 +0000

On Sun, Jan 29, 2017 at 1:48 PM Ozgur Karatas <mueddib@xxxxxxxxxx> wrote:

29.01.2017, 10:05, "Amit Kumar" <free.amit.kumar@xxxxxxxxx>:
 On Thu, Jan 26, 2017 at 12:31 PM Greg KH <greg@xxxxxxxxx> wrote:
On Thu, Jan 26, 2017 at 11:08:48AM +0530, Amit Kumar wrote:
> Hi,
> For last several days when I build arm64/defconfig even against
> next-20170125, I
> get the following error.
> arch/arm64/crypto/crc32-arm64.c:1:0: error: unknown feature modifier
> ‘crc’
>  /*
>   ^
> make[1]: *** [arch/arm64/crypto/crc32-arm64.o] Error 1
> make: *** [arch/arm64/crypto] Error 2
 Have you tried asking on the linux arm mailing list?

Thank you for your reply.
I'm a newbie and not competent enough to sort out this problem, so I have sent mail to kernelnewbies to bring this issue to the Linux Kernel Community. I think that mailing list is more suitable if I were able create a patch. I am learning kernel development and very soon I'll start contributing to Linux Kernel

Hello,

you are welcome firstly and of course you will contribute to the development and thanks. Please find and understand to how to debug C code? What happens when a kernel module fails? How to fix to compilation errors?

The error in the example is obvious, should be examine to crc32-arm64.c code, The kernel can't initialize to crc32-arm64.o module and it may be a feature errors.

Please review crc32-arm64.c
checkpatch.pl check to crc32-arm64.c

run make:

$ make M=arch/arm64/crypto/
  LD      arch/arm64/crypto//built-in.o
  Building modules, stage 2.
  MODPOST 0 modules

Module created! Good!
Check module,

$ make arch/arm64/crypto/crc32-arm64.o
  CHK     include/config/kernel.release
  CHK     include/generated/uapi/linux/version.h
  CHK     include/generated/utsrelease.h
  CHK     include/generated/bounds.h
  CHK     include/generated/timeconst.h
  CHK     include/generated/asm-offsets.h
  CALL    scripts/checksyscalls.sh
  CC      arch/arm64/crypto/crc32-arm64.o
Thank you for your reply. I think these steps will be helpful in debugging in future. 

Regards,

~Ozgur

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@xxxxxxxxxxxxxxxxx
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies