public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "paul.hua.gm at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/98616] Compile gcc 10.2.0 error for loongson 2f CPU use MIPS n32 ABI on Gentoo OS
Date: Mon, 25 Jan 2021 03:50:51 +0000	[thread overview]
Message-ID: <bug-98616-4-j6DJQDe7Tl@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98616-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98616

Paul Hua <paul.hua.gm at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |paul.hua.gm at gmail dot com

--- Comment #2 from Paul Hua <paul.hua.gm at gmail dot com> ---
Hi,

The error message show:

---------------------------------------------------------------------
 configure: error: in
`/var/tmp/portage/sys-devel/gcc-10.2.0-r5/work/build/mips64el-unknown-linux-gnu/libgcc':
configure: error: cannot compute suffix of object files: cannot compile
See `config.log' for more details
make[2]: *** [Makefile:16845: configure-stage1-target-libgcc] Error 1
-----------------------------------------------------------------------

please see config.log for more details.

  parent reply	other threads:[~2021-01-25  3:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-10 14:50 [Bug bootstrap/98616] New: " tong__hui at 163 dot com
2021-01-10 14:56 ` [Bug bootstrap/98616] " tong__hui at 163 dot com
2021-01-25  3:50 ` paul.hua.gm at gmail dot com [this message]
2021-01-25 16:08 ` mikpelinux at gmail dot com
2021-07-24 20:27 ` pinskia at gcc dot gnu.org
2021-07-28 11:58 ` tong__hui at 163 dot com
2021-07-28 12:32 ` schwab@linux-m68k.org

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=bug-98616-4-j6DJQDe7Tl@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).