From: Peter Korsgaard <peter@korsgaard.com>
To: Yanghao Cheng <YanghaoBillCheng@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] test-pkg failed, then what?
Date: Sat, 30 Sep 2023 08:55:34 +0200 [thread overview]
Message-ID: <87lecocfq1.fsf@48ers.dk> (raw)
In-Reply-To: <CAGnyD8udPeWvFXjQGrV2kDhMRLVv9T0aNNAJPTgxjQNLr-BU8w@mail.gmail.com> (Yanghao Cheng's message of "Mon, 25 Sep 2023 15:42:59 -0700")
>>>>> "Yanghao" == Yanghao Cheng <YanghaoBillCheng@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
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-09-30 6:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-25 22:42 [Buildroot] test-pkg failed, then what? Yanghao Cheng
2023-09-30 6:55 ` Peter Korsgaard [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lecocfq1.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=YanghaoBillCheng@gmail.com \
--cc=buildroot@buildroot.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox