All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 14711] nodjs build problem missing bzip
Date: Sat, 09 Apr 2022 17:02:31 +0000	[thread overview]
Message-ID: <bug-14711-163-Fxumpr6Roe@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-14711-163@https.bugs.busybox.net/>

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

Arnout Vandecappelle <arnout@mind.be> changed:

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

--- Comment #7 from Arnout Vandecappelle <arnout@mind.be> ---
> Problem solved by adding BR2_PACKAGE_HOST_PYTHON3=y and BR2_PACKAGE_HOST_PYTHON3_BZIP2=y in the config file and did a full rebuild.

These should be enabled automatically when BR2_PACKAGE_HOST_NODEJS is enabled.

So I'm going to assume that you did 'make host-nodejs' without selecting
BR2_PACKAGE_HOST_NODEJS, and close this bug as invalid.

If, however, you somehow did run into this problem without running 'make
host-nodejs' (and without an external package that depends on host-nodejs
without selecting it), please reopen.

-- 
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-04-09 17:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-28 13:46 [Buildroot] [Bug 14711] New: nodjs build problem missing bzip bugzilla
2022-03-28 13:50 ` [Buildroot] [Bug 14711] " bugzilla
2022-03-28 19:03 ` bugzilla
2022-03-28 19:17 ` bugzilla
2022-03-30  5:15 ` bugzilla
2022-03-30  5:33 ` bugzilla
2022-03-31  4:16 ` bugzilla
2022-04-09 17:02 ` 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-14711-163-Fxumpr6Roe@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.