From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 14926] package/nodejs: build for host fails with GTEST errors
Date: Sat, 30 Jul 2022 07:30:00 +0000 [thread overview]
Message-ID: <bug-14926-163-SFaectsMBm@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-14926-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=14926
Yann E. MORIN <yann.morin.1998@free.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jacmet@uclibc.org,
| |yann.morin.1998@free.fr
--- Comment #8 from Yann E. MORIN <yann.morin.1998@free.fr> ---
Wolfgang, All,
The only package that used to need host-gtest was gtest itself. On master,
we bumped gtest to a newer version that no longer requires host-gtest, so
we dropped it.
The version bump seems very minor, so maybe it would be worth backporting
to the stable branch so we can drop host-gtest and fix this host-nodejs
issue.
Peter?
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:[~2022-07-30 7:30 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 [this message]
2022-07-30 14:51 ` bugzilla
2022-08-17 5:38 ` 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-14926-163-SFaectsMBm@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.