[Buildroot] test-pkg failed, then what?

Peter Korsgaard peter at korsgaard.com
Sat Sep 30 06:55:34 UTC 2023


>>>>> "Yanghao" == Yanghao Cheng <YanghaoBillCheng at gmail.com> writes:

 > Hello everyone,
 > I am trying to add the wiringpi package back as now that there's a
 > continuation on Github.
 > https://github.com/WiringPi/WiringPi

 > I brought the old config.in and .mk files off the old commit that removed
 > them and adjusted the site.
 > I tested it on my board and it builds. Prior to submission, I also tested
 > the package with test-pkg script. But the tests either failed or were
 > skipped.

 > I've read the section 18.25 of the manual, but there isn't any instruction
 > to go about fixing the failed test.

 > Following is the output

 >> $ utils/test-pkg -c wiringpi.config -p wiringpi
 >> bootlin-armv5-uclibc [1/6]: FAILED
 >> bootlin-armv7-glibc [2/6]: FAILED
 >> bootlin-armv7m-uclibc [3/6]: SKIPPED
 >> bootlin-x86-64-musl [4/6]: FAILED
 >> br-arm-full-static [5/6]: SKIPPED
 >> sourcery-arm [6/6]: FAILED
 >> 6 builds, 2 skipped, 4 build failed, 0 legal-info failed, 0 show-info
 >> failed

test-pkg by default builds under ~/br-test-pkg. After a failed build you
should have a number of subdirs there, each with a logfile explaining
the error.

-- 
Bye, Peter Korsgaard



More information about the buildroot mailing list