Skip to content

Conversation

@jmealo
Copy link
Contributor

@jmealo jmealo commented Sep 21, 2015

This PR includes @djanowski's Node.js 4 compatibility work and a small fix building on OSX 10.8+.

nodejs/node#2798

Replaces #8

@jmealo jmealo mentioned this pull request Sep 21, 2015
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

#7

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@bobrik: I didn't even look at that PR because of the title >_<. Isn't my commit safer as it leaves all existing logic in and fixes the problem?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It still changes liblzf and I still believe that this change should go upstream (liblzf itself)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It definitely should, I'm just trying to help the community transition to
Node 4.0. I will try to do this later today.

On Mon, Sep 21, 2015 at 9:15 AM, Ian Babrou notifications@github.com
wrote:

In src/lzf/lzfP.h
#9 (comment):

@@ -144,7 +144,9 @@ using namespace std;

if defined (WIN32)

define LZF_USE_OFFSETS defined(_M_X64)

else

-# if __cplusplus > 199711L
+# if MAC_OS_X_VERSION_MIN_REQUIRED >= MAC_OS_X_VERSION_10_8

It still changes liblzf and I still believe that this change should go
upstream (liblzf itself)


Reply to this email directly or view it on GitHub
https://github.com/Topface/node-lzf/pull/9/files#r39968314.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jmealo did you write to the author of Liblzf?

@fadimko fadimko changed the title Node 4.0 compatibility and OSX build fixes OSX build fixes Nov 9, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

4 participants