Executing “make†command = no rule for target 'modules'
Clash Royale CLAN TAG#URR8PPP
up vote
1
down vote
favorite
I am compiling a driver for mt7601U on my machine with Manjaro 17.1.2 - Deepin 15.
The instructions for compiling the driver can be found here. I have done all the necessary commenting for the code. When I try to execute the command:
make -C /lib/modules/$(uname -r)/build M=$(pwd) modules
It responded:
make: Entering directory '/usr/lib/modules/4.14.14-1-MANJARO/build'
make: *** No rule to make target 'modules'. Stop
make: Leaving directory '/usr/lib/modules/4.14.14-1-MANJARO/build'
Do I need another package to compile the driver correctly?
arch-linux manjaro deepin
edited Feb 10 at 4:43
aliceinpalth
760116
asked Jan 24 at 11:09
Yves Gonzaga
1062
add a comment |Â
up vote
1
down vote
favorite
I am compiling a driver for mt7601U on my machine with Manjaro 17.1.2 - Deepin 15.
The instructions for compiling the driver can be found here. I have done all the necessary commenting for the code. When I try to execute the command:
make -C /lib/modules/$(uname -r)/build M=$(pwd) modules
It responded:
make: Entering directory '/usr/lib/modules/4.14.14-1-MANJARO/build'
make: *** No rule to make target 'modules'. Stop
make: Leaving directory '/usr/lib/modules/4.14.14-1-MANJARO/build'
Do I need another package to compile the driver correctly?
arch-linux manjaro deepin
edited Feb 10 at 4:43
aliceinpalth
760116
asked Jan 24 at 11:09
Yves Gonzaga
1062
add a comment |Â
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I am compiling a driver for mt7601U on my machine with Manjaro 17.1.2 - Deepin 15.
The instructions for compiling the driver can be found here. I have done all the necessary commenting for the code. When I try to execute the command:
make -C /lib/modules/$(uname -r)/build M=$(pwd) modules
It responded:
make: Entering directory '/usr/lib/modules/4.14.14-1-MANJARO/build'
make: *** No rule to make target 'modules'. Stop
make: Leaving directory '/usr/lib/modules/4.14.14-1-MANJARO/build'
Do I need another package to compile the driver correctly?
arch-linux manjaro deepin
edited Feb 10 at 4:43
aliceinpalth
760116
asked Jan 24 at 11:09
Yves Gonzaga
1062
I am compiling a driver for mt7601U on my machine with Manjaro 17.1.2 - Deepin 15.
The instructions for compiling the driver can be found here. I have done all the necessary commenting for the code. When I try to execute the command:
make -C /lib/modules/$(uname -r)/build M=$(pwd) modules
It responded:
make: Entering directory '/usr/lib/modules/4.14.14-1-MANJARO/build'
make: *** No rule to make target 'modules'. Stop
make: Leaving directory '/usr/lib/modules/4.14.14-1-MANJARO/build'
Do I need another package to compile the driver correctly?
arch-linux manjaro deepin
edited Feb 10 at 4:43
aliceinpalth
760116
asked Jan 24 at 11:09
Yves Gonzaga
1062
edited Feb 10 at 4:43
aliceinpalth
760116
edited Feb 10 at 4:43
aliceinpalth
760116
edited Feb 10 at 4:43
aliceinpalth
760116
760116
asked Jan 24 at 11:09
Yves Gonzaga
1062
asked Jan 24 at 11:09
Yves Gonzaga
1062
asked Jan 24 at 11:09
Yves Gonzaga
1062
1062
add a comment |Â
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
0
down vote
Generally, /lib/modules/*/build (where * is a versioning formatting of some sort) is a soft link to the Linux kernel header files to help build packages. The actual files being linked to are commonly found in /usr/src/linux-* (where * is again a versioning format).
It seems that you are on Linux 4.14. You should first verify that by running uname -r to double check the version. If so, you can install the header files by running the following:
$ sudo pacman -S linux414-headers
You may also want to update your system using:
$ sudo pacman-mirrors -f 5 && sudo pacman -Syyu
Then, reboot your system.
answered Feb 10 at 1:43
aliceinpalth
760116
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
Generally, /lib/modules/*/build (where * is a versioning formatting of some sort) is a soft link to the Linux kernel header files to help build packages. The actual files being linked to are commonly found in /usr/src/linux-* (where * is again a versioning format).
It seems that you are on Linux 4.14. You should first verify that by running uname -r to double check the version. If so, you can install the header files by running the following:
$ sudo pacman -S linux414-headers
You may also want to update your system using:
$ sudo pacman-mirrors -f 5 && sudo pacman -Syyu
Then, reboot your system.
answered Feb 10 at 1:43
aliceinpalth
760116
add a comment |Â
up vote
0
down vote
Generally, /lib/modules/*/build (where * is a versioning formatting of some sort) is a soft link to the Linux kernel header files to help build packages. The actual files being linked to are commonly found in /usr/src/linux-* (where * is again a versioning format).
It seems that you are on Linux 4.14. You should first verify that by running uname -r to double check the version. If so, you can install the header files by running the following:
$ sudo pacman -S linux414-headers
You may also want to update your system using:
$ sudo pacman-mirrors -f 5 && sudo pacman -Syyu
Then, reboot your system.
answered Feb 10 at 1:43
aliceinpalth
760116
add a comment |Â
up vote
0
down vote
up vote
0
down vote
Generally, /lib/modules/*/build (where * is a versioning formatting of some sort) is a soft link to the Linux kernel header files to help build packages. The actual files being linked to are commonly found in /usr/src/linux-* (where * is again a versioning format).
It seems that you are on Linux 4.14. You should first verify that by running uname -r to double check the version. If so, you can install the header files by running the following:
$ sudo pacman -S linux414-headers
You may also want to update your system using:
$ sudo pacman-mirrors -f 5 && sudo pacman -Syyu
Then, reboot your system.
answered Feb 10 at 1:43
aliceinpalth
760116
Generally, /lib/modules/*/build (where * is a versioning formatting of some sort) is a soft link to the Linux kernel header files to help build packages. The actual files being linked to are commonly found in /usr/src/linux-* (where * is again a versioning format).
It seems that you are on Linux 4.14. You should first verify that by running uname -r to double check the version. If so, you can install the header files by running the following:
$ sudo pacman -S linux414-headers
You may also want to update your system using:
$ sudo pacman-mirrors -f 5 && sudo pacman -Syyu
Then, reboot your system.
answered Feb 10 at 1:43
aliceinpalth
760116
answered Feb 10 at 1:43
aliceinpalth
760116
answered Feb 10 at 1:43
aliceinpalth
760116
answered Feb 10 at 1:43
aliceinpalth
760116
760116
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f419318%2fexecuting-make-command-no-rule-for-target-modules%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
