From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
Cc: Kevin <anaknaga@inventati.org>,
WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Trouble building WireGuard since December releases
Date: Thu, 25 Jan 2018 00:07:39 +0100 [thread overview]
Message-ID: <CAHmME9qM8woaJ9-g0_xZW55qsWyMPKBX3L8rBxuoBwBoGytpXw@mail.gmail.com> (raw)
In-Reply-To: <87lggngkih.fsf@fifthhorseman.net>
On Wed, Jan 24, 2018 at 7:49 PM, Daniel Kahn Gillmor
<dkg@fifthhorseman.net> wrote:
>
> On Mon 2018-01-22 17:07:38 +0100, Jason A. Donenfeld wrote:
> > Ahh, small update. When building this, I noticed:
> >
> > Makefile:944: "Cannot use CONFIG_STACK_VALIDATION=y, please install
> > libelf-dev, libelf-devel or elfutils-libelf-devel"
>
> fwiw, debian had the same issue around libelf-dev with their kernel
> source packaging, and treated it as a bug there, which was resolved in
> the kernel package itself, rather than requiring additional build
> dependencies of all kernel modules: https://bugs.debian.org/886474
Seems like a sane resolution.
>
> (this message is just about libelf-dev; i haven't followed the details
> about objtool)
The detail about objtool is just that they forgot to include it in
their headers, so when the build system tries to use it, it can't find
it and fails. Simple problem with a simple solution, thankfully.
prev parent reply other threads:[~2018-01-24 23:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-22 14:42 Kevin
2018-01-22 15:23 ` Greg KH
2018-01-22 15:34 ` Jason A. Donenfeld
2018-01-22 15:53 ` Jason A. Donenfeld
2018-01-22 16:07 ` Jason A. Donenfeld
2018-01-24 18:49 ` Daniel Kahn Gillmor
2018-01-24 23:07 ` Jason A. Donenfeld [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=CAHmME9qM8woaJ9-g0_xZW55qsWyMPKBX3L8rBxuoBwBoGytpXw@mail.gmail.com \
--to=jason@zx2c4.com \
--cc=anaknaga@inventati.org \
--cc=dkg@fifthhorseman.net \
--cc=wireguard@lists.zx2c4.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;
as well as URLs for NNTP newsgroup(s).