Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 10261] Grub2 fails to build for x86_64
Date: Tue, 29 Aug 2017 14:57:10 +0000	[thread overview]
Message-ID: <bug-10261-163-gpvN5m8Nuy@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-10261-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=10261

--- Comment #5 from Erico Nunes <nunes.erico@gmail.com> ---
I am able to reproduce the issue with your config, running Fedora 26 if that
matters. Had to remove some of your user specific settings such as ones
pointing to your BR2_EXTERNAL, but nevertheless reproduced:

> checking whether -fno-asynchronous-unwind-tables works... yes
> checking whether -fno-unwind-tables works... yes
> checking for target linking format... unknown
> configure: error: no suitable link format found

I retested and am not able to reproduce a grub2 build failure with
pc_x86_64_efi_defconfig, so it must be one of your changes.

So now we need to narrow down which of your changes caused this, might be the
changes in the grub2 config or more likely some of your optimization settings.

Also we might consider retesting this with the v2 patchset on patchwork at [1]
since it did some better separation between the host part and target part of
grub2 which I wouldn't discard being a cause here (this would be one more
reason to have something like that merged). I plan to respin that for 2017.11.


[1]
https://patchwork.ozlabs.org/project/buildroot/list/?submitter=46481&q=grub2&archive=&delegate=&state=*

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2017-08-29 14:57 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 [this message]
2017-08-30  1:50 ` bugzilla at busybox.net
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-gpvN5m8Nuy@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