|
242 | Packages | Bug Report | Medium | Low | [flac] fails to build | Closed | |
Task Description
This is just the sad state of what people do to working software:
if(CMAKE_SYSTEM_PROCESSOR STREQUAL "i686" AND HAVE_STACKREALIGN_FLAG)
add_compile_options(-mstackrealign)
endif()
which results in nasm to fail with “unknown option -m”
a) they rewrite half of the build system without apparently understanding fully the autoconf part
b) they don’t bother to delete to autoconf part
c) they write code for porting the software apparenty without testing (why bother then in the first place?)
|
|
311 | Packages | Bug Report | Medium | Low | [ffmpeg] fails with SIGILL on i686 | Assigned | |
Task Description
work fine on pentium4
reproducable: ffplay <file.mp4>
offending opcode:
0xb5f315e7: f3 0f 10 83 d0 0b 00 00 movss
0xbd0(%ebx),%xmm0
|
|
239 | Packages | Bug Report | Medium | Low | [ffmpeg] and [ffmepg4.4] fail to build | Closed | |
Task Description
libswscale/x86/rgb2rgb_template.c: In function ‘interleaveBytes_sse2’:
libswscale/x86/rgb2rgb_template.c:1838:9: error: the register ‘xmm2’ cannot be clobbered in ‘asm’ for the current target
1838 | __asm__(
| ^
Also on i486 symbols are missing if not using LTO and probing of libraries like x264/x265 fail.
|
|
277 | Packages | Bug Report | Medium | Low | [emacs] rebuild fails on 486, needs librsvg | Closed | |
Task Description
/usr/src/debug/emacs-28.1/src/image.c:10009: undefined reference to `rsvg_handle_set_stylesheet’ # /usr/bin/ld: /usr/src/debug/emacs-28.1/src/image.c:10196: undefined reference to `rsvg_handle_set_stylesheet’
|
|
252 | Packages | Bug Report | Medium | Low | [dbus-python/python-dbus] mixup | New | |
Task Description
packages (like upower) which include a dependency on python-dbus
use a 3.9 version and miss the correct one dbus-python (which
replaces python-dbus). This will only solve itself when upstream
adapts the PKGBUILDs to this name change.
|
|
258 | Packages | Bug Report | Medium | Low | [clang] fails to build on i486 | Closed | |
Task Description
/usr/bin/c++ -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -D_LARGEFILE_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -I/build/clang/src/clang-13.0.1.src/build/unittests/Tooling -I/build/clang/src/clang-13.0.1.src/unittests/Tooling -I/build/clang/src/clang-13.0.1.src/include -I/build/clang/src/clang-13.0.1.src/build/include -I/build/clang/src/llvm-13.0.1.src/utils/unittest/googletest/include -I/build/clang/src/llvm-13.0.1.src/utils/unittest/googlemock/include -march=i486 -mtune=generic -O2 -pipe -fno-plt -fexceptions -Wp,-D_FORTIFY_SOURCE=2 -Wformat -Werror=format-security -fstack-clash-protection -Wp,-D_GLIBCXX_ASSERTIONS -fPIC -fno-semantic-interposition -fvisibility-inlines-hidden -Werror=date-time -Wall -Wextra -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wno-missing-field-initializers -Wimplicit-fallthrough -Wno-class-memaccess -Wno-redundant-move -Wno-pessimizing-move -Wno-noexcept-type -Wdelete-non-virtual-dtor -Wsuggest-override -Wno-comment -Wmisleading-indentation -fdiagnostics-color -ffunction-sections -fdata-sections -fno-common -Woverloaded-virtual -fno-strict-aliasing -pedantic -Wno-long-long -O3 -DNDEBUG -fno-exceptions -Wno-suggest-override -std=c++14 -MD -MT unittests/Tooling/CMakeFiles/ToolingTests.dir/RecursiveASTVisitorTests/CallbacksLeaf.cpp.o -MF unittests/Tooling/CMakeFiles/ToolingTests.dir/RecursiveASTVisitorTests/CallbacksLeaf.cpp.o.d -o unittests/Tooling/CMakeFiles/ToolingTests.dir/RecursiveASTVisitorTests/CallbacksLeaf.cpp.o -c /build/clang/src/clang-13.0.1.src/unittests/Tooling/RecursiveASTVisitorTests/CallbacksLeaf.cpp
{standard input}: Assembler messages:
{standard input}: Error: open CFI at the end of file; missing .cfi_endproc directive
c++: fatal error: Killed signal terminated program cc1plus
compilation terminated.
We can ommit the tests..
Also lto is not good (breaks early) and you need lots of memory and swap to build it.
|
|
262 | Packages | Bug Report | Medium | Low | [ca-certificates] contains empty cert bundle | Closed | |
Task Description
-r--r--r-- 1 root root 0 May 12 07:00 /etc/ca-certificates/extracted/tls-ca-bundle.pem
curl -v https://www.openssl.org
* Trying 104.89.5.252:443...
* Connected to www.openssl.org (104.89.5.252) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* error setting certificate verify locations: CAfile: /etc/ssl/certs/ca-certificates.crt CApath: none
* Closing connection 0
curl: (77) error setting certificate verify locations: CAfile: /etc/ssl/certs/ca-certificates.crt CApath: none
|
|
320 | Packages | Bug Report | Medium | Low | [btop] On i486 fails on clock_gettime64 | New | |
Task Description
shows a red ERROR: on startup, strace shows:
write(2, "\n", 1
) = 1
clock_gettime64(CLOCK_REALTIME, {tv_sec=1675495215, tv_nsec=436798535}) = 0
exit_group(1) = ?
+++ exited with 1 +++
[root@eurobuild6-7-i486 ~]# btop
ERROR: No UTF-8 locale detected!
|
|
246 | Packages | Bug Report | Medium | Low | [blender] doesn't work (and doesn't build) | New | |
Task Description
blender 2.93 has dependencies on wrong versions of
- llvm (via openshadinglanguage)
- boost (via openimageio)
Could NOT find PythonLibsUnix (missing: PYTHON_LIBRARY PYTHON_LIBPATH PYTHON_INCLUDE_DIR PYTHON_INCLUDE_CONFIG_DIR)’
blender 3.0.1:
Haru not found, disabling WITH_HARU’ and ‘Cycles OSL requires WITH_LLVM, the library may not have been found. Configure LLVM or disable WITH_CYCLES_OSL
Let’s tackle one issue after the other. 
|
|
261 | Packages | Bug Report | Medium | Low | [binutils] FTBFS | Closed | |
Task Description
/build/binutils/src/binutils-gdb/libiberty/fibheap.c: In function ‘fibheap_replace_key_data’:
/build/binutils/src/binutils-gdb/libiberty/fibheap.c:38:25: error: ‘LONG_MIN’ undeclared (first use in th
is function)
38 | #define FIBHEAPKEY_MIN LONG_MIN
| ^~~~~~~~
/build/binutils/src/binutils-gdb/libiberty/fibheap.c:220:30: note: in expansion of macro ‘FIBHEAPKEY_MIN’
220 | if (okey == key && okey != FIBHEAPKEY_MIN)
| ^~~~~~~~~~~~~~
/build/binutils/src/binutils-gdb/libiberty/fibheap.c:36:1: note: ‘LONG_MIN’ is defined in header ‘<limits.h>’; did you forget to ‘#include <limits.h>’?
35 | #include "fibheap.h"
+++ |+#include <limits.h>
Amazing code quality
|
|
103 | Packages: Stable | Bug Report | Medium | Low | yarn segfaults | New | |
Task Description
experienced when building buildbot-www
/bin/sh: line 1: 4744 Segmentation fault (core dumped) yarn install –pure-lockfile
|
|
99 | Packages: Stable | Bug Report | Medium | Low | Incompatible Qt library (version 0x50d02) with this lib ... | Closed | |
Task Description
Seen with trojita:
Cannot mix incompatible Qt library (version 0x50d02) with this library (version 0x50d01)
|
|
102 | Packages: Stable | Bug Report | Medium | Low | firefox-i18-n gets pushed to stable though firefox is n ... | Closed | |
Task Description
warning: cannot resolve “firefox>=71.0”, a dependency of “firefox-i18n-de”
|
|
101 | Packages: Stable | Bug Report | Medium | Low | clang 9.0.0 moved to stable too soon (breaks kdevelop) | Closed | |
Task Description
:: installing clang (9.0.1-1.0) breaks dependency ‘clang=9.0.0’ required by kdevelop
|
|
105 | Packages: Stable | Bug Report | Medium | Low | chromium crash in blocked syscalls (libseccomp) | Closed | |
Task Description
chromium apparently also has trouble in some seccomp jailing:
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
[1201:1210:0227/131355.020958:FATAL:gpu_data_manager_impl_private.cc(990)] The display compositor is frequently crashing. Goodbye.
[1]+ Trace/breakpoint trap (core dumped) chromium
|
|
96 | Packages: Stable | Bug Report | Medium | Medium | [rust] broken or missing backend | Closed | |
Task Description
shell> echo > rust.rc <<EOF
fn main() {
println!( "Hello Rust! " );
}
EOF
shell> rustc rust.rs
error: failed to find a `codegen-backends` folder in the sysroot candidates:
* /usr
* /usr
Presumably the i686 folders are moved around in PKGBUILD to form lib32
libraries for rust on 64-bit.
|
|
146 | Packages: Upstream | Bug Report | Medium | Low | trojita doesn't build, missing a patch, failures on qt ... | Closed | |
Task Description
=⇒ ERROR: Failure while downloading https://cgit.kde.org/trojita.git/patch/?id=cf2364b8
SHA1 in https://anongit.kde.org/trojita):
cf2364b80fa8ae844df8350cd5833d47cce235f2
Fix possible crash when downloading attachments
Yep, promising, lets download the patch and add it to the package.
Original bug: https://bugs.kde.org/show_bug.cgi?id=417697
–
/build/trojita/src/trojita-0.7/src/Gui/Window.cpp:981:26: error: aggregate ‘QPainterPath path’ has incomplete type and cannot be defined
981 | QPainterPath path;
| ^~~~
needs a #include <QPainterPath>
Reported as https://bugs.kde.org/show_bug.cgi?id=432827
|
