From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15889] please update meson
Date: Tue, 12 Dec 2023 19:48:49 +0000 [thread overview]
Message-ID: <bug-15889-163-hZ91uv6wdN@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-15889-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=15889
Yann E. MORIN <yann.morin.1998@free.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |INVALID
--- Comment #1 from Yann E. MORIN <yann.morin.1998@free.fr> ---
stsp, All,
(In reply to stsp from comment #0)
> Current buildroot git has meson-1.1.1.
> But the latest release is 1.3.0.
We had to revert the bump to version 1.2.0, see:
https://gitlab.com/buildroot.org/buildroot/-/commit/acfdf21f0b752e844a33c70a0fd2f82f4534a5a0
> I can't build my project with 1.1.1
> (or even 1.2).
Please help us by doing the version bump localy and test it,
and then contribute the patch with appropriate explanations
on why it is now safe to bump to 1.3.0 and how the breakage
with 1.2.0 was fixed upstream.
See the manual for how to contribute to Buildroot:
https://buildroot.org/downloads/manual/manual.html#_contributing_to_buildroot
As this is a feature request, it is better handled on the
mailing list now; closing.
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
next prev parent reply other threads:[~2023-12-12 19:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-11 8:57 [Buildroot] [Bug 15889] New: please update meson bugzilla
2023-12-12 19:48 ` bugzilla [this message]
2023-12-13 6:44 ` [Buildroot] [Bug 15889] " 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-15889-163-hZ91uv6wdN@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