Date: Fri, 15 May 2020 07:31:45 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 246479] devel/llvm10: libcxx is not packaged, new features can't be used Message-ID: <bug-246479-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D246479 Bug ID: 246479 Summary: devel/llvm10: libcxx is not packaged, new features can't be used Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: Individual Port(s) Assignee: brooks@FreeBSD.org Reporter: mb@64k.by Flags: maintainer-feedback?(brooks@FreeBSD.org) Assignee: brooks@FreeBSD.org after installing `llvm10` from the ports i realized that it doesn't include= the nowadays fully integrated `libcxx` package. which in turn means i can not u= se the new `concepts` from c++20 ( as example ). the gcc ports on the other ha= nd do include a fully packaged and upto date libstdc++. if `llvm10` would ship its corresponding `libcxx` then linking would require passing `-Wl,rpath=3D...` like as is the case with the gcc port. what are the reasons against packaging `libcxx` as well? maybe related: - https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D215193 note: for now i have to manually install `libcxx` and maybe `libcxxabi` and do all the `-Wl,...` anyways. i think for a usable current llvm port it should include it's `libcxx` which gets distributed in the official tarball. --=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-246479-7788>