Djam/kernel-5.15
1
0
Fork 0
mirror of https://abf.rosa.ru/djam/kernel-5.15.git synced 2025-02-24 02:52:55 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
kernel-5.15/perf-python-ext-link-with-dl.patch

23 lines
746 B
Diff
Raw Normal View History

Keep the patches in the kernel project instead of a separate one Earlier, the patches were kept in the respective branches of a separate project, https://abf.io/soft/kernel-patches-and-configs. And before that - in the custom tarballs. Now all the patches are kept here along with the spec file and are applied the default way rather than by separate scripts. This should make the maintenance of the patches as well as the experiments with the new ones a lot easier. The previous scheme seemed to offer a bit more flexibility (different patch sets for different cases) at the cost of maintenance. But as it turned out, that flexibility was not worth it and was rarely used, at most.
2016-07-26 11:24:24 +03:00
diff --git a/tools/perf/util/setup.py b/tools/perf/util/setup.py
Updated to version 4.17.4
2018-07-05 21:40:11 +03:00
index 001be4f9d3b9..b49aa54baaad 100644
Keep the patches in the kernel project instead of a separate one Earlier, the patches were kept in the respective branches of a separate project, https://abf.io/soft/kernel-patches-and-configs. And before that - in the custom tarballs. Now all the patches are kept here along with the spec file and are applied the default way rather than by separate scripts. This should make the maintenance of the patches as well as the experiments with the new ones a lot easier. The previous scheme seemed to offer a bit more flexibility (different patch sets for different cases) at the cost of maintenance. But as it turned out, that flexibility was not worth it and was rarely used, at most.
2016-07-26 11:24:24 +03:00
--- a/tools/perf/util/setup.py
+++ b/tools/perf/util/setup.py
Updated to version 4.17.4
2018-07-05 21:40:11 +03:00
@@ -31,6 +31,9 @@ cflags += ['-fno-strict-aliasing', '-Wno-write-strings', '-Wno-unused-parameter'
if cc != "clang":
cflags += ['-Wno-cast-function-type' ]
Keep the patches in the kernel project instead of a separate one Earlier, the patches were kept in the respective branches of a separate project, https://abf.io/soft/kernel-patches-and-configs. And before that - in the custom tarballs. Now all the patches are kept here along with the spec file and are applied the default way rather than by separate scripts. This should make the maintenance of the patches as well as the experiments with the new ones a lot easier. The previous scheme seemed to offer a bit more flexibility (different patch sets for different cases) at the cost of maintenance. But as it turned out, that flexibility was not worth it and was rarely used, at most.
2016-07-26 11:24:24 +03:00
+libs = getenv('LIBS', '').split()
+libs += ['dl']
+
src_perf = getenv('srctree') + '/tools/perf'
build_lib = getenv('PYTHON_EXTBUILD_LIB')
build_tmp = getenv('PYTHON_EXTBUILD_TMP')
Updated to version 4.17.4
2018-07-05 21:40:11 +03:00
@@ -48,6 +51,7 @@ perf = Extension('perf',
Keep the patches in the kernel project instead of a separate one Earlier, the patches were kept in the respective branches of a separate project, https://abf.io/soft/kernel-patches-and-configs. And before that - in the custom tarballs. Now all the patches are kept here along with the spec file and are applied the default way rather than by separate scripts. This should make the maintenance of the patches as well as the experiments with the new ones a lot easier. The previous scheme seemed to offer a bit more flexibility (different patch sets for different cases) at the cost of maintenance. But as it turned out, that flexibility was not worth it and was rarely used, at most.
2016-07-26 11:24:24 +03:00
include_dirs = ['util/include'],
extra_compile_args = cflags,
extra_objects = [libtraceevent, libapikfs],
+ libraries = libs,
)
setup(name='perf',
Reference in a new issue Copy permalink