From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15021] Buildroot not compiling with systemd and glibc.
Date: Tue, 27 Sep 2022 13:43:52 +0000 [thread overview]
Message-ID: <bug-15021-163-PKqjeuxhXT@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-15021-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=15021
--- Comment #3 from Thomas Petazzoni <thomas.petazzoni@bootlin.com> ---
If you're developing an actual product, I would suggest using either 2022.08 or
2022.02.
If you really want to be at the tip, use master, and revert commit
80c8c15c8534a24382b900a07082a289a368f736. We have it since only a few days,
precisely to see what will be the issues with the glibc 2.36 bump. Now we need
to figure out the solutions to those issues :-)
--
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:[~2022-09-27 13:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-27 7:26 [Buildroot] [Bug 15021] New: Buildroot not compiling with systemd and glibc bugzilla
2022-09-27 9:06 ` [Buildroot] [Bug 15021] " bugzilla
2022-09-27 10:11 ` bugzilla
2022-09-27 13:43 ` bugzilla [this message]
2022-11-02 20:57 ` 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-15021-163-PKqjeuxhXT@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