On 3/31/19 2:19 PM, Gordan Bobic wrote:
> I blew the dust off my Chromebook after a year and came across a few
> interesting issues.
>
> Firefox:
> Current release has no FF package.
I know, I cannot get it to build any more. I choose to not include it
over having an old and vulnerable version.
IIRC, FF needs to be build with rust, which needs a recent llvm and llvm
after 3.7 just does not support armv5 any more.
OK, I tested a bit with my systems:
* the odroid XU4, runs Xorg normal. I previously configured it to
run KDE. it shows the graphical login after boot. You can login.
All normal. FF (52.8) and TB (52.9) crash with a segmentation
fault. Konqueror (the KDE browser) just works.
* the raspberry 3B shows the "something went wrong" page. It is
difficult to debug on this system. it has *all* packages installed
(I test here if newly build packages do install). "startx" also
does not work here. I probably need to test with a more normal
installed system.
Jacco
--
You received this message because you are subscribed to the Google Groups "redsleeve-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to redsleeve-use...@googlegroups.com.
To post to this group, send an email to redslee...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/redsleeve-users/1c510099-674d-2871-dd40-ed0dcec0acdd%40redsleeve.org.
For more options, visit https://groups.google.com/d/optout.
Yes, that's the one.
I don't recall what triggered me to build it with this llvm version ...
If you're interested, I still got the buildlogs and other mock artefacts from both builds.
Jacco
To view this discussion on the web, visit https://groups.google.com/d/msgid/redsleeve-users/CAMx4oe3WrpNL40nVcLLjmA%2BRgq_t2oXRRvUM1i3Ts9bphYJmsw%40mail.gmail.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/redsleeve-users/637a5e98-b16b-5315-f1c0-98da5c0842da%40redsleeve.org.
Not sure which issue you refer to, there are multiple in that threat. However, what I can see from my logs is that 'autogen.sh' is not used. (no surprise, it is also not in the SPEC)
I also had some unbuildable drivers, which I hacked out of the build. This is the configure statement that builded the last mesa on RS7:
./configure --build=armv5tel-redhat-linux-gnueabi --host=armv5tel-redhat-linux-gnueabi --program-prefix= --disable-dependency-tracking --prefix=/usr --exec-prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin --sysconfdir=/etc --datadir=/usr/share --includedir=/usr/include --libdir=/usr/lib --libexecdir=/usr/libexec --localstatedir=/var --sharedstatedir=/var/lib --mandir=/usr/share/man --infodir=/usr/share/info --enable-libglvnd --enable-selinux --enable-osmesa --with-dri-driverdir=/usr/lib/dri --enable-egl --disable-gles1 --enable-gles2 --disable-xvmc --enable-vdpau --with-egl-platforms=x11,drm,wayland --enable-shared-glapi --enable-gbm --disable-opencl --enable-glx-tls --enable-texture-float=yes --enable-gallium-llvm --enable-dri --with-gallium-drivers=swrast,r300,freedreno,nouveau,virgl --with-dri-drivers=nouveau,radeon,r200
Jacco