Skip to content

Conversation

@danbev
Copy link
Contributor

Currently when building with the following configuration options:
$ ./configure --without-ssl && make

The following link error is reported:

Undefined symbols for architecture x86_64:
"node::openssl_config", referenced from:
node::Init(int*, char const**, int*, char const***) in node.o
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see
invocation)

Adding an HAVE_OPENSSL directive around this code allows the build to
pass.

Checklist
  • commit message follows commit guidelines
Affected core subsystem(s)

src

Currently when building with the following configuration options: $ ./configure --without-ssl && make The following link error is reported: Undefined symbols for architecture x86_64: "node::openssl_config", referenced from: node::Init(int*, char const**, int*, char const***) in node.o ld: symbol(s) not found for architecture x86_64 clang: error: linker command failed with exit code 1 (use -v to see invocation) Adding an HAVE_OPENSSL directive around this code allows the build to pass.
@nodejs-github-botnodejs-github-bot added the c++ Issues and PRs that require attention from people who are familiar with C++. label Feb 28, 2017
@addaleaxaddaleax added the lib / src Issues and PRs related to general changes in the lib or src directory. label Feb 28, 2017
@mscdexmscdex added build Issues and PRs related to build files or the CI. openssl Issues and PRs related to the OpenSSL dependency. labels Feb 28, 2017
@richardlau
Copy link
Member

cc @sam-github

danbev added a commit to danbev/node that referenced this pull request Mar 2, 2017
Currently when building with the following configuration options: $ ./configure --without-ssl && make The following link error is reported: Undefined symbols for architecture x86_64: "node::openssl_config", referenced from: node::Init(int*, char const**, int*, char const***) in node.o ld: symbol(s) not found for architecture x86_64 clang: error: linker command failed with exit code 1 (use -v to see invocation) Adding an HAVE_OPENSSL directive around this code allows the build to pass. PR-URL: nodejs#11618 Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: Sam Roberts <[email protected]>
@danbev
Copy link
ContributorAuthor

Landed in e1d8899

@danbevdanbev closed this Mar 2, 2017
@danbevdanbev deleted the add-have_openssl-directive branch March 2, 2017 06:37
@evanlucas
Copy link
Contributor

This is not landing cleanly on v7.x-staging. Mind opening a backport PR?

@danbev
Copy link
ContributorAuthor

danbev commented Mar 7, 2017 via email

@jasnelljasnell mentioned this pull request Apr 4, 2017
danbev added a commit to danbev/node that referenced this pull request Apr 11, 2017
Currently when building with the following configuration options: $ ./configure --without-ssl && make The following link error is reported: Undefined symbols for architecture x86_64: "node::openssl_config", referenced from: node::Init(int*, char const**, int*, char const***) in node.o ld: symbol(s) not found for architecture x86_64 clang: error: linker command failed with exit code 1 (use -v to see invocation) Adding an HAVE_OPENSSL directive around this code allows the build to pass. PR-URL: nodejs#11618 Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: Sam Roberts <[email protected]>
danbev added a commit to danbev/node that referenced this pull request May 30, 2017
Currently when building with the following configuration options: $ ./configure --without-ssl && make The following link error is reported: Undefined symbols for architecture x86_64: "node::openssl_config", referenced from: node::Init(int*, char const**, int*, char const***) in node.o ld: symbol(s) not found for architecture x86_64 clang: error: linker command failed with exit code 1 (use -v to see invocation) Adding an HAVE_OPENSSL directive around this code allows the build to pass. PR-URL: nodejs#11618 Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: Sam Roberts <[email protected]>
@gibfahngibfahn mentioned this pull request Jun 15, 2017
3 tasks
@gibfahn
Copy link
Member

Should this be backported to v6.x-staging? If yes please follow the guide and raise a backport PR, if no let me know or add the dont-land-on label.

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

Labels

buildIssues and PRs related to build files or the CI.c++Issues and PRs that require attention from people who are familiar with C++.lib / srcIssues and PRs related to general changes in the lib or src directory.opensslIssues and PRs related to the OpenSSL dependency.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

11 participants

@danbev@richardlau@evanlucas@gibfahn@sam-github@bnoordhuis@jasnell@addaleax@cjihrig@mscdex@nodejs-github-bot