From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 13126] make fails - bzip2-1.0.6.tar.gz and DirectFB-1.7.7.tar.gz aren't tarballs
Date: Mon, 07 Mar 2022 19:44:26 +0000 [thread overview]
Message-ID: <bug-13126-163-idokOVWKPS@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-13126-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=13126
Peter Korsgaard <jacmet@uclibc.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|NEW |RESOLVED
--- Comment #2 from Peter Korsgaard <jacmet@uclibc.org> ---
Fixed for directfb{,-examples} as well with
https://git.buildroot.org/buildroot/commit/?id=89ab2a5a3f4588891ab1e9e76feb8c3f69402d5c
--
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
prev parent reply other threads:[~2022-03-07 19:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-30 2:31 [Buildroot] [Bug 13126] New: make fails - bzip2-1.0.6.tar.gz and DirectFB-1.7.7.tar.gz aren't tarballs bugzilla at busybox.net
2020-07-30 22:21 ` [Buildroot] [Bug 13126] " bugzilla at busybox.net
2022-03-07 19:44 ` 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-13126-163-idokOVWKPS@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox