Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 14926] package/nodejs: build for host fails with GTEST errors
Date: Wed, 17 Aug 2022 05:38:28 +0000	[thread overview]
Message-ID: <bug-14926-163-dMacd7GBwG@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-14926-163@https.bugs.busybox.net/>

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

Peter Korsgaard <jacmet@uclibc.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|NEW                         |RESOLVED

--- Comment #10 from Peter Korsgaard <jacmet@uclibc.org> ---
The gtest version bump (and nodejs security fixes) are now backported to
2022.02.x / 2022.05.x and will be in the August releases, thanks.

-- 
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

      parent reply	other threads:[~2022-08-17  5:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-29  7:33 [Buildroot] [Bug 14926] New: package/nodejs: build for host fails with GTEST errors bugzilla
2022-07-29  7:59 ` [Buildroot] [Bug 14926] " bugzilla
2022-07-29  8:29 ` bugzilla
2022-07-29  9:36 ` bugzilla
2022-07-29 12:11 ` bugzilla
2022-07-29 13:17 ` bugzilla
2022-07-29 13:27 ` bugzilla
2022-07-29 13:33 ` bugzilla
2022-07-30  7:30 ` bugzilla
2022-07-30 14:51 ` bugzilla
2022-08-17  5:38 ` 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-14926-163-dMacd7GBwG@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