On Thu, Aug 13, 2020 at 09:23:35AM -0600, Jeff Law wrote:
> On Thu, 2020-08-13 at 11:13 -0400, Omair Majid wrote:
> > Jeff Law writes:
> >
> > > I can't help with the untagging, but I'm here if there's anything
> > > going wrong with the system tools that is ultimately affecting dotnet.
> >
> >
On Thu, 2020-08-13 at 11:13 -0400, Omair Majid wrote:
> Jeff Law writes:
>
> > I can't help with the untagging, but I'm here if there's anything
> > going wrong with the system tools that is ultimately affecting dotnet.
>
> Thanks.
>
> Just for context:
>
> .NET Core uses a bundled (and modifi
Jeff Law writes:
> I can't help with the untagging, but I'm here if there's anything
> going wrong with the system tools that is ultimately affecting dotnet.
Thanks.
Just for context:
.NET Core uses a bundled (and modified) copy of libunwind for unwinding
the stack. This version doesn't work
On Thu, 2020-08-13 at 10:21 -0400, Omair Majid wrote:
> Hi,
>
> One of the recent builds produced for "dotnet3.1" for rawhide is broken
> on aarch64. It built successfully in koji, but produced aarch64 binaries
> that segfault on startup. A new build of dotnet3.1 requires a working
> older build.
Hi,
One of the recent builds produced for "dotnet3.1" for rawhide is broken
on aarch64. It built successfully in koji, but produced aarch64 binaries
that segfault on startup. A new build of dotnet3.1 requires a working
older build. That means all recent builds of dotnet3.1 in Rawhide/F33 on
failed
