Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add support for z/OS #520

Closed
wants to merge 12 commits into from
Closed

add support for z/OS #520

wants to merge 12 commits into from

Conversation

gabylb
Copy link
Contributor

@gabylb gabylb commented Mar 12, 2021

Include the following changes specific to z/OS:

  • remove O2 and O3 opts due to compile issue causing intermittent failure
  • support setting javahome
  • set compiler flags based on compiler and node versions
  • link to libjvm.x - find Java's lib_dir to link to libjvm.x instead of assuming users have their LDFLAGS env variable set to that path

and:

gabylb and others added 12 commits November 18, 2019 13:28
This is to workaround previous (to v14) versions of node
and a compiler bug affected by those versions, as follows:

- v8 (ships with D190508), requires -U_VARARG_EXT_ and no-opt
- v12 (ships with D191122), requires no-opt
- v14 (ships with D191122), no workaround needed.
Find Java's lib_dir to link to libjvm.x, instead of assuming
users have their LDFLAGS env variable set to that path.
zos: rebase and apply custom compile flags to support Node v8, v12 and v14
The destructor InstanceMethodCallBaton() calls m_javaObject->Unref()
which aborts when m_javaObject is NULL.

Affects at least `npm test` from `node-jdbc` npm, which aborts in
test `testcreatetable`:

(abort) [0x26C7C640]
(__cxa_end_catch) [0x2E2CC414]
(InstanceMethodCallBaton::~InstanceMethodCallBaton()+0x140) [0x2E2CD2A4]
(Nan::AsyncWorker::Destroy()@AF61_58+0x28) [0x2E2CCE4C]
(Nan::AsyncWorker::Destroy()+0x18) [0x2E2C9F12]
(Nan::AsyncExecuteComplete(uv_work_s*)+0x4e) [0x27DB5430]
...
src: verify pointer before calling its method
@joeferner
Copy link
Owner

merged manually because of merge conflicts

@joeferner joeferner closed this Jul 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants