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 (d1e20e8) for aarch64 on arm64-01.dub.ipfire.org
Date: Sat, 09 May 2020 20:36:11 +0000	[thread overview]
Message-ID: <49KJrC4pZ0z1yf7@arm64-01.dub.ipfire.org> (raw)

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

https://nightly.ipfire.org/next/2020-05-09%2019%3A27%3A02%20%2B0000-d1e20e8c/aarch64

commit d1e20e8ca7cab5586c328ebf677d1864294d49e8
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date:   Sat May 9 19:27:02 2020 +0000

    core145: fix firewall rules.pl path
    
    Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>

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

Packaged toolchain compilation                                          
Checking for necessary space on disk                                    [ DONE ]
Building LFS                                                            
stage2                                                      [        1 ][ DONE ]
linux (4.14.173)                              KCFG=-headers [       20 ][ DONE ]
man-pages (2.34)                                            [        8 ][ DONE ]
glibc (2.31)                                                [    12:10 ][ DONE ]
tzdata (2019c)                                              [        3 ][ DONE ]
cleanup-toolchain                                           [        0 ][ DONE ]
zlib (1.2.11)                                               [        1 ][ DONE ]
binutils (2.34)                                             [       51 ][ DONE ]
gmp (6.1.2)                                                 [       39 ][ DONE ]
gmp-compat (4.3.2)                                          [       45 ][ DONE ]
mpfr (4.0.2)                                                [       19 ][ DONE ]
libmpc (1.1.0)                                              [        7 ][ DONE ]
file (5.38)                                                 [       10 ][ DONE ]
gcc (9.3.0)                                                 [    17:44 ][ DONE ]
sed (4.4)                                                   [       22 ][ DONE ]
autoconf (2.69)                                             [        3 ][ DONE ]
automake (1.16.2)                                           [        4 ][ DONE ]
berkeley (5.3.28)                                           [     1:27 ][ DONE ]
berkeley-compat (4.4.20)                                    [        1 ][ FAIL ]

    http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/config/config/config.sub
    
    If the version you run (../dist/config.guess) is already up to date, please
    send the following data and any information you think might be
    pertinent to <config-patches(a)gnu.org> in order to provide the needed
    information to handle your system.
    
    config.guess timestamp = 2005-09-19
    
    uname -m = aarch64
    uname -r = 4.14.173-ipfire
    uname -s = Linux
    uname -v = #1 SMP Debian 4.19.98-1 (2020-01-26)
    
    /usr/bin/uname -p =
    /bin/uname -X     =
    
    hostinfo               =
    /bin/universe          =
    /usr/bin/arch -k       =
    /bin/arch              =
    /usr/bin/oslevel       =
    /usr/convex/getsysinfo =
    
    UNAME_MACHINE = aarch64
    UNAME_RELEASE = 4.14.173-ipfire
    UNAME_SYSTEM  = Linux
    UNAME_VERSION = #1 SMP Debian 4.19.98-1 (2020-01-26)
    configure: error: cannot guess build type; you must specify one
    make: *** [berkeley-compat:74: /usr/src/log/db-4.4.20] Error 1

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

                 reply	other threads:[~2020-05-09 20:36 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=49KJrC4pZ0z1yf7@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