Skip to content

Error in building the Linux x86 library #41427

Description

@The2Alert

Version

16.13.0

Platform

Linux DESKTOP-GFGGCIN 5.10.16.3-microsoft-standard-WSL2 #1 SMP Fri Apr 2 22:23:49 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Error

Error in building the Linux x86 library


Screenshots of the problem:






Versions:


Activity

  1. richardlau commented on Jan 7, 2022

    @richardlau
    Member

    That's odd... it looks like despite the configure flags it was trying to build the x64 version of push_registers_asm.cc.
    For comparison, this is the successful log of the x86 16.13.1 build from the unofficial builds project which shows the ia32 version of the file being compiled:
    https://unofficial-builds.nodejs.org/logs/202112011619-v16.13.1/x86.log

  2. The2Alert commented on Jan 7, 2022

    @The2Alert
    Author

    I have been building x64 and it is going without any problems

  3. The2Alert commented on Jan 7, 2022

    @The2Alert
    Author

    But with x86, here's the problem

  4. added
    buildIssues and PRs related to Node.js builds or CI infrastructure.
    on Jan 7, 2022
  5. The2Alert commented on Jan 8, 2022

    @The2Alert
    Author

    the problem remains unresolved!

  6. The2Alert commented on Jan 14, 2022

    @The2Alert
    Author

    Build shared library node 16.13.2 ia32:

    Screenshot_1
    Screenshot_2

  7. The2Alert commented on Jan 14, 2022

    @The2Alert
    Author

    suggest a solution to the problem

  8. The2Alert commented on Jan 18, 2022

    @The2Alert
    Author

    Issue resolved.

    Platform: Linux dev2alert-virtualbox 5.10.0-10-686 #1 SMP Debian 5.10.84-1 (2021-12-08) i686 GNU/Linux
    But it remains a problem for Ubuntu 20 x64.

  9. github-actions commented on Jun 25, 2026

    @github-actions
    Contributor

    This issue has been marked as stale due to 210 days of inactivity.
    It will be automatically closed in 30 days if no further activity occurs. If this is still relevant, please leave a comment or update it to keep it open.

  10. added
    staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.
    on Jun 25, 2026
  11. github-actions commented on Jul 26, 2026

    @github-actions
    Contributor

    This issue has been automatically closed after 30 days of inactivity following its stale status (no activity for a total of 120 days).
    If this is still relevant, feel free to reopen it or leave a comment with additional details so we can continue the discussion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    buildIssues and PRs related to Node.js builds or CI infrastructure.staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions