• armv6
• ports

Page to track building of ports for armv6.

Package build status

As of a recent -CURRENT poudriere build on the cluster, there were 969 IGNOREd ports (including 13 blacklisted) and 130 failures, for a total number of SKIPPED 2755. (You may also view the index to all the builds on -CURRENT.)

Some of the IGNOREd ports are expected failures for non-x86 architectures (e.g. no linux emulation support). This list attempts to help coordinate the efforts to fix the other ones.

Patches already available for testing

Please see Bugzilla search on "armv" and "attachment is patch"; sorted by Summary (which is usuallly portname)

A brief glance suggests these will unblock at least 100 ports.

MarkLinimon continues to test a few of them as of 20171218.

How you can help

• mmel@ interested in top graphics metaports (qt4/qt5/mate/gnome3/kde4) and is actively submitting patches.

• MikaelUrankar has also been submitting many patches.

• MarkLinimon is going through the errorlogs to classify errors, marking ports broken, and submitting patches.

  • this patch conditionalizes firebird25 to only x86, which is a blocker for libreoffice. It seems harmless on my amd64 machine but needs an -exp run.

• IanLepore is interested in some of the math and scientific ports.

Build failures

Build failures that are already known

These ports have already been marked BROKEN or IGNORE.

• BROKEN is for ports that should be expected to build on the arch, but have failures.

• IGNORE is for ports that are not expected to build on the arch.

In general only the first case is worth working on; however, port maintainers are inconsistent in their use.

The best way to browse these problems:

• go to, e.g., a recent -CURRENT poudriere build on the cluster

• scroll down to Ignored ports

• right-click on Reason to sort alpha

The Search textbox may be used to narrow down the results.

Examples that should be relatively easy to address:

• asm or assembler: uses x86-specific assembler

• compiler does not support

• c99, c11

Less easy:

• Blacklisted: it was intentionally not built on the cluster.

• runaway builds

• FreeBSD 12.0: probably not your problem

Finally, the reason may be missing. Contact MarkLinimon if you need help.

Build failures that are new

These fall into several categories:

• ports that have recently been added
• ports that are actually broken elsewhere (e.g. "everywhere", "only on -CURRENT", and so forth)
• ports that newly fail on armv6.

It requires some detective work to figure out which is which, but for now, let's narrow it down to the latter group.

updates to bring the text below up-to-date are pending as of 20171218

Common errors

package fails to build under emulation but ok on real hardware

TBA

runaway process

In general you will want to confirm from multiple runs.

• devel/aws-sdk-cpp
• devel/rcs
• devel/rcs57
• games/flightgear-data
• games/urbanterror-data
• games/ufoai-data
• java/openjdk8-jre (statistical)
• lang/erlang-runtime19
• lang/erlang-runtime20
• math/suitesparse

problems with qemu

In general you will want to confirm from multiple runs.

• biology/plinkseq: it uses protobuf see ports r379486 for a possible fix

• graphics/gnofract4d
• mail/cone
• science/libint
• x11/xgrab:

  • invokes Xvfb :0 which fails under emulation: XKB: Failed to compile keymap
    Keyboard initialization failed. This could be a missing or incorrect setup of xkeyboard-config.
    Fatal server error: (EE) Failed to activate virtual core keyboard: 2(EE)

CategoryPorts