From: vcaputo@pengaru.com
To: Rob Landley <rob@landley.net>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Commit fc72ae40e303 broke x86-64 build environment.
Date: Sat, 13 Jan 2018 21:31:29 -0800 [thread overview]
Message-ID: <20180114053129.f72gfyphp2a6tmb6@shells.gnugeneration.com> (raw)
In-Reply-To: <5481b34b-9bf2-4709-8a2f-5cfe4bbcef2c@landley.net>
On Sat, Jan 13, 2018 at 11:13:13PM -0600, Rob Landley wrote:
> You've made the ORC unwinder part of allnoconfig, which means trying to
> build "make ARCH=x86_64 allnoconfig" requires installing a new package
> (libelf-dev) or else the build breaks.
>
> What's worse, if I go into menuconfig and switch it back to frame
> pointer, the build STILL breaks:
>
> $ make -j 8
> Makefile:932: *** "Cannot generate ORC metadata for
> CONFIG_UNWINDER_ORC=y, please install libelf-dev, libelf-devel or
> elfutils-libelf-devel". Stop.
> $ grep UNWIND .config
> # CONFIG_UNWINDER_ORC is not set
> CONFIG_UNWINDER_FRAME_POINTER=y
> # CONFIG_UNWINDER_GUESS is not set
>
> As far as I can tell, x86-64 doesn't build anymore without libelf-dev.
> It's a new hard requirement for the build.
>
FYI this has already been brought up on lkml:
https://patchwork.kernel.org/patch/10137237/
IIRC you can get things working by deleting include/config/auto.conf
when you've switched back to CONFIG_UNWINDER_FRAME_POINTER.
I don't believe anything other than making CONFIG_UNWINDER_ORC the
default was intentional. The frustration is just a consequence of some
build system bug.
Regards,
Vito Caputo
prev parent reply other threads:[~2018-01-14 5:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-14 5:13 Rob Landley
2018-01-14 5:31 ` vcaputo [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=20180114053129.f72gfyphp2a6tmb6@shells.gnugeneration.com \
--to=vcaputo@pengaru.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rob@landley.net \
/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
Powered by JetHome