Road trip dates setup

So this year we are going to Moomins World, Naantali, Finland. All dates are set, PTO granted, car checked.

Trip will start on 5th July with Szczecin -> Łódź trip. There I will take my 6 years old daughter Mira to event named “Old computers & games” to show her which kind of computers I used. Then Łódź -> Olecko to visit my mother. Will spend few days there.

And then crazy trip starts. Friday 11th will take us to Klaipėda, Lithuania to see dolphins. Next day we go to Rīga, Latvia through Hill of Crosses in Šiauliai, Lithuania. Look around and on Sunday -> Tallinn, Estonia where we will spend ~24h as this direction is mostly to not drive everything in one day.

Then ferry to Helsinki, some sightseeing and on 15th we will go to Turku and stay there in yet another hotel.

Finally on 16th July plan is to spend whole day in Moomins World in Naantali. Walk, see, take photos and have a good time.

Next day equals Tampere. Moomins museum and visiting Thomas Ruecker. Then quick run to catch ferry in Helsinki so we can spend some time in Tallinn again and do some proper sightseeing. Similar with Riga and finally Devils’ Museum in Kaunas, Lithuania on last day.

Few days of rest in Olecko and go back home probably through Gdańsk.

I hope that it will be the adventure. One of those nasty disturbing uncomfortable things which you remember for long ;D

From a diary of AArch porter –- testsuites

More and more software come with testsuites. But not every distribution runs them for each package (nevermind is it Debian, Fedora or Ubuntu). Why it matters? Let me give example from yesterday: HDF 4.2.10.

There is a bug reported against libhdf with information that it built fine for Ubuntu. As I had issues with hdf in Fedora I decided to look and found even simpler patch than one I wrote. Tried it and got package built. But that’s all…

Running testsuite is easy: “make check”. But result was awesome:

!!! 31294 Error(s) were detected !!!

It does not look good, right? So yesterday I spent some time yesterday on searching for architecture related check and found main reason for so big amount of errors — unknown systems are treated as big endian… Simple switch there and from 31294 it dropped to just 278 ones.

Took me a while to find all 27 places where miscellaneous variations of “#if defined(__aarch64__)” were needed and finally got to point where “make check” simply worked as it should.

So if you port software do not assume it is fine once it builds. Run testsuite to be sure that it runs properly.

AArch64 is in the house

Today FedEx courier delivered me a package. Inside was APM Mustang in 19″ rack case.

I unpacked, grabbed all required cables from my cable boxes (power, Ethernet, serial), connected it and booted. It arrived at very good moment as we are in a middle of Fedora 21 mass rebuild so I do not have to use remote machines anymore.

Will not write about technical details cause those are already known (8 cores, 16GB ram, SATA storage, 1GbE networking). Do not expect benchmarks as I am not allowed to publish results. If you want to compare build speed then go to Launchpad and check how long it takes to build Ubuntu packages for arm64 target.

My plans for machine? Run Fedora rawhide, fix building issues. I also plan to play with virtualization to check how Ubuntu and Debian work.