public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "doko at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/108339] New: riscv64-linux-gnu: fails to link libgcc_s.so on the GCC 10 branch
Date: Mon, 09 Jan 2023 09:33:11 +0000 [thread overview]
Message-ID: <bug-108339-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108339
Bug ID: 108339
Summary: riscv64-linux-gnu: fails to link libgcc_s.so on the
GCC 10 branch
Product: gcc
Version: 10.4.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: doko at gcc dot gnu.org
Target Milestone: ---
the gcc-10 branch fails to build on riscv64-linux-gnu with the binutils-2.40
branch, trying to build a cross compiler, building libgcc_s.so:
/usr/riscv64-linux-gnu/bin/ld: relocation R_RISCV_JAL against `__udivdi3' which
may bind externally
can not be used when making a shared object; recompile with -fPIC
collect2: error: ld returned 1 exit status
make[5]: *** [Makefile:994: libgcc_s.so] Error 1
make[5]: Leaving directory
'/<<PKGBUILDDIR>>/gcc/build/riscv64-linux-gnu/libgcc'
all newer branches and the trunk successfully build with this binutils
versions, so assuming that some backport is needed for the gcc-10 branch to
work with recent binutils?
next reply other threads:[~2023-01-09 9:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-09 9:33 doko at gcc dot gnu.org [this message]
2023-01-09 10:08 ` [Bug target/108339] " marxin at gcc dot gnu.org
2023-01-09 16:49 ` [Bug target/108339] [10 only] " pinskia at gcc dot gnu.org
2023-01-09 16:51 ` pinskia at gcc dot gnu.org
2023-01-09 16:52 ` [Bug target/108339] [11/10 " pinskia at gcc dot gnu.org
2023-01-10 4:56 ` doko at gcc dot gnu.org
2023-02-20 11:03 ` cvs-commit at gcc dot gnu.org
2023-02-20 11:05 ` kito at gcc dot gnu.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-108339-4@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).