Yocto Project Discussions
 help / color / mirror / Atom feed
From: "Zoltan Kerenyi Nagy" <kerenyi.nagy.zoltan@gmail.com>
To: yocto@lists.yoctoproject.org
Subject: Re: insmod - huawei E3372h kernel module
Date: Fri, 08 Jan 2021 02:24:20 -0800	[thread overview]
Message-ID: <20128.1610101460089237791@lists.yoctoproject.org> (raw)
In-Reply-To: <CAHwRhWanj0AnPWRQcXCku6ZxnBeDWRueCO=U4BDxH8ZxFQyYrg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2622 bytes --]

Hi,

Makefile: huawei_cdc_ncm-y :=    huawei_cdc_ncm.o obj-m += huawei_cdc_ncm.o KDIR ?= /lib/modules/`uname -r`/build all: make -C $(KDIR) M=$(PWD) modules clean: make -C $(KDIR) M=$(PWD) clean install: cp *.ko /lib/modules/$(shell uname -r)/kernel/drivers/misc/ depmod -a

This one doesnt work:
DEBUG: Executing shell function do_compile NOTE: make -j 8 KERNEL_SRC=/home/kerenyiz/oe-core/build/tmp-glibc/work-shared/barix-ipam400/kernel-source KERNEL_PATH=/home/kerenyiz/oe-core/build/tmp-glibc/work-shared/barix-ipam400/kernel-source KERNEL_VERSION=4.10.0 CC=arm-oe-linux-gnueabi-gcc   -fuse-ld=bfd LD=arm-oe-linux-gnueabi-ld.bfd   AR=arm-oe-linux-gnueabi-ar  O=/home/kerenyiz/oe-core/build/tmp-glibc/work-shared/barix-ipam400/kernel-build-artifacts KBUILD_EXTRA_SYMBOLS= ERROR: oe_runmake failed make -C /lib/modules/`uname -r`/build M=/home/kerenyiz/oe-core/build/tmp-glibc/work/barix_ipam400-oe-linux-gnueabi/huawei/1.1-r0 modules make[1]: warning: jobserver unavailable: using -j1.  Add '+' to parent make rule. make[1]: Entering directory '/usr/src/linux-headers-4.15.0-88-generic' make[2]: Entering directory '/home/kerenyiz/oe-core/build/tmp-glibc/work-shared/barix-ipam400/kernel-build-artifacts' make[3]: Circular /home/kerenyiz/oe-core/build/tmp-glibc/work/barix_ipam400-oe-linux-gnueabi/huawei/1.1-r0/huawei_cdc_ncm.o <- /home/kerenyiz/oe-core/build/tmp-glibc/work/barix_ipam400-oe-linux-gnueabi/huawei/1.1-r0/huawei_cdc_ncm.o dependency dropped. LD [M]  /home/kerenyiz/oe-core/build/tmp-glibc/work/barix_ipam400-oe-linux-gnueabi/huawei/1.1-r0/huawei_cdc_ncm.o arm-oe-linux-gnueabi-ld.bfd: no input files /usr/src/linux-headers-4.15.0-88-generic/scripts/Makefile.build:578: recipe for target '/home/kerenyiz/oe-core/build/tmp-glibc/work/barix_ipam400-oe-linux-gnueabi/huawei/1.1-r0/huawei_cdc_ncm.o' failed make[3]: *** [/home/kerenyiz/oe-core/build/tmp-glibc/work/barix_ipam400-oe-linux-gnueabi/huawei/1.1-r0/huawei_cdc_ncm.o] Error 1 /usr/src/linux-headers-4.15.0-88-generic/Makefile:1577: recipe for target '_module_/home/kerenyiz/oe-core/build/tmp-glibc/work/barix_ipam400-oe-linux-gnueabi/huawei/1.1-r0' failed make[2]: *** [_module_/home/kerenyiz/oe-core/build/tmp-glibc/work/barix_ipam400-oe-linux-gnueabi/huawei/1.1-r0] Error 2 make[2]: Leaving directory '/home/kerenyiz/oe-core/build/tmp-glibc/work-shared/barix-ipam400/kernel-build-artifacts' Makefile:146: recipe for target 'sub-make' failed make[1]: *** [sub-make] Error 2 make[1]: Leaving directory '/usr/src/linux-headers-4.15.0-88-generic' Makefile:25: recipe for target 'all' failed make: *** [all] Error 2 ERROR: F --
Zolee

[-- Attachment #2: Type: text/html, Size: 3105 bytes --]

      parent reply	other threads:[~2021-01-08 10:24 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-07 13:46 insmod - huawei E3372h kernel module Zoltan Kerenyi Nagy
2021-01-07 15:03 ` [yocto] " Zoran
2021-01-07 15:16   ` Zoltan Kerenyi Nagy
2021-01-07 15:27     ` Zoran
     [not found]     ` <1657FCB4180F6472.31350@lists.yoctoproject.org>
2021-01-07 17:20       ` Zoran
     [not found]         ` <CAHwRhWZSW+g0qJkAQLz5npmi5ig37XTvM6r_tJWmpk3ERMB9ew@mail.gmail.com>
2021-01-07 18:35           ` Zoran
2021-01-08 10:36         ` Zoltan Kerenyi Nagy
2021-01-08 11:22           ` Zoltan Kerenyi Nagy
2021-01-08 11:59             ` [yocto] " Zoran
2021-01-08 12:28               ` Zoltan Kerenyi Nagy
2021-01-08 12:49                 ` [yocto] " Zoran
     [not found]                 ` <165842AB3B8C5237.7830@lists.yoctoproject.org>
2021-01-08 14:43                   ` Zoran
2021-01-11 10:23                     ` Zoltan Kerenyi Nagy
2021-01-11 13:20                     ` Zoltan Kerenyi Nagy
2021-01-12 15:13                     ` Zoltan Kerenyi Nagy
2021-01-12 15:17                       ` Zoltan Kerenyi Nagy
2021-01-17 12:34                     ` Zoltan Kerenyi Nagy
2021-01-17 22:27                       ` [yocto] " Zoran
2021-01-18  5:27                         ` Zoltan Kerenyi Nagy
2021-01-19 13:00                         ` Zoltan Kerenyi Nagy
2021-01-19 13:23                           ` [yocto] " Zoran
     [not found]                           ` <165BA4E49F808CA9.28472@lists.yoctoproject.org>
2021-01-19 13:27                             ` Zoran
2021-01-19 13:41                         ` Zoltan Kerenyi Nagy
2021-01-19 14:48                           ` Zoltan Kerenyi Nagy
2021-01-19 16:54                             ` [yocto] " Zoran
2021-01-20 11:20                               ` Zoltan Kerenyi Nagy
2021-01-20 13:04                                 ` [yocto] " Zoran
2021-01-21 10:00                                   ` Zoltan Kerenyi Nagy
2021-01-25 13:39                                     ` Zoltan Kerenyi Nagy
2021-01-08 12:35               ` Zoltan Kerenyi Nagy
2021-01-08 10:24     ` Zoltan Kerenyi Nagy [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20128.1610101460089237791@lists.yoctoproject.org \
    --to=kerenyi.nagy.zoltan@gmail.com \
    --cc=yocto@lists.yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox