public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: Bryan Hundven <bryanhundven@gmail.com>
To: jack <yppah56@gmail.com>
Cc: crossgcc maillist <crossgcc@sourceware.org>
Subject: Re: bug-repo
Date: Thu, 23 Jul 2020 14:00:12 -0700	[thread overview]
Message-ID: <CAJ+oik1CEGT42ZcFvJ05tR7wbk169yqeSUSA85Q6JPdTU8ymuA@mail.gmail.com> (raw)
In-Reply-To: <ae3326a6-07f9-f450-9e75-8787df24166b@gmail.com>

Please attach .config and build.log

On Thu, Jul 23, 2020 at 1:59 PM jack via crossgcc <crossgcc@sourceware.org>
wrote:

> |
> |
>
> |I do something :
> |
>
> |./ct-ng build|
>
>
>
> ||====|||====||====||====|||====|||====||====||====|||====|||====||====||====|||====|||====||====||====|
>
> |then report Error:|
> ||||
>
> |
> |
>
> |
> |
>
> ||
>
> |[INFO ]  Performing some trivial sanity checks
> [WARN ]  Number of open files 1024 may not be sufficient to build the
> toolchain; increasing to 2048
> [INFO ]  Build started 20200724.041308
> [INFO ]  Building environment variables
> [WARN ]  Directory '/home/user/src' does not exist.
> [WARN ]  Will not save downloaded tarballs to local storage.
> [EXTRA]  Preparing working directories
> [EXTRA]  Installing user-supplied crosstool-NG configuration
> [EXTRA] =================================================================
> [EXTRA]  Dumping internal crosstool-NG configuration
> [EXTRA]    Building a toolchain for:
> [EXTRA]      build  = x86_64-pc-linux-gnu
> [EXTRA]      host   = x86_64-pc-linux-gnu
> [EXTRA]      target = alphaev4-unknown-elf
> [EXTRA]  Dumping internal crosstool-NG configuration: done in 0.13s (at
> 00:02)
> [INFO ] =================================================================
> [INFO ]  Retrieving needed toolchain components' tarballs
> [EXTRA]    Retrieving 'gmp-6.2.0'
> [EXTRA]    Verifying SHA512 checksum for 'gmp-6.2.0.tar.xz'
> [EXTRA]    Retrieving 'mpfr-4.0.2'
> [EXTRA]    Verifying SHA512 checksum for 'mpfr-4.0.2.tar.xz'
> [EXTRA]    Retrieving 'isl-0.22'
> [EXTRA]    Verifying SHA512 checksum for 'isl-0.22.tar.xz'
> [EXTRA]    Retrieving 'mpc-1.1.0'
> [EXTRA]    Verifying SHA512 checksum for 'mpc-1.1.0.tar.gz'
> [EXTRA]    Retrieving 'binutils-2.34'
> [EXTRA]    Verifying SHA512 checksum for 'binutils-2.34.tar.xz'
> [EXTRA]    Retrieving 'gcc-9.2.0'
> [EXTRA]    Verifying SHA512 checksum for 'gcc-9.2.0.tar.xz'
> [EXTRA]    Retrieving 'newlib-3.3.0'
> [EXTRA]    Verifying SHA512 checksum for 'newlib-3.3.0.tar.gz'
> [INFO ]  Retrieving needed toolchain components' tarballs: done in
> 432.72s (at 07:15)
> [INFO ] =================================================================
> [INFO ]  Extracting and patching toolchain components
> [EXTRA]    Extracting gmp-6.2.0
> [EXTRA]    Patching gmp-6.2.0
> [EXTRA]    Extracting mpfr-4.0.2
> [EXTRA]    Patching mpfr-4.0.2
> [EXTRA]    Extracting isl-0.22
> [EXTRA]    Patching isl-0.22
> [EXTRA]    Extracting mpc-1.1.0
> [EXTRA]    Patching mpc-1.1.0
> [EXTRA]    Extracting binutils-2.34
> [EXTRA]    Patching binutils-2.34
> [EXTRA]    Extracting gcc-9.2.0
> [EXTRA]    Patching gcc-9.2.0
> [EXTRA]    Extracting newlib-3.3.0
> [EXTRA]    Patching newlib-3.3.0
> [INFO ]  Extracting and patching toolchain components: done in 38.62s
> (at 07:53)
> [INFO ] =================================================================
> [INFO ]  Installing GMP for host
> [EXTRA]    Configuring GMP
> [EXTRA]    Building GMP
> [EXTRA]    Installing GMP
> [INFO ]  Installing GMP for host: done in 57.80s (at 08:51)
> [INFO ] =================================================================
> [INFO ]  Installing MPFR for host
> [EXTRA]    Configuring MPFR
> [EXTRA]    Building MPFR
> [EXTRA]    Installing MPFR
> [INFO ]  Installing MPFR for host: done in 31.19s (at 09:22)
> [INFO ] =================================================================
> [INFO ]  Installing ISL for host
> [EXTRA]    Configuring ISL
> [EXTRA]    Building ISL
> [EXTRA]    Installing ISL
> [INFO ]  Installing ISL for host: done in 32.28s (at 09:55)
> [INFO ] =================================================================
> [INFO ]  Installing MPC for host
> [EXTRA]    Configuring MPC
> [EXTRA]    Building MPC
> [EXTRA]    Installing MPC
> [INFO ]  Installing MPC for host: done in 10.32s (at 10:05)
> [INFO ] =================================================================
> [INFO ]  Installing binutils for host
> [EXTRA]    Configuring binutils
> [EXTRA]    Prepare binutils for static build
> [ERROR]    make[1]: *** [configure-ld] Error 1
> [ERROR]    make[1]: *** Waiting for unfinished jobs....
> [ERROR]
> [ERROR]  >>
> [ERROR]  >>  Build failed in step 'Installing binutils for host'
> [ERROR]  >>        called in step '(top-level)'
> [ERROR]  >>
> [ERROR]  >>  Error happened in: CT_DoExecLog[scripts/functions@376]
> [ERROR]  >>        called from:
> do_binutils_backend[scripts/build/binutils/binutils.sh@205]
> [ERROR]  >>        called from:
> do_binutils_for_host[scripts/build/binutils/binutils.sh@70]
> [ERROR]  >>        called from: main[scripts/crosstool-NG.sh@695]
> [ERROR]  >>
> [ERROR]  >>  For more info on this error, look at the file: 'build.log'
> [ERROR]  >>  There is a list of known issues, some with workarounds, in:
> [ERROR]  >> https://crosstool-ng.github.io/docs/known-issues/
> [ERROR]  >>
> [ERROR]  >>  If you feel this is a bug in crosstool-NG, report it at:
> [ERROR]  >> https://github.com/crosstool-ng/crosstool-ng/issues/
> [ERROR]  >>
> [ERROR]  >>  Make sure your report includes all the information
> pertinent to this issue.
> [ERROR]  >>  Read the bug reporting guidelines here:
> [ERROR]  >>      http://crosstool-ng.github.io/support/
> [ERROR]
> [ERROR]  (elapsed: 10:39.24)
> [10:40] / ct-ng:261: recipe for target 'build' failed
> make: *** [build] Error 2
>
> |
> --
> For unsubscribe information see http://sourceware.org/lists.html#faq
>

      reply	other threads:[~2020-07-23 21:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-23 20:58 bug-repo jack
2020-07-23 21:00 ` Bryan Hundven [this message]

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=CAJ+oik1CEGT42ZcFvJ05tR7wbk169yqeSUSA85Q6JPdTU8ymuA@mail.gmail.com \
    --to=bryanhundven@gmail.com \
    --cc=crossgcc@sourceware.org \
    --cc=yppah56@gmail.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).