mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Davidlohr Bueso <dave@stgolabs.net>
To: Vinson Lee <vlee@twopensource.com>
Cc: David Howells <dhowells@redhat.com>,
	David Woodhouse <David.Woodhouse@intel.com>,
	"Luis R. Rodriguez" <mcgrof@suse.com>,
	Mimi Zohar <zohar@linux.vnet.ibm.com>,
	Marcel Holtmann <marcel@holtmann.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: Linux 4.3-rc1 build error on CentOS 5.11 "scripts/sign-file.c:23:25: fatal error: openssl/cms.h: No such file or directory"
Date: Fri, 11 Sep 2015 16:22:32 -0700	[thread overview]
Message-ID: <20150911232232.GE19736@linux-q0g1.site> (raw)
In-Reply-To: <CAHTgTXVjAmbQz5HM7wAVforMmxQYdgCoz0JKtkb1V30jBSz8zQ@mail.gmail.com>

On Fri, 11 Sep 2015, Vinson Lee wrote:

>Hi.
>
>With the latest Linux 4.3-rc1, I am hitting this build error on CentOS 5.11.
>
>  HOSTCC  scripts/sign-file
>scripts/sign-file.c:23:25: fatal error: openssl/cms.h: No such file or directory
> #include <openssl/cms.h>

fwiw/rant, I have run into kernel build issues recently due to lack of openssl libs.
The solution is trivial, in my case just intalling my distros openssl-devel
package, but this will probably break things for more people. And this is with default
configs... annoying.

Thanks,
Davidlohr

  reply	other threads:[~2015-09-11 23:22 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-11 22:41 Vinson Lee
2015-09-11 23:22 ` Davidlohr Bueso [this message]
2015-09-12 21:40   ` Jim Davis
2015-09-14  2:14   ` Dongsheng Yang
2015-09-15 13:40 ` David Howells
2015-09-15 22:01   ` Vinson Lee
2015-09-15 22:56   ` David Howells
2015-09-16 22:45   ` David Howells
2015-09-18  6:48     ` Vinson Lee
2015-09-24 11:18     ` David Howells
2015-09-24 11:21     ` David Howells
2015-09-24 22:24       ` Vinson Lee
2015-09-25  6:16       ` David Howells
2015-09-25 14:24       ` David Howells
2015-09-26  1:43         ` Vinson Lee

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=20150911232232.GE19736@linux-q0g1.site \
    --to=dave@stgolabs.net \
    --cc=David.Woodhouse@intel.com \
    --cc=dhowells@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --cc=mcgrof@suse.com \
    --cc=vlee@twopensource.com \
    --cc=zohar@linux.vnet.ibm.com \
    /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
all inboxes | Powered by JetHome®