All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15898] Unable to boot syslinux.efi produced by buildroot (EFI 64-bit), the one provided by the tarball works fine though
Date: Sat, 23 Dec 2023 18:49:17 +0000	[thread overview]
Message-ID: <bug-15898-163-trkqwJHlic@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-15898-163@https.bugs.busybox.net/>

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

Meliodas <meliodasren01@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |DUPLICATE

--- Comment #1 from Meliodas <meliodasren01@gmail.com> ---
This can be closed as a duplicate of 11861. I tried building syslinux 6.0.3
myself outside of buildroot and had the same problem. Applying the patch from
11861 fixed it. I don't know how to apply the patch when building from within
buildroot though.

*** This bug has been marked as a duplicate of bug 11861 ***

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2023-12-23 18:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-22 18:56 [Buildroot] [Bug 15898] New: Unable to boot syslinux.efi produced by buildroot (EFI 64-bit), the one provided by the tarball works fine though bugzilla
2023-12-23 18:49 ` bugzilla [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=bug-15898-163-trkqwJHlic@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@uclibc.org \
    /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.