Repository navigation
Adding TCP_FASTOPEN_CONNECT prevents compiling on older systems #54604
Description
Activity
In the mean time, if someone can tell me what the latest version of nodejs is that does not need TCP_FASTOPEN_CONNECT so I can build that?
TCP_FASTOPEN_CONNECTis introduced inc-ares@1.33.0which landed in22.7.0.c-ares@1.33.1which fixedTCP_FASTOPEN_CONNECTon unsupported platform which landed in yesterday atmain.In the mean time, if someone can tell me what the latest version of nodejs is that does not need TCP_FASTOPEN_CONNECT so I can build that?
I believe the previous version
22.6.0should be fine to use.abcbarryn commented
on Aug 28, 2024 on Aug 28, 2024 via email · Hidden as off-topicAuthorshow commentMore actions- Thank you very much.On 2024-08-28 02:40, KaKa wrote: #54549 [1] is the one that will disable TCP_FASTOPEN_CONNECT on unsupported platform. Merged in yesterday. > In the mean time, if someone can tell me what the latest version of > nodejs is that does not need TCP_FASTOPEN_CONNECT so I can build that? I believe the previous version 22.6.0 should be fine to use. -- Reply to this email directly, view it on GitHub [2], or unsubscribe [3]. You are receiving this because you authored the thread.Message ID: ***@***.***>
I will try 22.6.0 and wait for a new release with this fixed.
PS: Someone needs to delete/disable PiaoR's account. It looks like his message was deleted, but he tried to send me a link to a virus.
- addedcaresIssues and PRs related to the c-ares dependency or the cares_wrap binding.Issues and PRs related to the c-ares dependency or the cares_wrap binding.
on Aug 28, 2024 I will try 22.6.0 and wait for a new release with this fixed.
Should this issue be closed?
I have not tested the patch, I am just going to fall back to 22.6.0.
github-actions commented
on Apr 28, 2026 on Apr 28, 2026 – with GitHub ActionsContributorMore actionsThis 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.- addedstaleIssues 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 Apr 28, 2026 I no longer have or use the system on which I encountered this issue so I am unable to test...
- removedstaleIssues 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 Apr 29, 2026 github-actions commented
on Jul 28, 2026 on Jul 28, 2026 – with GitHub ActionsContributorMore actionsThis issue has been marked as stale due to 90 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.- addedstaleIssues 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 Jul 28, 2026
Version
v22.7.0
Platform
Subsystem
No response
What steps will reproduce the bug?
Attempt to compile nodejs on an older system that lacks support for TCP_FASTOPEN_CONNECT.
How often does it reproduce? Is there a required condition?
All the time.
What is the expected behavior? Why is that the expected behavior?
Be able to compile/build nodejs from source.
What do you see instead?
error: ‘TCP_FASTOPEN_CONNECT’ undeclared (first use in this function)
Multiple instances of this
Additional information
Please implement an option to disable this feature if the target platform does not support it.
Also, read this: https://blog.apnic.net/2021/07/05/tcp-fast-open-not-so-fast/