Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 11 Jan 2017 11:20:27 -0200
From:      "Dr. Rolf Jansen" <rj@obsigna.com>
To:        freebsd-arm@freebsd.org
Subject:   Re: lldb on BeagleBone Black
Message-ID:  <8FDE5FCC-9BA8-4601-A32E-04FBAB5FFBEA@obsigna.com>
In-Reply-To: <3DA2368D-AE7B-4D69-A634-2861D2EFA9AE@obsigna.com>
References:  <3DA2368D-AE7B-4D69-A634-2861D2EFA9AE@obsigna.com>

next in thread | previous in thread | raw e-mail | index | archive | help
> Am 09.01.2017 um 00:59 schrieb Dr. Rolf Jansen <rj@obsigna.com>:
>=20
> I am running FreeBSD 12.0-CURRENT (BEAGLEBONE) #0 r311461: Fri Jan  6 =
03:13:01 UTC 2017
>=20
> Does any of the llvm ports build on the BBB? I am looking for a =
working lldb, and pre-build packages are not available, and I fear there =
is a certain reason why not -- perhaps build failures?
>=20
> Therefore, is it actually possible to obtain a working lldb (with gui =
option) for armv6 by building e.g. devel/llvm-devel on my BeagleBone =
Black?
>=20
> Which of the llvm-ports would be most promising?

I tried building devel/llvm-devel having the ports tree attached on a =
fast USB disk. After 36 h of building it bailed out because of some =
obscure error in the AArch64 code generator.

Finally, I don't think that building any LLVM port is viable on the BBB, =
first because building takes forever. The BBB needs 1 minute for =
compiling a C++ file which got only 20 lines of code. Of course this =
comes because the C++ experts tend for some ingenious reasons to hide =
all the implementations into the headers which need then to be compiled =
again and again. Second, it doesn't make sense at all to build LLVM for =
all the possible targets on a machine which I will never ever use for =
cross-development.

I will now try a non-ports build of LLVM 3.91 for the armv6 target only.

Best regards

Rolf




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8FDE5FCC-9BA8-4601-A32E-04FBAB5FFBEA>