-
Notifications
You must be signed in to change notification settings - Fork 422
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
Building failed #288
Comments
Take a look at #262. You will need to change the code after clone yourself.. |
After following this commit to change the code, I still got some errors:
|
If you used that commit as-is its code changes are likely not kicking in because they pertain kernel versions 6.x and are guarded by the #defines. Looking at your compile output you are running 5.14 (with backported code from 6.x it seems). Try removing the #defines from the commit such that the code for 6.x remains. |
I do not see the #defines in the commit. |
Sorry, I meant #if/#ifdef blocks. |
I manually added the code changes and got some errors:
|
Progress. If you take a look at the same commit, where you took the code from, there are couple of more files you might need to change. |
Is there a patch file to apply all the commits? I am unable to change all the commit code manually. |
There are 4-5 lines of code you need to change across three files. I think that is a really small patch to do manually. Nevertheless, this post https://stackoverflow.com/questions/6188591/download-github-pull-request-as-unified-diff#6188624 explains how to get a diff/patch file from a PR or commit on github. Beware that after you apply the patch, you will need to manually deal with the #if/#ifdef lines that were added by the patch. |
I followed the post, but it did not work:
|
I still got this error:
|
Failing at this line:
makes me think that this part of the 6.x kernel code was not not backported to your kernel version. What happens if you do not include this change from the commit? In other words, keep the original line:
|
This fixed the issue:
|
I guess what you're seeing is similar to issues observed as so far: Hard to say which is it going to be, case by case, but trial and error approach, as performed so far, should work for the outstanding errors. Good luck! |
I see your recovery is very good, can I ask you a question? I need to compile the xdma driver in the Kylin V10 system. Has anyone adapted the xdma driver in Kylin? I have a problem now. When the host computer operates pcie xdma, the system will freeze. After checking the log, I found that pcie is stuck. What is the situation when pcie (pcie ff) is stuck? Have you encountered this before? |
I got some errors when building this package on AlmaLinux 9.4. Please help.
The text was updated successfully, but these errors were encountered: