This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/85142] Wrong -print-multi-os-directory & -print-multi-lib output for riscv64 + multilib
- From: "wilson at tuliptree dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Tue, 03 Apr 2018 02:43:11 +0000
- Subject: [Bug target/85142] Wrong -print-multi-os-directory & -print-multi-lib output for riscv64 + multilib
- Auto-submitted: auto-generated
- References: <bug-85142-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85142
--- Comment #9 from Jim Wilson <wilson at tuliptree dot org> ---
On Mon, 2018-04-02 at 23:50 +0000, joseph at codesourcery dot com
wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85142
>
> --- Comment #8 from joseph at codesourcery dot com <joseph at
> codesourcery dot com> ---
> "." is correct for the default multilib in the non-OS directory
> arrangements, just not in the OS directory arrangements.
This is obvious. I don't understand why you are repeating the obvious.
But "." is what we get from --print-multi-os-dirnames which looks wrong
which is why I'm looking into this further.
Looking at this a bit more, I noticed that if I use --print-search-
dirs, then the paths appear to be correct. It searches
$sysroot/lib64/lp64d first, and then $sysroot/usr/lib64/lp64d. It is
only the --print-multi-* options that are printing output that looks
wrong for the default case.
I also noticed that I forgot a comma in my earlier MULTILIB_DEFAULTS
suggestion.
Anyways, I'm looking at the problem. You don't need to do anything. I
don't need any help. Just wait until I have more info about what is
going on here.
Jim