[Slackbuilds-users] Unstated requirement (apparently) to build octave

[Kyle Guinn]

On 3/21/20, Jim Diamond <JimDiamond at ns.sympatico.ca> wrote:
> Well, that may be so.  However, after 1525 seconds of compiling on a
> somewhat low-end Xeon, here is the end of the show:
>   ...
>   help/which.m ................................................... PASS
> 8/8
>   image/cmpermute.m .............................................. PASS
> 19/19
>   image/cmunique.m ............................................... PASS
> 19/19
>   image/colormap.m ............................................... PASS
> 9/9
>   image/contrast.m ............................................... PASS
> 1/1
>   image/frame2im.m ............................................... PASS
> 4/4
>   image/getframe.m ...............................................libGL
> error: failed to authenticate magic 2
> libGL error: failed to load driver: i965
> fatal: caught signal Illegal instruction -- stopping myself...
> /bin/sh: line 1: 14187 Illegal instruction     (core dumped) /bin/sh
> ../run-octave --norc --silent --no-history -p /tmp/SBo/octave-5.2.0/test/mex
> /tmp/SBo/octave-5.2.0/test/fntests.m /tmp/SBo/octave-5.2.0/test
> Makefile:27887: recipe for target 'check-local' failed
> make[3]: *** [check-local] Error 132
> make[3]: Leaving directory '/tmp/SBo/octave-5.2.0'
> Makefile:26265: recipe for target 'check-am' failed
> make[2]: *** [check-am] Error 2
> make[2]: Leaving directory '/tmp/SBo/octave-5.2.0'
> Makefile:25976: recipe for target 'check-recursive' failed
> make[1]: *** [check-recursive] Error 1
> make[1]: Leaving directory '/tmp/SBo/octave-5.2.0'
> Makefile:26267: recipe for target 'check' failed
> make: *** [check] Error 2
>
>
> I will point out that on the compiling Xeon, I am using the
> Nouveau driver, and the string "965" does not appear anywhere in
> /var/log/Xorg.0.log.
>
> However, on the laptop I am ssh'ed in from, Xorg.0.log has
> [     8.295] (II) Module vesa: vendor="X.Org Foundation"
> [     8.295]    compiled for 1.18.0, module version = 2.3.4
> [     8.295]    Module class: X.Org Video Driver
> [     8.295]    ABI class: X.Org Video Driver, version 20.0
> [     8.295] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets:
>         i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G,
>         915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM,
>         Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35,
> Q33,
>         GM45, 4 Series, G45/G43, Q45/Q43, G41, B43
>
> Also, running xrandr and/or xdpyinfo from the Xeon shows that a
> program running on the Xeon can find out my screen configuration and
> other information, so I can imagine some nosy X program finding out
> what is going on.  In fact, running glinfo on the Xeon gives output
> starting with
>         libGL error: failed to authenticate magic 2
>         libGL error: failed to load driver: i965
>         GL_VERSION: 3.0 Mesa 11.2.2
> so again, programs running on the Xeon can know a lot about the laptop
> from which I ssh'ed into the Xeon.
>
> This may have nothing to do with anything, but the fact that the above
> error message whined about i965 and the only i965 driver in use that I
> know about is the one on my laptop made me put those together.
> However, I freely admit the reasoning is not rock-solid.

I've got a similar setup where I've SSH'd into other machines to build
octave.  I've seen some similar errors with some of the graphics
tests, but none of them were fatal and it continued to build the
package.

If all else fails, just comment out the `make check` line.

-Kyle