Re: port-amd64/55367: failure to compile amd64 current with clang

[Jason Thorpe <thorpej%me.com@localhost>]

The following reply was made to PR toolchain/55367; it has been noted by GNATS.

From: Jason Thorpe <thorpej%me.com@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: port-amd64-maintainer%netbsd.org@localhost,
 gnats-admin%netbsd.org@localhost,
 netbsd-bugs%netbsd.org@localhost,
 rares.aioanei%gmail.com@localhost
Subject: Re: port-amd64/55367: failure to compile amd64 current with clang
Date: Thu, 11 Jun 2020 06:38:43 -0700

 > On Jun 11, 2020, at 5:15 AM, Sevan Janiyan <venture37%geeklan.co.uk@localhost> =
 wrote:
 >=20
 > The following reply was made to PR port-amd64/55367; it has been noted =
 by GNATS.
 >=20
 > From: Sevan Janiyan <venture37%geeklan.co.uk@localhost>
 > To: "gnats-bugs%netbsd.org@localhost" <gnats-bugs%NetBSD.org@localhost>
 > Cc:=20
 > Subject: Re: port-amd64/55367: failure to compile amd64 current with =
 clang
 > Date: Thu, 11 Jun 2020 13:12:35 +0100
 >=20
 > This is due to proplib update and drvctl using the now depracted API. =
 It
 > results in warnings which the compiler is set to treat as errors. Keep
 > an eye out for update commits as thorpej is in the process of updating
 > things.
 
 This is a clang problem.  GCC does not treat these linker warnings as =
 fatal, nor should it.
 
 -- thorpej