From: IPFire Nightly Builder <nightly-builds@ipfire.org>
To: nightly-builds@lists.ipfire.org
Subject: [FAILED] Nightly Build of next (25f14fa) for armv5tel on arm64-02.dub.ipfire.org
Date: Fri, 25 Sep 2020 09:00:54 +0000 [thread overview]
Message-ID: <4ByQqp1MjLz5ysy@arm64-02.dub.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 3103 bytes --]
https://nightly.ipfire.org/next/2020-09-25%2008%3A41%3A46%20%2B0000-25f14fa0/armv5tel
commit 25f14fa0d547349b68d62aa18a64f90e0145d8ec
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Fri Sep 25 08:41:46 2020 +0000
netsnmpd: Disable parallel build
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
https://git.ipfire.org/?p=ipfire-2.x.git;a=shortlog;h=25f14fa0d547349b68d62aa18a64f90e0145d8ec
Full toolchain compilation
Checking for necessary space on disk [ DONE ]
stage1 [ 0 ][ DONE ]
ccache (3.4.1) PASS=1 [ 3 ][ DONE ]
binutils (2.34) PASS=1 [ 17 ][ FAIL ]
gcc -O2 -pipe -Wall -fexceptions -fPIC -fomit-frame-pointer -o sysinfo sysinfo.o syslex_wrap.o
WARNING: 'makeinfo' is missing on your system.
You should only need it if you modified a '.texi' file, or
any other file indirectly affecting the aspect of the manual.
You might want to install the Texinfo package:
<http://www.gnu.org/software/texinfo/>
The spurious makeinfo call might also be the consequence of
using a buggy 'make' (AIX, DU, IRIX), in which case you might
want to install GNU make:
<http://www.gnu.org/software/make/>
(pod2man --center="GNU Development Tools" --release="binutils-2.34" --section=1 addr2line.pod | sed -e '/^.if n .na/d' > addr2line.1.T$$ && \
mv -f addr2line.1.T$$ addr2line.1) || (rm -f addr2line.1.T$$ && exit 1)
make[4]: *** [Makefile:474: binutils.info] Error 127
make[4]: *** Waiting for unfinished jobs....
(pod2man --center="GNU Development Tools" --release="binutils-2.34" --section=1 ar.pod | sed -e '/^.if n .na/d' > ar.1.T$$ && \
mv -f ar.1.T$$ ar.1) || (rm -f ar.1.T$$ && exit 1)
(pod2man --center="GNU Development Tools" --release="binutils-2.34" --section=1 dlltool.pod | sed -e '/^.if n .na/d' > dlltool.1.T$$ && \
mv -f dlltool.1.T$$ dlltool.1) || (rm -f dlltool.1.T$$ && exit 1)
./sysinfo -d </build/nightly/next/build/usr/src/binutils-2.34/binutils/sysroff.info >sysroff.h
rm -f addr2line.pod
rm -f ar.pod
rm -f dlltool.pod
make[4]: Leaving directory '/build/nightly/next/build/usr/src/binutils-build/binutils/doc'
make[3]: *** [Makefile:1134: info-recursive] Error 1
make[3]: Leaving directory '/build/nightly/next/build/usr/src/binutils-build/binutils'
make[2]: *** [Makefile:3632: all-binutils] Error 2
make[2]: Leaving directory '/build/nightly/next/build/usr/src/binutils-build'
make[1]: *** [Makefile:853: all] Error 2
make[1]: Leaving directory '/build/nightly/next/build/usr/src/binutils-build'
make: *** [binutils:133: /build/nightly/next/log/binutils-2.34-tools1] Error 2
ERROR: Building binutils PASS=1 [ FAIL ]
Check /build/nightly/next/log/_build.toolchain.log for errors if applicable[ FAIL ]
reply other threads:[~2020-09-25 9:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4ByQqp1MjLz5ysy@arm64-02.dub.ipfire.org \
--to=nightly-builds@ipfire.org \
--cc=nightly-builds@lists.ipfire.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