site  contact  subhomenews

shared-mime-info, vte, sakura in OE

November 02, 2017 — BarryK

Three more. These took 4-5 hours!




Tags: oe

hardinfo, mtr added to OE

November 01, 2017 — BarryK

Two more this morning.



Family stuff for the next few hours, hope to port more packages this evening.

Tags: oe

ufiformat, libtommath ported into OE

October 31, 2017 — BarryK

Did a couple more this morning.



Tags: oe

pmcputemp, mdview, dvd-close added to OE

October 31, 2017 — BarryK

As mentioned in earlier posts, various packages that I compiled in a running Pyro64, are now being ported into OE, so that I will have a more complete automated compile from source. More added today:




Tags: oe

arp-scan, bbe, pnscan added to OE

October 31, 2017 — BarryK

For Pyro64 0.5, I had compiled these as PETs. have now moved them into OE.




Tags: oe

ntpdate utility compiled in OpenEmbedded

October 30, 2017 — BarryK

Most of the binary packages used to build Quirky Pyro64 0.5 were compiled in OE, but not all. A few failed to compile, so I compiled them in a running Pyro64, and a few were never attempted in OE -- so these are all PETs.

Utility ntpdate is used by tasmod's Psync app, that syncs the time/date from an NTP server. Quirky/Easy have a rewritten version of Psync, named Qsync. This utility is in the ntp package.

I compiled ntp as a PET, because the recipe in OE is unsuitable. Unfortunately, although systemd is supposed to be an optional feature in OE, some developers are hard-coding it into build recipes. This makes life difficult for me, as I have to write my own recipe for that package.

I will turn this post into a small tutorial, showing how I wrote my own recipe for ntp.

A search with find revealed the recipe here:


If I could just modify that recipe to suit my needs, I could have created this file:


...where meta-quirky is my custom layer. See the online github repo:

However, I wanted to rewrite the recipe from scratch. The thing is, do not modify the original, create a new one. The new recipe, in my custom layer, will override the original:


How to write a recipe? Actually, this is made easy (well, easier) by a special script:

# recipetool create -o

...this is neat. You specify the URL of the source package, and required name of the recipe file, and it will create a skeleton recipe. Which most likely will need further tweaking.

Examining the original recipe helps, as does having already compiled the package in a running Pyro64. From previous experience having compiled this package, I knew what configure options are needed, and the dependencies.

Dependencies, ah, this is a bit of a dark art. A few years ago, OE was structured differently. Now, each package is compiled in its own isolated mini-filesystem. You have to know all the required deps, and specify them. Not quite all, as the basic packages such as glibc are provided.

Here is my

LIC_FILES_CHKSUM = "file://COPYRIGHT;md5=e877a1d567a6a58996d2b66e3e387003 \
file://libjsmn/LICENSE;md5=5adc94605a1f7a797a9a834adbe335e3 \

SRC_URI = "${PV}.tar.gz"
SRC_URI[md5sum] = "745384ed0dedb3f66b33fe84d66466f9"
SRC_URI[sha256sum] = "ddd2366e64219b9efa0f7438e06800d0db394ac5c88e13c17b70d0dcdf99b99f"

# openssl has libcrypto...
DEPENDS = "bison-native libevent readline libcap openssl"

inherit perlnative autotools pkgconfig

# --with-yielding_select=yes is required when cross-compiling.
EXTRA_OECONF = "--with-yielding_select=yes --enable-ipv6 --with-crypto --enable-linuxcaps --with-lineeditlibs=readline"

# only want this one executable...
do_install () {
mkdir -p ${D}/usr/sbin
install -m 755 ${B}/ntpdate/ntpdate ${D}/usr/sbin

SUMMARY = "NTP is a protocol designed to synchronize the clocks of computers over a network"

I have added a few things to the original skeleton. For example, the original only has "bison-native" as dependency.

As I only want the ntpdate utility, I created a custom install function. Those variables are pre-defined: D=destination, B=build and S=source paths. The build folder is usually different from the source.

To examine the end result, the entire build is here (in the case of my own hard drive):


...I did an "ldd ./ntpdate" to check that it had all the expected libs. Yep, ok.

To do the build, I added the ntp package by appending this line "IMAGE_INSTALL_append = " ntp"":


Then, to do the actual build:

# bitbake -c build ntp

If there is an error, and I did get one, I advise cleaning out the entire build. Although you could just run the "build" command again, some packages won't like it. The "clean" command erases everything, all of folder "4.2.8p10-r0" shown above.

# bitbake -c clean ntp

...then run a "build". The final installed result can be seen here:

/mnt/sdb1/projects/oe/oe-quirky/buildPC/tmp-glibc/work/nocona-64-oe-linux/ntp/4.2.8p10-r0/image is the content of this image folder that will be imported into woofQ. However, one final step:

# bitbake -g core-image-quirky

...this creates some package-list and package-dependency files, pn-buildlist, and The woofQ import script reads these, which is why they must be updated.


Over in woofQ, there are two scripts for importing binary packages from OE, 0pre-oe and 0pre-oe-add. The former was run originally, the latter is for importing additional packages. Just run 0pre-oe-add:

# ./0pre-oe-add

...and it picks up the new ntp package and offers to import it.

It will also pickup packages previously in OE, now removed, and offer to remove them from woofQ.

Tags: oe

Quirky Pyro64 0.5 coming soon

October 27, 2017 — BarryK

Advance notice, I plan to upload Quirky Pyro64 0.5 in a couple of days. This is Quirky Linux built from packages compiled from source in OpenEmbedded.

Right now, have started a recompile from scratch in OE, then tomorrow should be able to import the binary packages to woofQ, then build Pyro64 0.5.

I intend to upload all of the binary packages, and the source packages, to ibiblio. The binary packages are about 1.2GB, and uploading this lot is not something that I want to do that often, as my only Internet access is via my mobile phone.

I don't have a landline phone, just a mobile. I am on prepaid, not a plan, and pay AU$40 for 6GB, so that's my allocation per month, which is pitiful. I can top it up within a month, AU$10 for 1GB.

These Internet expenses add up, and I am thinking of bringing back a PayPal donate button. I had one years ago, and enough donations trickled in to pay the Internet costs. But that was when I was leading the Puppy Linux project.

Well, I will think about whether to put up a donate button or not. Actually, what prompted me to think about this, was recently there have been a couple of enquiries from people who wanted to donate to my work.


Note, 0.5 will have Samba, that I have compiled in a running Pyro64, not in OE, so it is a PET package. The Samba in OE wants kerberus dependency, which I did not want, so experimented with configuration options, for the smallest build, and using the inbuilt heimdal instead of kerberus.

Even so, my PET is 11MB, whereas 01micko got his samba PET down to about 8MB -- though he has an older version.

I hope that I haven't configured-out too much functionality, and that it works OK. Well, testers will be welcome when 0.5 comes out.

For the record, here are my configure options:

# ./configure --prefix=/usr --localstatedir=/var --sysconfdir=/etc --libdir=/usr/lib --enable-fhs --includedir=/usr/include --bindir=/usr/bin --sbindir=/usr/sbin --with-configdir=/etc/samba --with-piddir=/var/run --with-privatedir=/etc/samba/private --with-privatelibdir=/usr/lib --with-modulesdir=/usr/lib --with-lockdir=/var/cache/samba --with-logfilebase=/var/log/samba --enable-cups --with-acl-support --with-automount --with-quotas --with-syslog --without-winbind --with-ldap --without-pam --without-ads --libexecdir=/usr/libexec --datadir=/usr/share --without-dmapi --without-fam --without-lttng --without-systemd --disable-avahi --enable-gnutls --without-sendfile-support --nopyc --nopyo --extra-python=/usr/bin/python3 --without-ad-dc --without-ntvfs-fileserver

...if you know something about configuring Samba, what do you think? Note that Pyro64 has all 64-bit libs in /lib and /usr/lib, with /lib64 and /usr/lib64 being symlinks.

Feedback can go here. This is where 0.5 will be announced:

Tags: oe, quirky

The return of Pyro64

October 23, 2017 — BarryK

Every now and again, I get frustrated by the bloatedness and weirdness of Ubuntu and Debian DEBs, that I am using in Quirky and Easy builds. I did play with Pyro64, packages compiled from source in OpenEmbedded, but only briefly.

But have just completed a compile in OE, for the x86_64 architecture (not x32), and built a new Pyro64, and it sure is looking good.

The difference in size of deployed distro is incredible. Quirky Pyro64 (now at version 0.3.3) is 274MB, and that includes LibreOffice, whereas Quirky Xerus 8.3 is 331MB. These have about the same functionality. Furthermore, I will probably be able to reduce the size of the Pyro64 build, as this is an early pre-alpha build.

If Pyro64 is so good, why did I previously go back to building with Ubuntu DEBs?

Well, there were some issues at the time, for example with the video. However, I have tackled some of these, and things are looking very good.

Then there is the Ubuntu DEB repository. I guess that is the big thing, so convenient. With Pyro64, everything has to be compiled. Almost, there is a small repo of packages that I compiled, and we can add to it.

So, 'oe-qky-src' is active again:

Oh, one other thing. SeaMonkey is running without spitting out heaps of complaints to stderr -- that is very reassuring. I am wondering if I am just imagining things, but everything seems faster, including SeaMonkey.

The Pyro64 binary packages can be used for building Quirky and Easy. I am thinking, will bring out another Quirky, and if testers like it, might go the same way for Easy.

Tags: oe