You are not logged in.
Hi everyone!
Please, I need help with an update to the package python311. Particularly, in the package version (pkgver), because there is a new version in the official repository Python 3.11.10.
Also, I found a wrong package name in the "makedepends" list. Actually the package "bluez-libs" is used, and should be used the "boost-libs" pkg.
I don't know if is it necessary tag the maintainers, but I'll really appreciate the help with these changes.
Offline
Sorry, I forget something, is it possible add the flag "--enable-optimizations" to the configure process?. This is for clean temp files of the previous compilations.
This have the "Readme.rst" file:
Profile Guided Optimization
PGO takes advantage of recent versions of the GCC or Clang compilers. If used,
either via ``configure --enable-optimizations`` or by manually running
``make profile-opt`` regardless of configure flags, the optimized build
process will perform the following steps:The entire Python directory is cleaned of temporary files that may have
resulted from a previous compilation.An instrumented version of the interpreter is built, using suitable compiler
flags for each flavor. Note that this is just an intermediary step. The
binary resulting from this step is not good for real-life workloads as it has
profiling instructions embedded inside.After the instrumented interpreter is built, the Makefile will run a training
workload. This is necessary in order to profile the interpreter's execution.
Note also that any output, both stdout and stderr, that may appear at this step
is suppressed.The final step is to build the actual interpreter, using the information
collected from the instrumented one. The end result will be a Python binary
that is optimized; suitable for distribution or production installation.
Offline
Why in the world are you using that package? It shouldn't even exist as it does.
Just use the 'python' package in Extra. 3.12 didn't break that much, unless you've got a very specific use-case.
Last edited by Scimmia (2024-11-19 20:10:15)
Offline
Also, I found a wrong package name in the "makedepends" list. Actually the package "bluez-libs" is used, and should be used the "boost-libs" pkg.
Do you mean bluez-libs should be replaced by boost-libs in makedepends?
https://github.com/python/cpython/blob/ … e.ac#L2237
I don't know if is it necessary tag the maintainers, but I'll really appreciate the help with these changes.
Leave a comment on https://aur.archlinux.org/packages/python311
This is for clean temp files of the previous compilations.
Cleanup is already provided by makepkg see the -c and -C options.
Offline
Why in the world are you using that package? It shouldn't even exist as it does.
Just use the 'python' package in Extra. 3.12 didn't break that much, unless you've got a very specific use-case.
I need this version to run llm models using the mlc engine. I use the vulkan driver and miniconda envs give me errors in the execution.
Do you mean bluez-libs should be replaced by boost-libs in makedepends?
https://github.com/python/cpython/blob/ … e.ac#L2237
In a server mode environment this can open unexplored backdoors, but maybe I'm wrong.
Leave a comment on https://aur.archlinux.org/packages/python311
Done!, Thanks!
Cleanup is already provided by makepkg see the -c and -C options.
The 3.10 version has the flag "--enable-optimizations" and this not, in the "configure" process.
Last edited by wleivam (2024-11-19 22:48:23)
Offline
Besides, we would recommend using Python 3.11;
Have you tried running it with python 3.12 or python 3.13 (python 3.13 rebuild has started in staging repo, so it will enter extra in the next few months) ?
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
loqs wrote:Do you mean bluez-libs should be replaced by boost-libs in makedepends?
https://github.com/python/cpython/blob/ … e.ac#L2237In a server mode environment this can open unexplored backdoors, but maybe I'm wrong.
Do you mean having bluez-libs on the system during package build opens unexplored backdoors or building python's socket module with bluetooth support opens unexplored backdoors?
loqs wrote:Cleanup is already provided by makepkg see the -c and -C options.
The 3.10 version has the flag "--enable-optimizations" and this not, in the "configure" process.
Why must cleanup be performed by configure instead of makepkg?
Offline
Have you tried running it with python 3.12 or python 3.13 (python 3.13 rebuild has started in staging repo, so it will enter extra in the next few months) ?
I try with the 3.12, but I've gotten an error compiling the Apache TVM fork. The version 3.13 was released the last week, so no.
Do you mean having bluez-libs on the system during package build opens unexplored backdoors or building python's socket module with bluetooth support opens unexplored backdoors?
Both, I don't need the bluetooth working in my server, but again, maybe I'm wrong because is a personal use case.
Why must cleanup be performed by configure instead of makepkg?
The cleanup is the first step of the conf, the real target of this flag is:
The end result will be a Python binary
that is optimized; suitable for distribution or production installation.
Offline
Lone_Wolf wrote:Have you tried running it with python 3.12 or python 3.13 (python 3.13 rebuild has started in staging repo, so it will enter extra in the next few months) ?
I try with the 3.12, but I've gotten an error compiling the Apache TVM fork. The version 3.13 was released the last week, so no.
Building relax worked for me. Possibly a difference in the cmake options you used or what you have installed on your system?
Both, I don't need the bluetooth working in my server, but again, maybe I'm wrong because is a personal use case.
That makes sense for your use case but why make that the default if you do not know of any actual issues it introduces when it removes functionality? What functionality does adding boost-libs add to the build?
Offline
That makes sense for your use case but why make that the default if you do not know of any actual issues it introduces when it removes functionality?
I compiled the 3.11.10 version without that lib, and I had no problems, but you're right.
What functionality does adding boost-libs add to the build?
It's to get a better PyTorch's performance, but again, It's for a personal use case.
Offline