All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 14826] make qemu_x86_64_defconfig stopped working
Date: Mon, 30 May 2022 22:04:02 +0000	[thread overview]
Message-ID: <bug-14826-163-uTv8cB8Iq4@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-14826-163@https.bugs.busybox.net/>

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

Yann E. MORIN <yann.morin.1998@free.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |yann.morin.1998@free.fr

--- Comment #1 from Yann E. MORIN <yann.morin.1998@free.fr> ---
Hello,

I am afraid I was not able to reproduce the failure.

From a clean checkout of git master (d590003), I did:

    make qemu_x86_64_defconfig
    make

And the build succeeded.

What version of Buildroot are you using?
What system are you building on?

Regards,
Yann E. MORIN.

-- 
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:[~2022-05-30 22:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-30 19:41 [Buildroot] [Bug 14826] New: make qemu_x86_64_defconfig stopped working bugzilla
2022-05-30 22:04 ` bugzilla [this message]
2022-05-30 23:40 ` [Buildroot] [Bug 14826] " bugzilla
2022-05-30 23:41 ` bugzilla
2022-05-31  9:28 ` bugzilla
2022-05-31 12:15 ` bugzilla
2022-05-31 17:48 ` bugzilla
2022-06-04  8:24 ` bugzilla

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-14826-163-uTv8cB8Iq4@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.