pkgsrc-Users archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: 'state_not_recoverable' is not a member of 'std::errc' on clang build (was: clang-13.0.1nb1 build from pkgsrc 2022Q2 fails on NetBSD-9.2_STABLE (2022-07-01))
- To: Matthias Petermann <mp%petermann-it.de@localhost>
- Subject: Re: 'state_not_recoverable' is not a member of 'std::errc' on clang build (was: clang-13.0.1nb1 build from pkgsrc 2022Q2 fails on NetBSD-9.2_STABLE (2022-07-01))
- From: nia <nia%NetBSD.org@localhost>
- Date: Sat, 16 Jul 2022 09:51:29 +0000
On Sat, Jul 16, 2022 at 09:49:04AM +0000, nia wrote:
> On Sat, Jul 16, 2022 at 07:55:25AM +0200, Matthias Petermann wrote:
> > So hopefully my concern sounds a little more concrete now: Is it possible
> > that _GLIBCXX_HAVE_ENOTRECOVERABLE is not defined in the scenario described
> > in the boundary conditions, and what are the possible reasons for this?
> >
> > Could it be that due to the fact that my NetBSD 9.2 sandbox is running on a
> > NetBSD 9.99.98 kernel, a decision is made at some point in a build (such as
> > a dependent package?) that leads to this? The list of installed dependencies
> > on the affected sandbox are:
>
> The problem is that your NetBSD 9 sandbox identifies as NetBSD 9.99 in
> uname, so the check to enable the fix for this problem fails. If you
> have a different NetBSD version in a chroot, you need to use
> pkgtools/libkver to fix the kernel version. If you're using pbulk,
> I have some tools to help with this.
If you don't want to use libkver, it looks like it's possible to override
OPSYS_VERSION in mk.conf - but this is very hacky.
Home |
Main Index |
Thread Index |
Old Index