From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Ramon Fried <rfried.dev@gmail.com>
Cc: "buildroot@buildroot.org" <buildroot@buildroot.org>
Subject: Re: [Buildroot] [autobuild.buildroot.net] Your daily results for 2022-05-20
Date: Sat, 21 May 2022 16:44:40 +0200 [thread overview]
Message-ID: <20220521164440.0f0df25f@windsurf> (raw)
In-Reply-To: <CAGi-RUKF09JmK_EACoQdBnS_Aw8G6Ep88Lx3rCHY3ZkxrqLvmQ@mail.gmail.com>
Hello Ramon,
On Sat, 21 May 2022 17:23:04 +0300
Ramon Fried <rfried.dev@gmail.com> wrote:
> > Build failures related to your packages:
> >
> > arch | reason | url
> > -------------+--------------------------------+---------------------------------------------------------------------------------
> > m68k | bitwise-0.43 | http://autobuild.buildroot.net/results/9e3b9a148bc84004fde4dfe9b389ca2b359a92e2
> > riscv64 | bitwise-0.43 | http://autobuild.buildroot.net/results/348afc2a0fde85c098a12b58e8e2dcc3780bbb6b
> >
> >
> > Thanks for your contribution to Buildroot!
> >
> > --
> > http://autobuild.buildroot.net
> Hi thomas.
> as I mentioned in an earlier mail, it looks like it is probably in dependencies.
> I took riscv64 as an example and built the qemu
> qemu_riscv64_virt_defconfig + bitwise locally.
> It is built successfully.
>
> How was the config file for building the above created ?
If you follow the links above, you end up in a directory that contains
the full .config file (config) as well as the corresponding defconfig
(named "defconfig"). These are the configurations that triggered the
build issue.
You can also reproduce a build issue by downloading the script
https://git.busybox.net/buildroot-test/plain/utils/br-reproduce-build
and run:
./br-reproduce-build 9e3b9a148bc84004fde4dfe9b389ca2b359a92e2
Where 9e3b9a148bc84004fde4dfe9b389ca2b359a92e2 is the identifier of the
failed build, as visible in the autobuild.buildroot.net URL.
Let me know if this helps!
Thomas Petazzoni
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next parent reply other threads:[~2022-05-21 14:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <62886d67.1c69fb81.ac372.4710SMTPIN_ADDED_MISSING@mx.google.com>
[not found] ` <CAGi-RUKF09JmK_EACoQdBnS_Aw8G6Ep88Lx3rCHY3ZkxrqLvmQ@mail.gmail.com>
2022-05-21 14:44 ` Thomas Petazzoni via buildroot [this message]
2022-05-21 16:47 ` [Buildroot] [autobuild.buildroot.net] Your daily results for 2022-05-20 Ramon Fried
2022-05-23 15:46 ` Thomas Petazzoni via buildroot
2022-05-23 18:24 ` James Hilliard
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=20220521164440.0f0df25f@windsurf \
--to=buildroot@buildroot.org \
--cc=rfried.dev@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
/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