Category: Uncategorized (Page 4 of 5)

I have been writing regular updates to the Alien’s ARM page on this blog which can be found in the top of left sidebar. Readers of this blog who only visit the blog’s front page, will probably not have noticed, so I decided to write a more visible status update on the main page.

When I first booted my “current state of affairs” on the ARM Chromebook (what I had at that time was a mix of packages somewhere between Slackware 13.37 and 14.0) it was clear that I had a lot of work ahead of me. The X.Org that I had was unable to start on the laptop. I could get as far as a terminal and get a wireless network connection functional, but I really wanted a graphical enviroment.

During the past two weeks I have been steadily updating SlackBuild scripts, and in the last 5 days I (re-)built 637 packages! Long live automation build scripts and distcc.

Creating packages is nice, but I needed to see the results.What I was working towards was the X.Org of Slackware-current and the XFCE which we also have in -current.

I am happy to announce: XFCE works!
Now at least I know that I didn’t do all tthis work for nothing 🙂

Running XFCE unveiled several annoying bugs in packages like pango, gtk+2 and gtk+3 which I fixed today. I also made a first attempt at compiling KDE and quickly ran into further packaging bugs (pciutils and qt need to be fixed). I had hopes that I could dump the content of the SD card into a downloadable image and make that available for download, but I felt that the sources were more important at this moment. Who has a Samsung ChromeBook and is willing to play-test this? I may change my mind tomorrow if there is some interest.

Just for fun: here is a 1’13” video of me logging in as “alienarm” and starting X, then loading up my blog page in firefox: http://dl.dropbox.com/u/2329942/VIDEO0006.3gp .VLC and the browser-plugin gecko-mediaplayer will be able to play this .3gp video which I shot with my phone (hence the shaky images).

I already uploaded the latest source code to taper .I have refreshed the sources on http://taper.alienbase.nl/mirrors/alienarm/bootstrap/source.local/ – but there is still a lot of work to do before I have fully caught up with slackware-current. I do not know if the stage1.sh bootstrap script still works with all the new sources, I have fixed at least the coreutils build though.

What I have also set up is a git repository for the sources. You can access this repository through a gitweb interface. If you want to clone the repository, you can use the git URI git://taper.alienbase.nl/bootstrap.git . Commit access is limited to myself for the moment, I have no intention of allowing anyone direct commit access except for other Slackware core-team members.

If you want to start compiling ARM packages yourself using these sources, first create a SlackBuild configuration file “/etc/slackbuild/machine.conf” with the following contents which will override the SlackBuild defaults for ARM hardfloat platforms like the Tegra and Exynos CPUs.:

export ARCH=”armv7hl”
export SLKCFLAGS=”-O2 -march=armv7-a -mfpu=vfpv3-d16″
export LIBDIRSUFFIX=””

You can use my rootfs to setup a working chroot environment if you want. More instructions will follow, perhaps it is wise to wait for those. I will leave that for another post, or perhaps a page on the SlackDocs wiki..

Have fun! Eric

A while ago when Libreoffice 3.5.0 was released, I found out to my chagrin that I was unable to successfully compile it on Slackware 13.37.

There was no change when 3.5.1 came out, but thankfully we now have a new maintenance release, LibreOffice 3.5.2. Lo and behold, I could successfully compile packages, but the SlackBuild needed several updates because the build process changes quite dramatically between the various 3.x releases. The developer team is slowly getting rid of the old StarOffice heritage, and ultimately the dependency on Java for the compilation should be completely removed. We’re note yet there however.

What I did manage is to get rid of the requirement to install an xulrunner package in order to create the LibreOffice packages. I updated my virtual machine running Slackware 13.37 with all the patches which were released by Pat. This includes a spiced-up version of Seamonkey which originally got the updates in order to be able to compile OpenJDK, but it is also able to aid in the compilation of LibreOffice. All you need to add now are packages for  Apache Ant and the Archive:Zip Perl module.

You can find the packages for Slackware 13.37 (and -current) in the usual locations (all of the mirrors below also offer rsync access):

• http://slackware.com/~alien/slackbuilds/libreoffice/ (master site)
• http://taper.alienbase.nl/mirrors/people/alien/slackbuilds/libreoffice/
• http://slackware.org.uk/people/alien/slackbuilds/libreoffice/
• http://scw.net.br/alien/slackbuilds/libreoffice/
• http://repo.ukdw.ac.id/alien-libreoffice/
• http://alien.slackbook.org/slackbuilds/libreoffice/

One word of caution!

LibreOffice changed the location of its configuration directory (again). Originally using ~/.ooo it switched to ~/.libreoffice which will probably be where you will find your custom settings stored. The 3.5 releases however, use ~/.config/libreoffice . The best thing to do is move your current configuration directory to the new location, so that LibreOffice keeps working as expected:

$ mv ~/.libreoffice ~/.config/libreoffice

If you had already started the new LibreOffice program, then you will have to delete the fresh and almost empty ~/.config/libreoffice directory first of course.

Cheers, Eric