From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 13356] libabseil-cpp: not building for raspberry pi
Date: Wed, 27 Jul 2022 18:34:27 +0000 [thread overview]
Message-ID: <bug-13356-163-gXxDgqInDV@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-13356-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=13356
Michael Nosthoff <buildroot@heine.tech> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #3 from Michael Nosthoff <buildroot@heine.tech> ---
the github issued set this to resolved since 20211102. See
https://github.com/abseil/abseil-cpp/issues/662
--
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-07-27 18:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-04 9:32 [Buildroot] [Bug 13356] New: libabseil-cpp: not building for raspberry pi bugzilla at busybox.net
2020-12-04 18:15 ` [Buildroot] [Bug 13356] " bugzilla at busybox.net
2020-12-04 18:18 ` bugzilla at busybox.net
2022-07-27 18:34 ` 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-13356-163-gXxDgqInDV@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.