Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error Whilst running make #300

Closed
explodersname opened this issue Apr 27, 2020 · 1 comment
Closed

Error Whilst running make #300

explodersname opened this issue Apr 27, 2020 · 1 comment
Labels
duplicate there's already a bug describing the same problem. please enhance the original issue. invalid not an issue; or the description doesn't make it clear what the actual problem is; or...

Comments

@explodersname
Copy link

explodersname commented Apr 27, 2020

Building v4l2-loopback driver...
make -C /lib/modules/`uname -r`/build M=/home/explodersname/v4l2loopback modules
make[1]: *** /lib/modules/4.19.98-08076-g24ab33fb8e14/build: No such file or directory.  Stop.
Makefile:42: recipe for target 'v4l2loopback.ko' failed
make: *** [v4l2loopback.ko] Error 2

is the error that is outputed my my terminal when running the command "make" I have already looked through my files and confirmed that /lib/modules/blahblah/build is a file and am confused as to why it hasnt found it. Maybe I need to find a way to add /root/ to the beginning of the file search? (This often happens when I want to install packages so i must add /root/ to the beginning of the file location if im not already in the directory)

@umlaeute umlaeute added duplicate there's already a bug describing the same problem. please enhance the original issue. invalid not an issue; or the description doesn't make it clear what the actual problem is; or... labels Apr 27, 2020
@umlaeute
Copy link
Owner

please install the proper kernel-headers for your system, and make sure that the you can actually build something.
and btw, /lib/modules/4.19.98-08076-g24ab33fb8e14/build should not be a file (in the narrow sense), but a symlink to the directory containing your kernel-headers.

<rant>
it's hard to tell you how tired i am of getting bug-reports like this.

  • please read the documentation before submitting bug-reports
  • please check the issue tracker before submitting bugs
  • please understand that i cannot take care of any quirks you might have done to break your build-system
    </rant>

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate there's already a bug describing the same problem. please enhance the original issue. invalid not an issue; or the description doesn't make it clear what the actual problem is; or...
Projects
None yet
Development

No branches or pull requests

2 participants