From: David Howells <dhowells@redhat.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: [modsign:devel-x509 19/19] gcc: error: security/keys/crypto/x509-asn1.c: No such file or directo
Date: Fri, 20 Jul 2012 14:28:07 +0000 [thread overview]
Message-ID: <7577.1342794487@warthog.procyon.org.uk> (raw)
Fengguang Wu <fengguang.wu@intel.com> wrote:
> Kernel build failed somewhere in
>
> tree: git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-modsign.git devel-x509
> head: 60e96ee932ebebf7c93f36b72475a12af7b0bc4e
> config: x86_64-allmodconfig (attached as .config)
>
> Build errors:
>
> gcc: error: security/keys/crypto/x509-asn1.c: No such file or directory
> gcc: error: security/keys/crypto/x509_rsakey-asn1.c: No such file or directory
> Can't open perl script "lib/build_OID_registry": No such file or directory
I can't reproduce this. The lib/build_OID_registry error is particularly odd
as the patches are clearly adding and modifying it. Are you building into a
separate directory to the source tree?
David
next reply other threads:[~2012-07-20 14:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-20 14:28 David Howells [this message]
2012-07-20 14:37 ` [modsign:devel-x509 19/19] gcc: error: security/keys/crypto/x509-asn1.c: No such file or directo Fengguang Wu
2012-07-20 14:52 ` David Howells
2012-07-20 15:08 ` David Howells
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=7577.1342794487@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=kernel-janitors@vger.kernel.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 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.