10000 Solaris doesn't necessarily have stdint.h, use inttypes.h by jacquesg · Pull Request #184 · nodejs/http-parser · GitHub
[go: up one dir, main page]

Skip to content
This repository was archived by the owner on Nov 6, 2022. It is now read-only.

Solaris doesn't necessarily have stdint.h, use inttypes.h #184

Closed
wants to merge 1 commit into from
Closed

Solaris doesn't necessarily have stdint.h, use inttypes.h #184

wants to merge 1 commit into from

Conversation

jacquesg
Copy link
@jacquesg jacquesg commented Aug 5, 2014

Solaris doesn't necessarily have stdint.h, it's more portable to use sys/inttypes.h.

See:
http://wiki.opencsw.org/porting-faq#toc1

@indutny
Copy link
Member
indutny commented Aug 6, 2014

What about sys/types.h does it include it?

@jacquesg
Copy link
Author
jacquesg commented Aug 6, 2014

No, it doesn't include sys/types.h. sys/inttypes.h basically includes sys/int_types.h for user-land code. sys/int_types.h then defines uint8_t and friends.

@rmustacc
Copy link
rmustacc commented Aug 6, 2014

@jacquesg what version of Solaris are you trying to build against? In general, most of the node ecosystem requires illumos or Solaris 10, which based on your doc suggests that we'll always have stdint.h available.

@jacquesg
Copy link
Author
jacquesg commented Aug 6, 2014

I believe the error is coming from a Solaris 9 sparc machine. We use http parser in libgit2. I'm the maintainer of Git-Raw, the perl bindings. Got the build failures by looking at the ActiveState perl builds.

Sent from my iPhone

On 06 Aug 2014, at 21:53, Robert Mustacchi notifications@github.com wrote:

@jacquesg what version of Solaris are you trying to build against? In general, most of the node ecosystem requires illumos or Solaris 10, which based on your doc suggests that we'll always have stdint.h available.


Reply to this email directly or view it on GitHub.

@tjfontaine
Copy link
Contributor

I think then we want to constrain this further if possible to S9 and older versions of solaris

@indutny
Copy link
Member
indutny commented Aug 24, 2014

So, @tjfontaine should I land it?

@jacquesg
Copy link
Author

@tjfontaine I don't think there is any value in constraining this to Solaris 9 and older. The fix works for all versions, introducing additional conditional logic IMHO would be senseless.

@jasnell
Copy link
Member
jasnell commented Oct 26, 2015

@indutny ... I assume this one is likely safe to close?

@jacquesg
Copy link
Author

Is there any reason this cannot be merged?

@indutny
Copy link
Member
indutny commented Dec 26, 2016

@jasnell I have no idea, we clearly need input of Solaris people here.

@jasnell
Copy link
Member
jasnell commented Dec 26, 2016

hmm... I'm not a solaris person either :-/ ... @misterdjules ideas?

@rmustacc
Copy link
rmustacc commented Dec 26, 2016 via email

@jacquesg
Copy link
Author

I've constrained this to Solaris 9.

@jacquesg
Copy link
Author

Anything else required to get this merged?

@derekargueta
Copy link
Contributor

Is this PR still being considered?

@jacquesg
Copy link
Author
jacquesg commented May 4, 2020

It is still relevant, atleast for me.

bnoordhuis pushed a commit that referenced this pull request May 4, 2020
PR-URL: #184
Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
@bnoordhuis
Copy link
Member

I somehow managed to completely overlook this PR for nearly six years, sorry about that. Merged just now in 55e736c, thanks Jacques!

@bnoordhuis bnoordhuis closed this May 4, 2020
@jacquesg jacquesg deleted the solaris branch May 4, 2020 10:04
ploxiln pushed a commit to ploxiln/http-parser that referenced this pull request May 4, 2020
PR-URL: nodejs#184
Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants
0