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

Update Bazel rules_foreign_cc from 0.4.0 to 0.8.0. #624

Merged
merged 1 commit into from
Jul 29, 2022

Conversation

shaper
Copy link
Contributor

@shaper shaper commented Jul 29, 2022

As part of building CVC5 for #622 I found that our rules_foreign_cc library seems quite dated. The new version allows specifying copts in the cmake rule, and there are surely other updates of potential use as well.

@shaper shaper requested a review from markww July 29, 2022 15:35
Copy link
Contributor

@markww markww left a comment

Choose a reason for hiding this comment

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

LGTM, but you need to run buildifier to fix internal checks.

@shaper shaper merged commit c46888b into google-research:main Jul 29, 2022
@shaper shaper deleted the update_rfcc branch July 29, 2022 17:21
@harsha-mandadi
Copy link
Collaborator

This version change has caused my build to fail on Mac with following error.

./lib/findprog-in.c:137:25: error: implicit declaration of function 'eaccess' is invalid in C99 [-Werror,-Wimplicit-function-declaration]
                    if (eaccess (progpathname, X_OK) == 0)
                        ^
./lib/findprog-in.c:137:25: note: did you mean 'access'?
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/unistd.h:431:6: note: 'access' declared here
int      access(const char *, int);
         ^
./lib/findprog-in.c:211:21: error: implicit declaration of function 'eaccess' is invalid in C99 [-Werror,-Wimplicit-function-declaration]
                if (eaccess (progpathname, X_OK) == 0)

Looks like error is related to eaccess being called before it is declared. It fails on something not related to raksha. Have you encountered this or is this only for mac users?

@markww
Copy link
Contributor

markww commented Aug 3, 2022

This looks like a warning that has been upgraded to an error. We should probably just disable -Werror for third party code; I'm surprised it's on in this build in the first place.

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.

3 participants