Search Criteria
Package Details: pyinstaller 6.6.0-2
Package Actions
Git Clone URL: | https://aur.archlinux.org/pyinstaller.git (read-only, click to copy) |
---|---|
Package Base: | pyinstaller |
Description: | Bundles a Python application and all its dependencies into a single package |
Upstream URL: | https://www.pyinstaller.org |
Licenses: | custom |
Submitter: | jackdroido |
Maintainer: | yochananmarqos |
Last Packager: | yochananmarqos |
Votes: | 47 |
Popularity: | 0.41 |
First Submitted: | 2012-06-13 22:56 (UTC) |
Last Updated: | 2024-04-16 15:58 (UTC) |
Dependencies (13)
- binutils
- pyinstaller-hooks-contribAUR (pyinstaller-hooks-contrib-gitAUR)
- python-altgraphAUR
- python-setuptools
- python-build (make)
- python-installer (python-installer-gitAUR) (make)
- python-wheel (make)
- python-pillow (python-pillow-gitAUR) (check)
- python-psutil (check)
- python-pytest (python-pytest7) (check)
- python-pytest-xdist (check)
- xmldiff (check)
- python-argcomplete (python-argcomplete-gitAUR) (optional) – tab completion for CLI tools
Required by (10)
- artemis3 (make)
- booru-downloader-git (make)
- cget (make)
- hascal-git (make)
- nile-git (make)
- ofinstaller-beans-git (make)
- pixelflasher (make)
- python-pyxel (optional)
- tf2cdownloader-git (make)
- xaur (make)
Latest Comments
1 2 3 4 5 Next › Last »
gir861 commented on 2024-04-18 06:00 (UTC) (edited on 2024-04-18 06:05 (UTC) by gir861)
Same here:
syyyr commented on 2024-04-17 08:20 (UTC)
It looks to me that the checksum for the source is wrong:
but the current checksum is: a37fa49f49232b27d87238e3c7b48b98e688d256c2667c2368d5366193d04775
yochananmarqos commented on 2024-03-27 14:59 (UTC)
Sorry guys, turns out I apparently screwed up merging the latest
makepkg.conf
pacnew.@chrisjbillington: Thanks, I've applied the diff.
chrisjbillington commented on 2024-03-27 02:17 (UTC)
The problem seems to be that as of pacman 6.1, released earlier this month, Arch's default
makepkg.conf
has-Wp,-D_FORTIFY_SOURCE=3
inCFLAGS
, and this conflicts with pyinstaller passing-D_FORTIFY_SOURCE=2
.To retain the stricter setting if it's set (which probably makes sense?), one might patch the pyinstaller bootloader build script:
fortify-source-fix.diff
:makepkg
succeeds for me after this change.Perhaps there is a more sensible way, but I think at least this identifies the problem. Not sure why some others aren't seeing this problem, as I would have expected the default makepkg.conf to be used in a clean chroot.
chrisjbillington commented on 2024-03-27 01:00 (UTC) (edited on 2024-03-27 01:01 (UTC) by chrisjbillington)
It's failing for me in a chroot as well.
I haven't built AUR packages in chroots before, so I may not be doing it right, but I'm seeing the same problem when I build as below (script at the bottom of this comment). I'm on Arch on an x86-64 system, is there anything from my system that propagates into a chroot like this? I do have custom stuff in LD_PRELOAD, but I'm running the below script with LD_PRELOAD unset (and PATH set conservatively) just in case:
LD_PRELOAD= PATH=/usr/local/bin:/usr/bin:/usr/local/sbin ./build.sh
I think maybe most of the "errors" are irrelevant, since they correspond to other lines that are output when you run makepkg that appear to indicate success:
I think it's might only the last one that is fatal:
libdl does exist:
Perhaps the error raised (
_FORTIFY_SOURCE" redefined
) when checking forlibdl
is causing that detection step to fail and be interpreted as libdl not being present?Anyway, here's how I'm building in a chroot, let me know if I'm doing anything wrong:
AmbassadorDave commented on 2024-03-26 21:35 (UTC) (edited on 2024-03-26 22:43 (UTC) by AmbassadorDave)
Same issue today as chrisjbilliington, full output matches his. Attempted update from 6.5.0-1 -> 6.5.0-2 using yay on EndeavourOS.
In the bootloader build config.log I also have the same error (err: ../test.c) as well as two more a bit further down:
and
yochananmarqos commented on 2024-03-26 16:19 (UTC)
@chrisjbillington: I just built it in a clean chroot with no issues. By the way, the precompiled bootloaders are removed purposely in order to compile it, so that first message is normal.
chrisjbillington commented on 2024-03-26 01:47 (UTC)
Build failing for me today, full output here:
https://gist.github.com/chrisjbillington/14ff939d18dfc970e7ef2a386f63e556
Key lines:
No precompiled bootloader found or compile forced. Trying to compile the bootloader for you ...
[...]
The configuration failed (complete log in /tmp/pyinstaller/src/pyinstaller-6.5.0/bootloader/build/config.log) ERROR: Failed compiling the bootloader. Please compile manually and rerun setup.py
This configuration step appears to involve compiling and running lots of C snippets to detect things about the environment. In the log file (config.log), there are a bunch of compile errors which are presumably the source of the problem, e.g.:
err: ../test.c: In function ‘main’: ../test.c:3:24: error: size of array ‘test_array’ is negative 3 | static int test_array[1 - 2 * !(sizeof(void *) == 4)]; | ^
~ytret commented on 2024-03-11 10:11 (UTC)
The sha256sum is wrong, for me it is:
0200fb8e27c284e5698a688aa904980b7a1692bc38daf6446bbae8f71b65dc2e pyinstaller-6.5.0.tar.gz
yochananmarqos commented on 2023-12-08 16:13 (UTC)
@HurricanePootis: I've limited it to only run the unit tests.
1 2 3 4 5 Next › Last »