Date: Tue, 2 Apr 2019 14:38:37 -0700
From: bob prohaska <fbsd@www.zefox.net>
To: John F Carr <jfc@mit.edu>
Cc: "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org>, "freebsd-ports@freebsd.org" <freebsd-ports@freebsd.org>
Subject: Re: RPI3, error: invalid operand in inline asm: 'rev16 ${0:w}, ${1:w}'
Message-ID: <20190402213837.GA32014@www.zefox.net>
In-Reply-To: <DD8176DE-9D48-4EC2-8895-5375C9D1C851@exchange.mit.edu>
References: <20190330152327.GA11933@www.zefox.net> <236A3D25-0B4D-46DA-95BA-71DA505CC2E0@exchange.mit.edu> <20190402015956.GA27268@www.zefox.net> <28F4BF7B-4391-4A4B-ABEC-36A154F9FAE2@exchange.mit.edu> <20190402161713.GA30854@www.zefox.net> <20190402180909.GA31620@www.zefox.net> <DD8176DE-9D48-4EC2-8895-5375C9D1C851@exchange.mit.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Apr 02, 2019 at 08:31:12PM +0000, John F Carr wrote: > > > > On Apr 2, 2019, at 14:09 , bob prohaska <fbsd@www.zefox.net> wrote: > > > > On Tue, Apr 02, 2019 at 09:17:13AM -0700, bob prohaska wrote: > >> On Tue, Apr 02, 2019 at 10:39:42AM +0000, 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, does chromium compile? > >> > >> The patch applied without difficulty and I've restarted the make > >> process using portmaster-devel. > >> > > > > The compile stopped again, seemingly with the same error, unchanged. > > > > Oddly, there's also an error immediately before, which has been seen > > before but I thought has been fixed at some point, > > > > In file included from ../../base/third_party/libevent/event.c:49: > > In file included from /usr/include/signal.h:42: > > /usr/include/machine/ucontext.h:46:2: error: unknown type name '__uint128_t' > > __uint128_t fp_q[32]; > > ^ > > 1 error generated. > > > > The relevant parts of the console output are at > > > > http://www.zefox.net/~fbsd/rpi3/portmaster/chromium/r345516/console.txt > > > > in case anybody's willing to take a look. > > > > Thanks for reading, > > > > bob prohaska > > I looked a little closer and figured out why it's failing. The chromium port compiles with options "--target=arm-linux-gnueabihf -march=armv7-a". That means it's using a Linux ABI on 32 bit ARM v7. The byte reverse functions in machine/endian.h do not work with that target. I think the rev* instructions don't exist in ARM v7. > > Does chromium come with object files built for ARM7a on Linux, so that target has to be used? I hope that question is directed to someone else! I can only state that a couple of versions ago chromium compiled and ran on the Pi3. That particular compile session had to be restarted many times to finish. By the time I was able to re-run it, compilation was successful but the executable failed with an error in a shared object library. Since then, roughly early February, chromium hasn't compiled on the Pi3. Prior to early February it compiled with difficulties connected to VM limitations. Thanks for reading! bob prohaska
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190402213837.GA32014>