-
Notifications
You must be signed in to change notification settings - Fork 903
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
Build Falco on ppc64le #1225
Build Falco on ppc64le #1225
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/assign @fntlnz |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi! Thanks for getting this in line, having ppc64le sounds exciting to us :)
Looking at this PR, seems that the relevant changes to build on ppc64le are in the CMake files, however the PR contains a lot of unrelated changes in other files that are probably the effect of some messed up rebase.
Please let me know how I can help
Once this is ready, I think that we can add a test runner for docker using |
Signed-off-by: sarveshtamba <[email protected]>
Signed-off-by: Amit Shirodkar <[email protected]> revert changes in falco-driver-loader for build on ppc64le Signed-off-by: Amit Shirodkar <[email protected]>
INSTALL_COMMAND "") | ||
|
||
if("${CMAKE_SYSTEM_PROCESSOR}" STREQUAL "ppc64le") | ||
ExternalProject_Add( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I love how you used moonjit here. I think this is worth discussing in the community call to see if we can just use moonjit for everything at this point. I'm adding a discussion point for today.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm trying to understand why we need to use moonjit here and consolidate if there's a valid reason.
I see that luait is still maintained despite what they say on the moonjit page.
URL "https://github.com/draios/sysdig/archive/${SYSDIG_VERSION}.tar.gz" | ||
# URL_HASH SHA256=bd09607aa8beb863db07e695863f7dc543e2d39e7153005759d26a340ff66fa5 | ||
# we need to change the case of the luaL_reg to luaL_Reg since we are using Moonjit | ||
PATCH_COMMAND sed -i "s/luaL_reg/luaL_Reg/g" ${SYSDIG_SOURCE_DIR}/userspace/libsinsp/chisel.cpp && sed -i "s/luaL_reg/luaL_Reg/g" ${SYSDIG_SOURCE_DIR}/userspace/libsinsp/lua_parser.cpp && sed -i "s/luaL_getn/lua_objlen /g" ${SYSDIG_SOURCE_DIR}/userspace/libsinsp/lua_parser_api.cpp |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The only thing that changes here is the patch command.
I think it's better if we just do the if for the patch command and not for the whole external project.
Next steps:
|
@kris-nova @fntlnz I wasn't able to build raptorjit on PowerPC , so on power, falco builds only with moonjit. |
I tested this and works very well. Moonjit is the right option in my opinion. |
@sarveshtamba: PR needs rebase. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/milestone 0.28.1 |
Issues go stale after 90d of inactivity. Mark the issue as fresh with Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with Provide feedback via https://github.com/falcosecurity/community. /lifecycle stale |
/milestone 0.32.0 |
Stale issues rot after 30d of inactivity. Mark the issue as fresh with Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with Provide feedback via https://github.com/falcosecurity/community. /lifecycle rotten |
Rotten issues close after 30d of inactivity. Reopen the issue with Mark the issue as fresh with Provide feedback via https://github.com/falcosecurity/community. |
@poiana: Closed this PR. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Signed-off-by: sarveshtamba [email protected]
What type of PR is this?
/kind feature
Any specific area of the project related to this PR?
/area build
What this PR does / why we need it: Support to build Falco on ppc64le.
Which issue(s) this PR fixes: Support to build Falco on ppc64le.
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?: