From: catalyst@jiji.arm.dev.gentoo.org
To: releng@gentoo.org,gentoo-releng-autobuilds@lists.gentoo.org
Subject: [gentoo-releng-autobuilds] [mips-qemu-auto] Catalyst fatal build error - stage1-mips2_softfloat-o32-systemd.spec
Date: Tue, 13 Jun 2023 03:02:01 +0000 [thread overview]
Message-ID: <99654c8b5123c7ecf04914c39016843f.root@jiji.arm.dev.gentoo.org> (raw)
*** Running command: time catalyst -a -c /etc/catalyst/catalyst.conf -f /tmp/catalyst-auto.20230609T144701Z.p7h0Bs/specs/stage1-mips2_softfloat-o32-systemd.spec
13 Jun 2023 03:02:01 -00: NOTICE : Loading configuration file: /etc/catalyst/catalyst.conf
NOTICE:catalyst:Loading configuration file: /etc/catalyst/catalyst.conf
13 Jun 2023 03:02:01 -00: NOTICE : conf_values[options] = ['autoresume', 'bindist', 'kerncache', 'pkgcache', 'clear-autoresume']
NOTICE:catalyst:conf_values[options] = ['autoresume', 'bindist', 'kerncache', 'pkgcache', 'clear-autoresume']
13 Jun 2023 03:02:01 -00: NOTICE : Processing spec file: /tmp/catalyst-auto.20230609T144701Z.p7h0Bs/specs/stage1-mips2_softfloat-o32-systemd.spec
NOTICE:catalyst:Processing spec file: /tmp/catalyst-auto.20230609T144701Z.p7h0Bs/specs/stage1-mips2_softfloat-o32-systemd.spec
13 Jun 2023 03:02:01 -00: ERROR : CatalystError: Unknown host machine type mips2_softfloat
ERROR:catalyst:CatalystError: Unknown host machine type mips2_softfloat
Command exited with non-zero status 2
0.17user 0.03system 0:00.21elapsed 99%CPU (0avgtext+0avgdata 29620maxresident)k
32inputs+0outputs (0major+5642minor)pagefaults 0swaps
Full build log at /tmp/catalyst-auto.20230609T144701Z.p7h0Bs/log/stage1-mips2_softfloat-o32-systemd.log
next reply other threads:[~2023-06-13 3:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-13 3:02 catalyst [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-06-18 9:43 [gentoo-releng-autobuilds] [mips-qemu-auto] Catalyst fatal build error - stage1-mips2_softfloat-o32-systemd.spec catalyst
2023-06-24 12:51 catalyst
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=99654c8b5123c7ecf04914c39016843f.root@jiji.arm.dev.gentoo.org \
--to=catalyst@jiji.arm.dev.gentoo.org \
--cc=gentoo-releng-autobuilds@lists.gentoo.org \
--cc=releng@gentoo.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