public inbox for buildroot@busybox.net
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 12826] nodejs-12.16.1: error: 'uv_sleep' was not declared in this scope
Date: Sun, 17 May 2020 18:52:38 +0000	[thread overview]
Message-ID: <bug-12826-163-761OKIbcTV@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-12826-163@https.bugs.busybox.net/>

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

Thomas Petazzoni <thomas.petazzoni@free-electrons.com> changed:

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

--- Comment #6 from Thomas Petazzoni <thomas.petazzoni@free-electrons.com> ---
I am sorry, but neither Peter Seiderer nor myself have been able to reproduce
the issue on 2020.02.1. I tested exactly the first defconfig you posted, and it
builds fine.

The libuv version 2020.02.1 does implement uv_sleep(), both the libuv package
and the libuv shipped with nodejs, so I don't see how your build failure could
happen.

Are you sure you did a full rebuild with 2020.02.1 ?

-- 
You are receiving this mail because:
You are on the CC list for the bug.

      parent reply	other threads:[~2020-05-17 18:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-29 10:18 [Buildroot] [Bug 12826] New: nodejs-12.16.1: error: 'uv_sleep' was not declared in this scope bugzilla at busybox.net
2020-04-29 12:23 ` [Buildroot] [Bug 12826] " bugzilla at busybox.net
2020-04-29 18:08 ` bugzilla at busybox.net
2020-04-29 20:06 ` bugzilla at busybox.net
2020-05-16 14:20 ` bugzilla at busybox.net
2020-05-16 14:23 ` bugzilla at busybox.net
2020-05-16 15:56 ` bugzilla at busybox.net
2020-05-17 18:52 ` bugzilla at busybox.net [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-12826-163-761OKIbcTV@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@busybox.net \
    /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