Skip to content
This repository has been archived by the owner on Sep 1, 2023. It is now read-only.

workaround strerror_r ignoring return value warning #40

Merged
merged 3 commits into from
Mar 17, 2014

Conversation

breznak
Copy link
Member

@breznak breznak commented Mar 11, 2014

fix (workaround) issue #39
because of Werror, just a hack. Affected: ubuntu 13.04 gcc

@breznak
Copy link
Member Author

breznak commented Mar 11, 2014

here is the manpage http://man7.org/linux/man-pages/man3/strerror.3.html

I've tried using the POSIX (more portable) version, but it wouldn't do without further changes. So keeping as is for now.

@rhyolight
Copy link
Member

@scottpurdy Please review.

@rhyolight rhyolight added this to the Sprint 17 milestone Mar 14, 2014
@rhyolight rhyolight modified the milestones: Sprint 18, Sprint 17 Mar 14, 2014
@scottpurdy
Copy link
Contributor

I must be missing something in the manpage that explains this but why are we saving the return value to local variable retval but never actually using it? Why not just remove it?

@breznak
Copy link
Member Author

breznak commented Mar 15, 2014

That was the point of this PR (fix warning which errors with Werror). We
need strerror_r as it passes value to errorbuf to message ...
Retval is a dummy variable to satisfy the missing return value/unused
variable warning/error. See commit message for details please.

scottpurdy added a commit that referenced this pull request Mar 17, 2014
workaround strerror_r ignoring return value warning
@scottpurdy scottpurdy merged commit 7d1271c into numenta:master Mar 17, 2014
@breznak breznak deleted the fix_ubuntu_netbeans_cpp branch April 3, 2014 22:08
utensil referenced this pull request in david-ragazzi/nupic.core Apr 4, 2014
pettitda pushed a commit to pettitda/nupic.core that referenced this pull request Jun 3, 2016
breznak added a commit to breznak/nupic.core that referenced this pull request Jul 31, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants