Error in building the Linux x86 library #41427

Activity

1. richardlau commented on Jan 7, 2022

   

   richardlau

   on Jan 7, 2022

   Member

   More actions

   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

   on Jan 7, 2022

   Author

   More actions

   I have been building x64 and it is going without any problems
3. The2Alert commented on Jan 7, 2022

   

   The2Alert

   on Jan 7, 2022

   Author

   More actions

   But with x86, here's the problem
4. Mesteery

   added

   buildIssues and PRs related to Node.js builds or CI infrastructure.Issues and PRs related to Node.js builds or CI infrastructure.

   on Jan 7, 2022
5. The2Alert commented on Jan 8, 2022

   

   The2Alert

   on Jan 8, 2022

   Author

   More actions

   the problem remains unresolved!
6. The2Alert commented on Jan 14, 2022

   

   The2Alert

   on Jan 14, 2022

   Last edited by The2Alert

   Author

   More actions

   Build shared library node 16.13.2 ia32:

   
   
7. The2Alert commented on Jan 14, 2022

   

   The2Alert

   on Jan 14, 2022

   Author

   More actions

   suggest a solution to the problem
8. The2Alert commented on Jan 18, 2022

   

   The2Alert

   on Jan 18, 2022

   Author

   More actions

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

   on Jun 25, 2026 – with GitHub Actions

   Contributor

   More actions

   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. github-actions

    added

    staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.Issues 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-actionsbot

    on Jul 26, 2026 – with GitHub Actions

    Contributor

    More actions

    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.
12. github-actions

    closed this as not plannedon Jul 26, 2026