Package: gcc-11-cross-ports
Version: 13
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
- broken Build-Depends:
gcc-11-cross-ports: lib32gcc1-ppc64-cross
lib32gcc1-sparc64-cross
lib32
Source: gcc-10-cross-ports
Version: 21
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
- broken Build-Depends:
gcc-10-cross-ports: lib32gcc1-ppc64-cross
lib32gcc1-sparc64-cross
lib32
Package: gcc-11-cross
Version: 17
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
- broken Build-Depends:
gcc-11-cross: lib32gcc1-amd64-cross
lib32gcc1-s390x-cross
lib64gcc1-i386-cross
Package: gcc-10-cross-base
Version: 20
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
- broken Build-Depends:
gcc-10-cross: lib32gcc1-amd64-cross
lib32gcc1-s390x-cross
lib64gcc1-i386-cross
Maintainer request.
Scott K
===
Please feel free to respond to this email if you don't understand why
your files were rejected, or if you upload new files which address our
concerns.
On Fri, 02 Oct 2015 15:45:18 -0400 Scott Kitterman
wrote:
> Package: gcc-python-plugin
> Version: 0.14-4
> Severity: normal
>
> It looks like gcc-python-plugin only supports building for one python3
version
> at a time, so it should build-dep on python3-dev vice python3-all-
>From the most recent armel build log [1]:
/usr/bin/doxygen: relocation error: /usr/lib/arm-linux-
gnueabi/libLLVM-3.9.so.1: symbol _ZTINSt13__future_base12_Result_baseE,
version GLIBCXX_3.4.15 not defined in file libstdc++.so.6 with link time
reference
proton-c/docs/api/CMakeFiles/docs-c.dir/bu
Package: gcc-python-plugin
Version: 0.14-4
Severity: normal
It looks like gcc-python-plugin only supports building for one python3 version
at a time, so it should build-dep on python3-dev vice python3-all-dev both to
make it build a little faster and to ease transition tracking.
8 matches
Mail list logo