[FAILED] Nightly Build of next (44bfc40) for aarch64 on arm64-01.dub.ipfire.org

[FAILED] Nightly Build of next (44bfc40) for aarch64 on arm64-01.dub.ipfire.org

[IPFire Nightly Builder]

[-- Attachment #1: Type: text/plain, Size: 3536 bytes --]

https://nightly.ipfire.org/next/2020-08-17%2010%3A05%3A40%20%2B0000-44bfc406/aarch64

commit 44bfc406407fcba783b532ce5e5bcd91092e08d0
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date:   Mon Aug 17 10:05:40 2020 +0000

    glibc: aarch64: Ignore uninitialised variables in the stage2 build, too
    
    Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>

https://git.ipfire.org/?p=ipfire-2.x.git;a=shortlog;h=44bfc406407fcba783b532ce5e5bcd91092e08d0

Packaged toolchain compilation                                          
Checking for necessary space on disk                                    [ DONE ]
Building LFS                                                            
stage2                                                      [        0 ][ DONE ]
linux (4.14.184)                              KCFG=-headers [       11 ][ DONE ]
man-pages (2.34)                                            [        5 ][ DONE ]
glibc (2.32)                                                [     7:25 ][ DONE ]
tzdata (2019c)                                              [        2 ][ DONE ]
cleanup-toolchain                                           [        0 ][ DONE ]
zlib (1.2.11)                                               [        2 ][ DONE ]
binutils (2.34)                                             [     1:15 ][ DONE ]
gmp (6.2.0)                                                 [       46 ][ DONE ]
gmp-compat (4.3.2)                                          [       45 ][ DONE ]
mpfr (4.1.0)                                                [       26 ][ DONE ]
libmpc (1.1.0)                                              [        7 ][ DONE ]
file (5.38)                                                 [        8 ][ DONE ]
gcc (10.2.0)                                                [    30:07 ][ FAIL ]

    
    If you ever happen to want to link against installed libraries
    in a given directory, LIBDIR, you must either use libtool, and
    specify the full pathname of the library, or use the `-LLIBDIR'
    flag during linking and do at least one of the following:
    - add LIBDIR to the `LD_LIBRARY_PATH' environment variable
    during execution
    - add LIBDIR to the `LD_RUN_PATH' environment variable
    during linking
    - use the `-Wl,-rpath -Wl,LIBDIR' linker flag
    - have your system administrator add LIBDIR to `/etc/ld.so.conf'
    
    See any operating system documentation about shared libraries for
    more information, such as the ld(1) and ld.so(8) manual pages.
    ----------------------------------------------------------------------
    make[5]: Nothing to be done for 'install-data-am'.
    make[5]: Leaving directory '/usr/src/gcc-build/aarch64-unknown-linux-gnu/libatomic'
    make[4]: Leaving directory '/usr/src/gcc-build/aarch64-unknown-linux-gnu/libatomic'
    make[3]: Leaving directory '/usr/src/gcc-build/aarch64-unknown-linux-gnu/libatomic'
    make[2]: Leaving directory '/usr/src/gcc-build'
    make[1]: Leaving directory '/usr/src/gcc-build'
    ln -svf ../usr/bin/cpp /lib
    '/lib/cpp' -> '../usr/bin/cpp'
    ln -svf gcc /usr/bin/cc
    '/usr/bin/cc' -> 'gcc'
    # remove gdb python files from libdir
    rm -rf /usr/lib/*-gdb.py
    Updating linker cache...
    Install done; saving file list to /usr/src/log/gcc-10.2.0 ...

ERROR: Building gcc                                                     [ FAIL ]
    Check /build/nightly/next/log/_build.base.log for errors if applicable[ FAIL ]