On Tue, Apr 02, 2019 at 08:31:12PM +, John F Carr wrote:
> >
> > On Apr 2, 2019, at 14:09 , bob prohaska wrote:
> >
> > On Tue, Apr 02, 2019 at 09:17:13AM -0700, bob prohaska wrote:
> >> On Tue, Apr 02, 2019 at 10:39:42AM +, John F Carr wrote:
> >>>
> >>> The problem I mentioned is with
On Tue, Apr 02, 2019 at 09:17:13AM -0700, bob prohaska wrote:
> On Tue, Apr 02, 2019 at 10:39:42AM +, John F Carr wrote:
> >
> > The problem I mentioned is with the system. I filed a bug:
> > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236920
> >
> > If you change the system header /us
On Tue, Apr 02, 2019 at 10:39:42AM +, John F Carr wrote:
>
> The problem I mentioned is with the system. I filed a bug:
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236920
>
> If you change the system header /usr/include/machine/endian.h
> according to the path in that bug report, doe
On Sat, Mar 30, 2019 at 05:50:35PM +, John F Carr wrote:
>
>
> > On Mar 30, 2019, at 11:23 , bob prohaska wrote:
> >
> > In a recent attempt to compile www/chromium on an RPI3 running r345516
> > compilation stopped with repeated reports of
> >
> > /usr/include/machine/endian.h:89:19: err
In a recent attempt to compile www/chromium on an RPI3 running r345516
compilation stopped with repeated reports of
/usr/include/machine/endian.h:89:19: error: invalid operand in inline asm:
'rev16 ${0:w}, ${1:w}'
Chromium compiled on the same host a couple of months ago, but the
executable fa
