public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel•org>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: kernel-build-reports@lists•linaro.org,
	linaro-kernel@lists•linaro.org, linux-next@vger•kernel.org
Subject: Re: next-20150817 build: 2 failures 16 warnings (next-20150817)
Date: Mon, 17 Aug 2015 10:39:04 -0700	[thread overview]
Message-ID: <20150817173904.GR10748@sirena.org.uk> (raw)
In-Reply-To: <20150818000125.2225c713@canb.auug.org.au>

[-- Attachment #1: Type: text/plain, Size: 798 bytes --]

On Tue, Aug 18, 2015 at 12:01:25AM +1000, Stephen Rothwell wrote:
> On Mon, 17 Aug 2015 13:23:04 +0100 Build bot for Mark Brown <broonie@kernel•org> wrote:

> > 	arm64-allmodconfig
> > ../scripts/sign-file.c:20:25: fatal error: openssl/bio.h: No such file or directory
> > ../scripts/extract-cert.c:23:25: fatal error: openssl/bio.h: No such file or directory

> > 	arm-allmodconfig
> > ../scripts/sign-file.c:20:25: fatal error: openssl/bio.h: No such file or directory
> > ../scripts/extract-cert.c:23:25: fatal error: openssl/bio.h: No such file or directory

> allmodconfig builds will now need libssl-dev or the equivalent installed
> to build the host programs for the new signing code that came in the
> security tree today.

Ugh.  This is going to be broken until I get home next Monday :(

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

      reply	other threads:[~2015-08-17 17:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-17 12:23 next-20150817 build: 2 failures 16 warnings (next-20150817) Build bot for Mark Brown
2015-08-17 14:01 ` Stephen Rothwell
2015-08-17 17:39   ` Mark Brown [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=20150817173904.GR10748@sirena.org.uk \
    --to=broonie@kernel$(echo .)org \
    --cc=kernel-build-reports@lists$(echo .)linaro.org \
    --cc=linaro-kernel@lists$(echo .)linaro.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=sfr@canb$(echo .)auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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