December 2019 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1106000] New: llvm-config contains gcc-incompatible flags
by bugzilla_noreply＠novell.com 19 Nov '21

19 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1106000 Bug ID: 1106000 Summary: llvm-config contains gcc-incompatible flags Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: msrb(a)suse.com Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- llvm-config --cflags contains "-Werror=unguarded-availability-new" which makes builds with gcc fail: cc1plus: error: -Werror=unguarded-availability-new: no option -Wunguarded-availability-new -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1092697] New: LLVM build fails on armv7l
by bugzilla_noreply＠novell.com 19 Nov '21

19 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1092697 Bug ID: 1092697 Summary: LLVM build fails on armv7l Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: msrb(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The llvm4/5/6 build fails on armv7l because it is running out of memory. It is happening during linking of stage1, most likely because of the size of debuginfo. Stage1 should not be built with debuginfo (it is only used to compile the next stage), but it got the "-g" parameter accidentally from %optflags. -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 1087136] New: GCC 8: llvm5 build fails
by bugzilla_noreply＠novell.com 19 Nov '21

19 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1087136 Bug ID: 1087136 Summary: GCC 8: llvm5 build fails Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: martin.liska(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Build the package with GCC 8, there's error: https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:… Please build the project as follows to reproduce the issue: osc build --alternative-project=openSUSE:Factory:Staging:Gcc7 -- You are receiving this mail because: You are on the CC list for the bug.

2 6

[Bug 1086445] New: libLLVMTableGen not packaged
by bugzilla_noreply＠novell.com 19 Nov '21

19 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1086445 Bug ID: 1086445 Summary: libLLVMTableGen not packaged Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: guillaume.gardet(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Currently, in Tumbleweed, LLVM only packages libLLVM.so* and we are missing additional libraries, such as libLLVMTableGen.so* Some packages fails to build (e.g. ldc package) because of the missing additional libraries. -- You are receiving this mail because: You are on the CC list for the bug.

2 10

[Bug 1073210] New: Link Time Optimization doesn't work out of the box on 64 bit systems because of bfd-plugins path mixup
by bugzilla_noreply＠novell.com 19 Nov '21

19 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1073210 Bug ID: 1073210 Summary: Link Time Optimization doesn't work out of the box on 64 bit systems because of bfd-plugins path mixup Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: l.lunak(a)centrum.cz QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When using LTO, linker is supposed to find a plugin for handling LTO in /usr/lib/bfd-plugins . And this path is hardcoded in sources, and it's "lib" even for 64 bit systems. However, neither GCC nor Clang/LLVM install their plugin there. GCC doesn't do anything with its plugin except for shipping it in its own directory, and LLVMGold is installed to /usr/lib64/bfd-plugins. So instead of LTO simply working when using -flto, one has to use gcc-ar/llvm-ar etc. to override the ar etc. which should work but don't because of this. I can easily submit fixed binutils and gcc packages to make them use /usr/lib64/bfd-plugins too, but I've first created this bugreport so that there's just one place for referring to this issue. Also I would first like to verify that this would indeed be the proper fix - is there any special reason why binutils hardcodes the "lib" there? -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1065464] New: Don't allow multiple OpenCL ICD packages to be installed simultaneously
by bugzilla_noreply＠novell.com 19 Nov '21

19 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1065464 Bug ID: 1065464 Summary: Don't allow multiple OpenCL ICD packages to be installed simultaneously Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: sonichedgehog_hyperblast00(a)yahoo.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- I considered this important enough to warrant a bug report. The forum thread where I discovered and further explained the issue can be found here: https://forums.opensuse.org/showthread.php/527821-Blender-crashes-at-startu… When running the command 'zypper dup' without additional parameters, zypper wants to install the OpenCL ICD named pocl. However Mesa already uses another ICD which seems to come in the package libOpenCL1. This is a problem because from the looks of it, you may only have one ICD installed on your system at once; More than that will cause a conflict, and every OpenCL application will crash with the following error: mesa: CommandLine Error: Option 'enable-value-profiling' registered more than once! LLVM ERROR: inconsistency in registered CommandLine options To test and confirm this, you can install both "libOpenCL1" and "pocl" simultaneously then attempt to run Blender 3D: The application should crash on startup with the console output quoted above. After removing the pocl package however, Blender will start and work properly again. Until this bug is solved by the X11 developers, it might be a good idea for the openSUSE repositories to be aware of it and mark multiple OpenCL ICD packages as incompatible, only recommending that you install one at once. Users may find that OpenCL applications have suddenly stopped working, and not know what to do in order to fix the problem. A workaround for the time being is to mark pocl as "taboo / never install". -- You are receiving this mail because: You are on the CC list for the bug.

2 17

[Bug 1041469] New: llvm4 spec issues
by bugzilla_noreply＠novell.com 19 Nov '21

19 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1041469 Bug ID: 1041469 Summary: llvm4 spec issues Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: msuchanek(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hello, llvm4 has this conditional: %if 0%{?sle_version} <= 130000 BuildRequires: gcc6 BuildRequires: gcc6-c++ %else BuildRequires: gcc BuildRequires: gcc-c++ %endif Since TW has no sle_version you get gcc6 on TW which is probably not intended. However, llvm4 is the only llvm which passes test on arm64 which may be the result of building with gcc6. Also lldb4 has ExclusiveArch: arm x86_64 arm is not an arch so this will build on x86_64 only. Maybe it was supposed to be %arm or armv7 or ... ? -- You are receiving this mail because: You are on the CC list for the bug.

2 5

[Bug 1026191] New: Add BPF into llvm target for PowerPC64 and AArch64
by bugzilla_noreply＠novell.com 19 Nov '21

19 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1026191 Bug ID: 1026191 Summary: Add BPF into llvm target for PowerPC64 and AArch64 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: glin(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- To build bcc on PowerPC64 and AArch64, we need to add BPF into the llvm build targets. We currently only build the native target on those two architectures. This is also for fate#322227. -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1012260] New: Clang++-3.8 symlink is missing
by bugzilla_noreply＠novell.com 19 Nov '21

19 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1012260 Bug ID: 1012260 Summary: Clang++-3.8 symlink is missing Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: alex.richardson(a)gmx.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- lrwxrwxrwx 1 root root 23 Oct 31 11:44 /usr/bin/clang -> /etc/alternatives/clang lrwxrwxrwx 1 root root 25 Oct 31 11:44 /usr/bin/clang++ -> /etc/alternatives/clang++ lrwxrwxrwx 1 root root 11 Oct 31 11:45 /usr/bin/clang-3.8 -> clang-3.8.1 -rwxr-xr-x 1 root root 99176 Oct 31 11:44 /usr/bin/clang-3.8.1 lrwxrwxrwx 1 root root 11 Oct 31 11:45 /usr/bin/clang++-3.8.1 -> clang-3.8.1 There should also be a symlink /usr/bin/clang++-3.8 -> /usr/bin/clang++-3.8.1 I am building some software that expects clang++-$MAJOR.$MINOR to exist and it would be nice if I didn't have to create that link myself. -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1135744] New: [Staging] texlive fails to build against gc 8.x
by bugzilla_noreply＠novell.com 18 Nov '21

18 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1135744 Bug ID: 1135744 Summary: [Staging] texlive fails to build against gc 8.x Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- gc 8.0.4 was submitted for inclusion into Factory. During the staging process though, texlive resulted in a build failure > /usr/lib64/gcc/x86_64-suse-linux/8/../../../../x86_64-suse-linux/bin/ld: picture.o: in function `operator new(unsigned long, GCPlacement, void (*)(void*, void*), void*)': [ 1376s] /usr/include/gc/gc_cpp.h:545: undefined reference to `GC_throw_bad_alloc()' [ 1376s] /usr/lib64/gcc/x86_64-suse-linux/8/../../../../x86_64-suse-linux/bin/ld: settings.o: in function `operator new(unsigned long, GCPlacement, void (*)(void*, void*), void*)': [ 1376s] /usr/include/gc/gc_cpp.h:545: undefined reference to `GC_throw_bad_alloc()' [ 1376s] /usr/lib64/gcc/x86_64-suse-linux/8/../../../../x86_64-suse-linux/bin/ld: settings.o: in function `gc::operator new(unsigned long)': [ 1376s] /usr/include/gc/gc_cpp.h:410: undefined reference to `GC_throw_bad_alloc()' [ 1376s] /usr/lib64/gcc/x86_64-suse-linux/8/../../../../x86_64-suse-linux/bin/ld: /usr/include/gc/gc_cpp.h:410: undefined reference to `GC_throw_bad_alloc()' [ 1376s] /usr/lib64/gcc/x86_64-suse-linux/8/../../../../x86_64-suse-linux/bin/ld: /usr/include/gc/gc_cpp.h:410: undefined reference to `GC_throw_bad_alloc()' [ 1376s] /usr/lib64/gcc/x86_64-suse-linux/8/../../../../x86_64-suse-linux/bin/ld: settings.o:/usr/include/gc/gc_cpp.h:410: more undefined references to `GC_throw_bad_alloc()' follow This can either be an issue in texlive (making use of code exposed in a library it is not linking, e.g. gccpp) or gc might use them implicitly and not linking the lib itself (possibly texlive needs a different way to identify what to link) -- You are receiving this mail because: You are on the CC list for the bug.

2 5