Re: [base-gcc] Unbreak sysutils/usmb

2019-11-09 Thread Marcus MERIGHI
Hello! lan...@openbsd.org (Landry Breuil), 2019.11.09 (Sat) 09:35 (CET): > On Sat, Nov 09, 2019 at 09:16:49AM +0100, Charlene Wendling wrote: > > > http://build-failures.rhaalovely.net/sparc64/2019-11-07/sysutils/usmb.log > > I wonder if we shouldnt rather remove the port itself. Iirc i tried it

Re: [base-gcc] Unbreak sysutils/usmb

2019-11-09 Thread Stuart Henderson
On 2019/11/09 09:35, Landry Breuil wrote: > On Sat, Nov 09, 2019 at 09:16:49AM +0100, Charlene Wendling wrote: > > > > > http://build-failures.rhaalovely.net/sparc64/2019-11-07/sysutils/usmb.log > > > > This is once again a port built with `-Werror' that is breaking after > > the glib2 update. >

Re: [base-gcc] Unbreak sysutils/usmb

2019-11-09 Thread Landry Breuil
On Sat, Nov 09, 2019 at 09:16:49AM +0100, Charlene Wendling wrote: > > > http://build-failures.rhaalovely.net/sparc64/2019-11-07/sysutils/usmb.log > > This is once again a port built with `-Werror' that is breaking after > the glib2 update. > > On macppc, it builds fine [1] once removed. > >

[base-gcc] Unbreak sysutils/usmb

2019-11-09 Thread Charlene Wendling
> http://build-failures.rhaalovely.net/sparc64/2019-11-07/sysutils/usmb.log This is once again a port built with `-Werror' that is breaking after the glib2 update. On macppc, it builds fine [1] once removed. HOMEPAGE [0] returns "Forbidden", and pages on the whole domain are empty. Maybe we