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

unix/freedos: djgpp errno.h have no ENOTSUP, so define it as "next number" #1959

Closed

Conversation

pohmelie
Copy link
Contributor

@pohmelie pohmelie commented Apr 2, 2016

#1956 solution(?)

This compiles just fine with djgpp.
42, cause 41 is the last one.

@@ -36,3 +36,6 @@

// djgpp dirent struct does not have d_ino field
#undef _DIRENT_HAVE_D_INO

// djgpp errno.h have no ENOTSUP
Copy link
Contributor

Choose a reason for hiding this comment

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

Usual idiom to do such things is to write such defined in #ifndef ENOTSUP. (What if next version of djgpp will define it?)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@pfalcon
So, I should include errno.h in mpconfigport_freedos.h?

Copy link
Contributor

Choose a reason for hiding this comment

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

Hmm, yes, I'd rather say yes, than no.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@pfalcon, ok, updated.

@pfalcon
Copy link
Contributor

pfalcon commented Apr 3, 2016

I also overlooked "next value". Not too robust. Along the lines of discussion above, I changed that to Linux value (88). Merged, thanks!

@pfalcon pfalcon closed this Apr 3, 2016
tannewt added a commit to tannewt/circuitpython that referenced this pull request Jun 22, 2019
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.

None yet

2 participants