Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 07 Apr 2022 20:50:36 +0000
From:      bugzilla-noreply@freebsd.org
To:        toolchain@FreeBSD.org
Subject:   [Bug 221423] gcc std::locale(LocaleName) crashes instead of throwing an exception
Message-ID:  <bug-221423-29464-pSdbGkymPJ@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-221423-29464@https.bugs.freebsd.org/bugzilla/>
References:  <bug-221423-29464@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221423

--- Comment #30 from Mark Millard <marklmi26-fbsd@yahoo.com> ---
(In reply to Mark Millard from comment #27)

Turns out that there is:

https://github.com/llvm/llvm-project/issues/54004

reporting the issue for llvm14 vs. using 13 in the
.so.VER naming:

QUOTE
Seen in conda-forge/clangdev-feedstock#165, where we explicitly test for
presence of libclang.so.<major_ver> in the installed environment. Turns out,
that libclang.so.14.0.0 is created, but not the symlink to libclang.so.14:

-- Installing:
/home/conda/feedstock_root/build_artifacts/[...]/lib/libclang.so.14.0.0
-- Installing:
/home/conda/feedstock_root/build_artifacts/[...]/lib/libclang.so.13
-- Installing: /home/conda/feedstock_root/build_artifacts/[...]/lib/libclan=
g.so
END QUOTE

but . . .

QUOTE
This is expected. libclang.so ABI usually stays stable across major release=
s,
so we've frozen the soname at libclang.so.13. The plan is to keep it with t=
his
name unless the ABI changes.
END QUOTE

There is more to the exchange but I'll stop quoting here.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-221423-29464-pSdbGkymPJ>