From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 10261] Grub2 fails to build for x86_64
Date: Wed, 30 Aug 2017 01:50:09 +0000 [thread overview]
Message-ID: <bug-10261-163-SDFFBKFJ3X@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-10261-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=10261
Erico Nunes <nunes.erico@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at buildroot.uclibc |nunes.erico at gmail.com
|.org |
--- Comment #6 from Erico Nunes <nunes.erico@gmail.com> ---
It turns out that grub2 fails to build with BR2_SSP_ALL=y.
The following defconfig is enough to reproduce the issue:
BR2_x86_64=y
BR2_SSP_ALL=y
BR2_TOOLCHAIN_BUILDROOT_GLIBC=y
BR2_TARGET_GRUB2=y
BR2_TARGET_GRUB2_X86_64_EFI=y
We already had Bug 8946 in the past with a very similar issue and from which we
can borrow a solution. So I sent the following patch as an attempt to address
this issue before 2017.08 is cut out:
https://patchwork.ozlabs.org/patch/807377/
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2017-08-30 1:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-29 7:49 [Buildroot] [Bug 10261] New: Grub2 fails to build for x86_64 bugzilla at busybox.net
2017-08-29 7:58 ` [Buildroot] [Bug 10261] " bugzilla at busybox.net
2017-08-29 9:56 ` bugzilla at busybox.net
2017-08-29 12:02 ` bugzilla at busybox.net
2017-08-29 13:34 ` bugzilla at busybox.net
2017-08-29 14:57 ` bugzilla at busybox.net
2017-08-30 1:50 ` bugzilla at busybox.net [this message]
2017-08-30 20:10 ` 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-10261-163-SDFFBKFJ3X@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox