public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/104707] gcc on riscv64 isn't passing entire library path to the linker
Date: Tue, 19 Apr 2022 11:00:42 +0000 [thread overview]
Message-ID: <bug-104707-4-WbSlD9tiLB@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104707-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104707
--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Jan Palus from comment #3)
> I doubt this has anything to do with riscv or multilib. It's just gcc that
> assumes all linkers should lookup /lib and /usr/lib and skips them when
> passing library paths to linker:
>
> https://gcc.gnu.org/git/?p=gcc.git;a=blob;f=gcc/gcc.cc;
> h=bb07cc244e30fbeccc701816db888f497d65eb08;hb=refs/heads/master#l7931
>
> I had the same issue on arm (32-bit) so no riscv, no multilib and dropping
> this logic fixes the issue.
Arm linux multilib is just as complex as riscvs really.
next prev parent reply other threads:[~2022-04-19 11:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-27 5:34 [Bug target/104707] New: " sterprim at outlook dot com
2022-02-27 5:41 ` [Bug target/104707] " pinskia at gcc dot gnu.org
2022-02-27 8:17 ` pinskia at gcc dot gnu.org
2022-04-19 10:33 ` jpalus+gcc at fastmail dot com
2022-04-19 11:00 ` pinskia at gcc dot gnu.org [this message]
2022-04-19 11:36 ` jpalus+gcc at fastmail dot com
2023-04-03 6:32 ` [Bug other/104707] GCC doesn't give default lib path to the linker when multilib is off sterprim at outlook dot com
2023-04-03 6:36 ` pinskia at gcc dot gnu.org
2023-04-03 6:58 ` [Bug driver/104707] " i at rvalue dot moe
2023-04-03 7:01 ` pinskia at gcc dot gnu.org
2024-04-10 11:13 ` pinskia at gcc dot gnu.org
2024-04-16 19:06 ` pinskia 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-104707-4-WbSlD9tiLB@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).