[Borgbackup] pip install failed

Bzzzz lazyvirus at gmx.com
Sun Sep 11 13:34:09 EDT 2022


On Sun, 11 Sep 2022 19:27:10 +0200
Boris Kirkorowicz <bkborg at kirk.de> wrote:

> Hi,
> thank you for your patience.

Which isn't rewarded, as you have visibly did not read the doc,
especially about the installation *requirements*.

When using a package, you only need the required libs, however when
building it, you need the development libs (which also install the
regular libs that'll be used by the program in exploitation in a
normal system).

Sooo, RTFM!

Jean-Yves


> Am 11.09.22 um 17:32 schrieb Thorsten Schöning:
> > As said, something like a developer package is necessary most
> > likely. Something like this:
> > 
> > https://pkgs.org/download/libopenssl-devel
> 
> I did so, and i had to install python310-devel as well. Now, the
> installation still fails, with >500 lines output. The last few lines
> are
> 
> 
> >       gcc -shared
> > build/temp.linux-x86_64-cpython-310/src/borg/platform/posix.o
> > -L/usr/lib64 -o
> > build/lib.linux-x86_64-cpython-310/borg/platform/posix.cpython-310-x86_64-linux-gnu.so
> > building 'borg.platform.linux' extension gcc -Wno-unused-result
> > -Wsign-compare -DNDEBUG -O2 -Wall -U_FORTIFY_SOURCE
> > -D_FORTIFY_SOURCE=3 -fstack-protector-strong -funwind-tables
> > -fasynchronous-unwind-tables -fstack-clash-protection
> > -Werror=return-type -g -DOPENSSL_LOAD_CONF -fwrapv
> > -fno-semantic-interposition -O2 -Wall -U_FORTIFY_SOURCE
> > -D_FORTIFY_SOURCE=3 -fstack-protector-strong -funwind-tables
> > -fasynchronous-unwind-tables -fstack-clash-protection
> > -Werror=return-type -g -IVendor/ -O2 -Wall -U_FORTIFY_SOURCE
> > -D_FORTIFY_SOURCE=3 -fstack-protector-strong -funwind-tables
> > -fasynchronous-unwind-tables -fstack-clash-protection
> > -Werror=return-type -g -IVendor/ -fPIC -I/usr/include/python3.10 -c
> > src/borg/platform/linux.c -o
> > build/temp.linux-x86_64-cpython-310/src/borg/platform/linux.o -Wall
> > -Wextra -Wpointer-arith In Datei, eingebunden von
> > /usr/include/bits/libc-header-start.h:33, von
> > /usr/include/limits.h:26, von
> > /usr/lib64/gcc/x86_64-suse-linux/11/include-fixed/limits.h:203, von
> > /usr/lib64/gcc/x86_64-suse-linux/11/include-fixed/syslimits.h:7,
> > von /usr/lib64/gcc/x86_64-suse-linux/11/include-fixed/limits.h:34,
> > von /usr/include/python3.10/Python.h:11, von
> > src/borg/platform/linux.c:27: /usr/include/features.h:424:5:
> > Warnung: #warning _FORTIFY_SOURCE > 2 is treated like 2 on this
> > platform [-Wcpp] 424 | #   warning _FORTIFY_SOURCE > 2 is treated
> > like 2 on this platform |     ^~~~~~~
> > src/borg/platform/linux.c:769:10: schwerwiegender Fehler:
> > sys/acl.h: Datei oder Verzeichnis nicht gefunden 769 | #include
> > "sys/acl.h" |          ^~~~~~~~~~~ Kompilierung beendet. error:
> > command '/usr/bin/gcc' failed with exit code 1 [end of output]
> > note: This error originates from a subprocess, and is likely not a
> > problem with pip. ERROR: Failed building wheel for borgbackup
> > Failed to build borgbackup ERROR: Could not build wheels for
> > borgbackup, which is required to install pyproject.toml-based
> > projects
> 
> after installing gcc11-devel (including several depending pkgs), I got
> 180 lines output, ending like this:
> 
> >       /usr/include/features.h:424:5: Warnung: #warning
> > _FORTIFY_SOURCE > 2 is treated like 2 on this platform [-Wcpp] 424
> > | #   warning _FORTIFY_SOURCE > 2 is treated like 2 on this
> > platform |     ^~~~~~~ gcc -shared
> > build/temp.linux-x86_64-cpython-310/src/borg/crypto/_crypto_helpers.o
> > build/temp.linux-x86_64-cpython-310/src/borg/crypto/low_level.o
> > -L/usr/lib64 -lcrypto -o
> > build/lib.linux-x86_64-cpython-310/borg/crypto/low_level.cpython-310-x86_64-linux-gnu.so
> > /usr/lib64/gcc/x86_64-suse-linux/11/../../../../x86_64-suse-linux/bin/ld:
> > /lib64/libc.so.6: unknown type [0x13] section `.relr.dyn'
> > /usr/lib64/gcc/x86_64-suse-linux/11/../../../../x86_64-suse-linux/bin/ld:
> > skipping incompatible /lib64/libc.so.6 when searching for
> > /lib64/libc.so.6
> > /usr/lib64/gcc/x86_64-suse-linux/11/../../../../x86_64-suse-linux/bin/ld:
> > cannot find /lib64/libc.so.6
> > /usr/lib64/gcc/x86_64-suse-linux/11/../../../../x86_64-suse-linux/bin/ld:
> > /lib64/libc.so.6: unknown type [0x13] section `.relr.dyn'
> > /usr/lib64/gcc/x86_64-suse-linux/11/../../../../x86_64-suse-linux/bin/ld:
> > skipping incompatible /lib64/libc.so.6 when searching for
> > /lib64/libc.so.6
> > /usr/lib64/gcc/x86_64-suse-linux/11/../../../../x86_64-suse-linux/bin/ld:
> > /lib64/ld-linux-x86-64.so.2: unknown type [0x13] section
> > `.relr.dyn'
> > /usr/lib64/gcc/x86_64-suse-linux/11/../../../../x86_64-suse-linux/bin/ld:
> > skipping incompatible /lib64/ld-linux-x86-64.so.2 when searching
> > for /lib64/ld-linux-x86-64.so.2
> > /usr/lib64/gcc/x86_64-suse-linux/11/../../../../x86_64-suse-linux/bin/ld:
> > cannot find /lib64/ld-linux-x86-64.so.2
> > /usr/lib64/gcc/x86_64-suse-linux/11/../../../../x86_64-suse-linux/bin/ld:
> > /lib64/ld-linux-x86-64.so.2: unknown type [0x13] section
> > `.relr.dyn'
> > /usr/lib64/gcc/x86_64-suse-linux/11/../../../../x86_64-suse-linux/bin/ld:
> > skipping incompatible /lib64/ld-linux-x86-64.so.2 when searching
> > for /lib64/ld-linux-x86-64.so.2 collect2: Fehler: ld gab 1 als
> > Ende-Status zurück error: command '/usr/bin/gcc' failed with exit
> > code 1 [end of output] note: This error originates from a
> > subprocess, and is likely not a problem with pip. ERROR: Failed
> > building wheel for borgbackup Failed to build borgbackup ERROR:
> > Could not build wheels for borgbackup, which is required to install
> > pyproject.toml-based projects
> 
> 
> As a non-developer, this is too much for me, I do not understand
> what's going on.
> 
> 
> 



More information about the Borgbackup mailing list