Your message dated Fri, 14 Sep 2018 23:33:35 +0200
with message-id <91cca305-45ef-0fed-c6b7-d7e875ea0...@physik.fu-berlin.de>
and subject line Re: Bug#907912 closed by Sylvestre Ledru
<sylves...@debian.org> (Bug#907912: fixed in llvm-toolchain-7 1:7~+rc3-1)
has caused the Debian Bug report #907912,
regarding llvm-toolchain-7: FTBFS linking libopenmp
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
907912: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907912
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: llvm-toolchain-7
Version: 1:7~svn331965-1
Severity: normal
User: debian-sp...@lists.debian.org
Usertags: sparc64
Hi!
llvm-toolchain-7 currently fails to build from source on the
following architectures because the embedded libomp doesn't
support them:
- powerpc
- powerpcspe
- riscv64
- sparc64
And possibly:
- armel
- mips
- mipsel
Although the latter three might be fixable by linking against
libatomic but I haven't looked into the details yet. Either way,
disabling libomp for the former four architectures or, better,
enabling it for supported architectures only, should fix the
FTBFS on multiple architectures.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaub...@debian.org
`. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
--- End Message ---
--- Begin Message ---
On 9/11/18 12:44 AM, John Paul Adrian Glaubitz wrote:
> This didn’t work for some reason:
>
>> https://buildd.debian.org/status/package.php?p=llvm-toolchain-7&suite=sid
>
> In my testbuilds, LLVM built fine on sparc64 with OpenMP disabled.
I lost track which of the many changes fixed this, but I think this
issue was because of the inverted ifeq logic for OPENMP_ENABLE.
Either way, closing as it has been fixed now.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaub...@debian.org
`. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
--- End Message ---