-
Notifications
You must be signed in to change notification settings - Fork 50
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
Make errors — MacOS Catalina, v10.15.7 #20
Comments
thanks for reporting. I have not compiled it on/for Mac. Perhaps you can file a regular pull request, please, so that someone else can pull your request and try that. I am very sorry, that I cannot test it at the moment. |
It's easier to change the Makefile: -CFLAGS = However, I'm not sure how to ifdef that so it only happens on the mac, and turning off that warning seems like a bad idea overall. |
I am using @EDePasquale's changes to run |
Of course, you can issue a pull request, perhaps best in form of a well-named branch. |
You don't need a Mac to verify the problem or its fix. You can add
Right, don't disable the error. Apple and LLVM.org have made it an error in their respective clangs for a reason. It needs to be fixed properly. Much more information at https://trac.macports.org/wiki/WimplicitFunctionDeclaration. |
Fixes Wikinaut#20 Co-authored-by: EDePasquale <[email protected]>
A sequence of errors occurred during installation when calling the 'make' command. In general, most of them seem to be related to implicit declarations, examples:
[-Werror,-Wimplicit-function-declaration]
return re(fd, M, D); /* SUN: need to find a even point */
To correct this for my machine, I modified the files to either remove or move the if blocks beginning with 'ifdef_WIN32', though there is likely a better solution that doesn't affect other non-Windows operating systems. To make it successfully build on my machine I changed the following:
I may have missed a change or 2 while writing this issue, but these same actions can be used to correct other similar errors.
The text was updated successfully, but these errors were encountered: