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

Test for libcap and gcc isn't robust enough #35

Open
hmaarrfk opened this issue Nov 13, 2021 · 3 comments · May be fixed by #36
Open

Test for libcap and gcc isn't robust enough #35

hmaarrfk opened this issue Nov 13, 2021 · 3 comments · May be fixed by #36

Comments

@hmaarrfk
Copy link

When trying to build the package on a non-standard system, the helpful error messages make the build process fail prematurely.

The issue is that on certain build system, one needs to specify the CFLAGS and other related parameters for gcc or cpp to find the appropriate headers.

This happens on conda-forge where I had to patch out the checks during the install procedure.

I understand that these are meant to guide to the user into installing the project correctly, but maybe we can decrease them to warnings?

Let me know how I can help.

Reference to some failing build logs (for unrelated issues)

conda-forge/staged-recipes#16926

@seveas
Copy link
Owner

seveas commented Nov 13, 2021

For the kernel checks, there's an envvar you can set to bypass them. I'd accept a pr that does something similar for the compiler/header checks.

@hmaarrfk
Copy link
Author

interesting. ok. i can probably do that.

also, i think you need kernel 2.6 now that you have FORCE

&& arg2 != PR_SPEC_FORCE_DISABLE

you might also be able to distribute wheels. i think the standard might define a Linux version that is old enough for your project.

@hmaarrfk
Copy link
Author

I had a serious brainfart with the kernel version.

I guess conda-forge does a few hacky things like they may install a new kernel, but expose older kernel versions to the libraries. I got things working on our system.

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 a pull request may close this issue.

2 participants