--- Begin Message ---
Package: gcc-snapshot
Version: 20170505-1
Severity: important
If I compile a program with
gcc-snapshot -fsanitize=address
I get when running it:
./a.out: error while loading shared libraries: libasan.so.4: cannot open shared object file: No such file or directory
libasan.so.4 is part of libasan4, which exists only in experimental,
while gcc-snapshot 20170505-1 is in unstable.
-- System Information:
Debian Release: 9.0
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64
(x86_64)
Foreign Architectures: i386
Kernel: Linux 4.9.0-3-amd64 (SMP w/12 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages gcc-snapshot depends on:
ii binutils 2.28-4
ii libc6 2.24-10
ii libc6-dev 2.24-10
ii libc6-dev-i386 2.24-10
ii libc6-dev-x32 2.24-10
ii libc6-i386 2.24-10
ii libc6-x32 2.24-10
ii libgc1c2 1:7.4.2-8
ii libgmp10 2:6.1.2+dfsg-1
ii libisl15 0.18-1
ii libmpc3 1.0.3-1+b2
ii libmpfr4 3.1.5-1
ii python 2.7.13-2
ii zlib1g 1:1.2.8.dfsg-5
gcc-snapshot recommends no packages.
Versions of packages gcc-snapshot suggests:
ii binutils [binutils-gold] 2.28-4
-- no debconf information
--- End Message ---
--- Begin Message ---
On 09.05.2017 15:48, Vincent Lefevre wrote:
> Package: gcc-snapshot
> Version: 20170505-1
> Severity: important
>
> If I compile a program with
>
> gcc-snapshot -fsanitize=address
>
> I get when running it:
>
> ./a.out: error while loading shared libraries: libasan.so.4: cannot open shared object file: No such file or directory
>
> libasan.so.4 is part of libasan4, which exists only in experimental,
> while gcc-snapshot 20170505-1 is in unstable.
set LD_LIBRARY_PATH for running your binaries. The libasan4 package isn't based
on the trunk, but on the gcc-7-branch, so it might be different.
closing this issue, there is no "propoer" solution.
--- End Message ---