Project

General

Profile

Actions

Feature #1069

closed

Bring Buildroot build up to date with PiBox.

Added by Hammel 4 months ago. Updated 4 months ago.

Status:
Closed
Priority:
Immediate
Assignee:
Target version:
Start date:
05 Nov 2023
Due date:
% Done:

100%

Estimated time:
Severity:
01 - Critical

Description

The Xeon buildroot build should likely be exactly the same as the PiBox build since the PiBox build does not build any RPi specific features from Buildroot (they are built separately).

Merge the PiBox buildroot.cfg into Xeon's version. And then update libpibox and pibox-network-config so they are up to date with any recent changes in the PiBox dev system build.

Actions #1

Updated by Hammel 4 months ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 20

This required updating the Xeon docker image with --fix-missing added to git updates.

The build works up to libpibox, where it fails with the following.

pibox.c: In function 'piboxLoadDisplayConfig':
pibox.c:173:9: warning: 'fclose' called on pointer returned from a mismatched allocation function [-Wmismatched-dealloc]
  173 |         fclose(fd);
      |         ^~~~~~~~~~
pibox.c:171:14: note: returned from 'popen'
  171 |         fd = popen( CMD_FBSIZE, "r");
      |              ^~~~~~~~~~~~~~~~~~~~~~~
touchProcessor.c:33:10: fatal error: tslib.h: No such file or directory
   33 | #include <tslib.h>
      |          ^~~~~~~~~
compilation terminated.

The errors on fclose I thought were fixed previously. It's likely I'm using an old archive and need to remove it and try again.

The missing tslib.h is likely because tslib is not enabled in the Xeon buildroot config.

Actions #2

Updated by Hammel 4 months ago

  • Status changed from In Progress to Closed
  • % Done changed from 20 to 100

Buildroot build has been updated to match the PiBox dev system build.

This allowed the xeon pkglist to build cleanly.

Changes tested, committed and pushed.

Closing issue.

Actions

Also available in: Atom PDF