public inbox for nightly-builds@lists.ipfire.org
 help / color / mirror / Atom feed
From: IPFire Nightly Builder <nightly-builds@ipfire.org>
To: nightly-builds@lists.ipfire.org
Subject: [FAILED] Nightly Build of next (815ca15) for aarch64 on arm64-01.dub.ipfire.org
Date: Mon, 17 Aug 2020 10:03:41 +0000	[thread overview]
Message-ID: <4BVV4G075Rz1yMh@arm64-01.dub.ipfire.org> (raw)

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

https://nightly.ipfire.org/next/2020-08-16%2010%3A29%3A43%20%2B0000-815ca15d/aarch64

commit 815ca15dc4e7e3d20a5fd7006395c9b1664bb04c
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date:   Sun Aug 16 10:28:09 2020 +0000

    make.sh: Increase maximum size of ramdisk to 8GB
    
    The previous 4GB were not enough for a full GCC bootstrap
    in the toolchain stage.
    
    Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>

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

Packaged toolchain compilation                                          
Checking for necessary space on disk                                    [ DONE ]
Building LFS                                                            
stage2                                                      [        0 ][ DONE ]
linux (4.14.184)                              KCFG=-headers [       12 ][ DONE ]
man-pages (2.34)                                            [        4 ][ DONE ]
glibc (2.32)                                                [     2:43 ][ FAIL ]

    304 |   SET_RESTORE_ROUND_GENERIC (RM, libc_feholdsetroundl, libc_feresetroundl)
    |   ^~~~~~~~~~~~~~~~~~~~~~~~~
    ../sysdeps/ieee754/ldbl-128/e_j1l.c:871:7: note: in expansion of macro 'SET_RESTORE_ROUNDL'
    871 |       SET_RESTORE_ROUNDL (FE_TONEAREST);
    |       ^~~~~~~~~~~~~~~~~~
    In file included from ../include/fpu_control.h:2,
    from ../sysdeps/aarch64/fpu/fenv_private.h:23,
    from ../sysdeps/ieee754/ldbl-128/e_j1l.c:101:
    ../sysdeps/aarch64/fpu/fpu_control.h:28:27: error: 'ctx.env.__fpcr' may be used uninitialized in this function [-Werror=maybe-uninitialized]
    28 | # define _FPU_SETCW(fpcr) __builtin_aarch64_set_fpcr (fpcr)
    |                           ^~~~~~~~~~~~~~~~~~~~~~~~~~
    In file included from ../sysdeps/aarch64/fpu/fenv_private.h:301,
    from ../sysdeps/ieee754/ldbl-128/e_j1l.c:101:
    ../sysdeps/generic/fenv_private.h:291:17: note: 'ctx.env.__fpcr' was declared here
    291 |   struct rm_ctx ctx __attribute__((cleanup (CLEANUPFUNC ## _ctx))); \
    |                 ^~~
    ../sysdeps/generic/fenv_private.h:304:3: note: in expansion of macro 'SET_RESTORE_ROUND_GENERIC'
    304 |   SET_RESTORE_ROUND_GENERIC (RM, libc_feholdsetroundl, libc_feresetroundl)
    |   ^~~~~~~~~~~~~~~~~~~~~~~~~
    ../sysdeps/ieee754/ldbl-128/e_j1l.c:871:7: note: in expansion of macro 'SET_RESTORE_ROUNDL'
    871 |       SET_RESTORE_ROUNDL (FE_TONEAREST);
    |       ^~~~~~~~~~~~~~~~~~
    cc1: all warnings being treated as errors
    make[3]: *** [/usr/src/glibc-build/sysd-rules:553: /usr/src/glibc-build/math/e_j1l.o] Error 1
    make[3]: Leaving directory '/usr/src/glibc-2.32/math'
    make[2]: *** [Makefile:470: math/others] Error 2
    make[2]: Leaving directory '/usr/src/glibc-2.32'
    make[1]: *** [Makefile:9: all] Error 2
    make[1]: Leaving directory '/usr/src/glibc-build'
    make: *** [glibc:113: /usr/src/log/glibc-2.32] Error 2

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

                 reply	other threads:[~2020-08-17 10:03 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=4BVV4G075Rz1yMh@arm64-01.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