-
Notifications
You must be signed in to change notification settings - Fork 269
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
[Kirkstone] - gstreamer version 1.20.3 and "-D_TIME_BITS=64 -D_FILE_OFFSET_BITS=64" build options #1725
Comments
If the patch you have mention fix the issue you can submit it as backport in
something like that will do the job:
|
Actually the issue is already fixed in gstreamer1.0_1.22.0, as I said the patch mentionned is included in gstreamer1.0_1.20.5. |
Sorry I got confused with the version, the patch should be applied on the
About the updated on kirk branch, I have no idea about when gstreamer imx fork will be updated. |
I think it would be a good idea to prepare a PR. Could you please prepare it? |
Hi @marlene-jacquier, can you make a PR with a patch file as @quaresmajose suggests? |
PR created: #1737 |
gstreamer1.0: use futex_time64 syscall if available (32-bit systems) #1725
There is an issue in official gstreamer version when building it with "-D_TIME_BITS=64 -D_FILE_OFFSET_BITS=64" options. This has been fixed in gstreamer version 1.20.5 with the following commit: https://gitlab.freedesktop.org/gstreamer/gstreamer/-/commit/94a0d579d7c987dd3fb40eaa579fb6dde8fdc6f4
The symptom is that a gstreamer pipeline is in this case taking 80% of the CPU without the patch, no issue when using 32 bits time.
Is there a plan to integrate at least gstreamer 1.20.5 on the kirkstone branch. to avoid patching it ?
The text was updated successfully, but these errors were encountered: