Skip to content

build: --disable-single-executable-application results in link failure #51730

Description

@mscdex

Version

At least v18.x and by the looks of it, everything since

Platform

No response

Subsystem

No response

What steps will reproduce the bug?

Configuring with --disable-single-executable-application results in a failed build during the final build steps because the functionality is always being referenced regardless of compile-time configuration and gives an error about no _register_sea.

Additionally I believe I saw some compiled test failures that happened after the above failures, so it seems like there is even more stuff broken with that configuration.

How often does it reproduce? Is there a required condition?

No response

What is the expected behavior? Why is that the expected behavior?

No response

What do you see instead?

Additional information

No response

Activity

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.single-executableIssues and PRs related to single-executable applications.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions