Control: blocked -1 by 797038
This problem has solved itself, according to
https://ci.debian.net/packages/libe/libelfin/unstable/amd64/ >.
The automatic checking indicate that it was fixed when clang migrated
from version 1:3.6-33 to 1:3.8-34. A closer look in the changelog make
me believe it wa
Control: forwarded -1 https://github.com/plasma-umass/coz/issues/74
This issue is also reported upstream.
--
Happy hacking
Petter Reinholdtsen
Petter Reinholdtsen writes:
> I found interesting comments regarding this in
> http://allanmcrae.com/2015/06/the-case-of-gcc-5-1-and-the-two-c-abis/ >
> and https://llvm.org/bugs/show_bug.cgi?id=23529 >.
> Apparently clang do not understand a new gcc invention, the API tag,
> which is inserted in
I found interesting comments regarding this in
http://allanmcrae.com/2015/06/the-case-of-gcc-5-1-and-the-two-c-abis/ >
and https://llvm.org/bugs/show_bug.cgi?id=23529 >.
Apparently clang do not understand a new gcc invention, the API tag,
which is inserted in symbols build using -std=c++11.
Acco
Package: src:libelfin
Version: 0.1+20160825.git.6eb10ca-1
Severity: important
When building the libelfin shared libraries with GCC 6 in unstable, the
resulting shared library do not work for programs compiled with clang++.
The following test code demonstrate the problem:
CXXFLAGS="-std=c++11"
P
5 matches
Mail list logo
