From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Calvince Otieno <calvncce@gmail.com>,
Linux Outreachy <outreachy@lists.linux.dev>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Kernel Build System <linux-kbuild@vger.kernel.org>
Subject: Re: Unable to make file
Date: Sat, 7 Oct 2023 21:14:23 +0700 [thread overview]
Message-ID: <ZSFnvwvXMiisHOJ7@debian.me> (raw)
In-Reply-To: <CADFX3OQ1rdnR=ONu5wufAYN0NrvMkaveQ_Y9z_1K8m9Dzz3SPA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 759 bytes --]
On Sat, Oct 07, 2023 at 04:50:32PM +0300, Calvince Otieno wrote:
> Hello team!
>
> I have a problem. I tried running the Make file and I got this error message:
>
> make[3]: *** No rule to make target 'debian/canonical-certs.pem',
> needed by 'certs/x509_certificate_list'. Stop.
>
> make[2]: *** [scripts/Makefile.build:480: certs] Error 2
>
> make[1]: *** [/home/calvince/Documents/labs/git/kernels/staging/Makefile:1913:
> .] Error 2
>
> make: *** [Makefile:234: __sub-make] Error 2
If you need to keep your modules signed, you have to generate your own
certificate. See Documentation/admin-guide/module-signing.rst in the kernel
sources for how to do that.
Thanks.
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2023-10-07 14:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-07 13:50 Unable to make file Calvince Otieno
2023-10-07 13:58 ` Isoken Ibizugbe
2023-10-07 14:00 ` Julia Lawall
2023-10-07 14:14 ` Bagas Sanjaya [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=ZSFnvwvXMiisHOJ7@debian.me \
--to=bagasdotme@gmail.com \
--cc=calvncce@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=outreachy@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.