On 30/11/18 23:23, Daniel Kahn Gillmor wrote:
entry=entry@entry=0xf051c962
Well that looks to be your problem, an unaligned pointer. You need to figure
out where it is coming from and fix it.
On Fri 2018-11-30 10:10:55 -0800, Steve Langasek wrote:
> On Fri, Nov 30, 2018 at 09:48:28AM +0100, Héctor Orón Martínez wrote:
>> Hello Steve,
>
>> Since you are doing a study building armhf on arm64 hardware, see
>> below yet another failure example.
>
> As a data point, this version of knot-res
On Fri, Nov 30, 2018 at 09:48:28AM +0100, Héctor Orón Martínez wrote:
> Hello Steve,
> Since you are doing a study building armhf on arm64 hardware, see
> below yet another failure example.
As a data point, this version of knot-resolver built successfully in Ubuntu:
https://launchpad.net/ubun
Hi Steve--
On Fri 2018-11-30 09:48:28 +0100, Héctor Orón Martínez wrote:
> Since you are doing a study building armhf on arm64 hardware, see
> below yet another failure example.
relevant links to knot-resolver failures on arm64:
https://bugs.debian.org/907729
https://gitlab.labs.nic.cz/knot/kn
Hello Steve,
Since you are doing a study building armhf on arm64 hardware, see
below yet another failure example.
Regards
Missatge de Daniel Kahn Gillmor del dia dj.,
22 de nov. 2018 a les 13:49:
>
> Hi armhf build maintainers--
>
> knot-resolver 3.1.0-1 is failing on arm-arm-01:
>
>
> ht
> > Many of those chipsets you list, as I understand, have a mesa driver
> > for them that support opengl and gles.
> > Such as freedreno which supports A4XX series. https://mesamatrix.net/
> >
> > Keep in mind, only the proprietary drivers seem to not support opengl
> > while the hardware is perfe
6 matches
Mail list logo
