From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11761] New: Building custom kernel 5.1-rc3 or later breaks on tools/objtool
Date: Mon, 08 Apr 2019 16:12:35 +0000 [thread overview]
Message-ID: <bug-11761-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=11761
Bug ID: 11761
Summary: Building custom kernel 5.1-rc3 or later breaks on
tools/objtool
Product: buildroot
Version: 2018.11.2
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: janusz.krzysztofik at intel.com
CC: buildroot at uclibc.org
Target Milestone: ---
The issue is related to kernel commit 056d28d135bca0b1d0908990338e00e9dadaf057
("objtool: Query pkg-config for libelf location"). Reverting that change
resolves the issue for me. Maybe it's too early for a bug report but that must
be resolved on buildroot side sooner or later, I believe.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2019-04-08 16:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-08 16:12 bugzilla at busybox.net [this message]
2019-04-08 19:24 ` [Buildroot] [Bug 11761] Building custom kernel 5.1-rc3 or later breaks on tools/objtool bugzilla at busybox.net
2019-04-13 15:13 ` bugzilla at busybox.net
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=bug-11761-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.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 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.