bug-binutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug ld/22962] [RISCV] add abi subdirectories support to ld


From: wilson at gcc dot gnu.org
Subject: [Bug ld/22962] [RISCV] add abi subdirectories support to ld
Date: Thu, 15 Mar 2018 22:10:59 +0000

https://sourceware.org/bugzilla/show_bug.cgi?id=22962

--- Comment #11 from Jim Wilson <wilson at gcc dot gnu.org> ---
(In reply to address@hidden from comment #10)
> Again, the quoted error is about a search that uses -rpath-link paths but 
> *not* -L paths.  GCC uses the right -L paths automatically, but 
> LIBPATH_SUFFIX settings in binutils are needed to get the right 
> -rpath-link paths used automatically.

Yes, I saw your message.  I hadn't missed it or forgotten about it.  I just
hadn't had time to respond to it yet, as it arrived too late in the day for me
to do anything with it.  Also, after missing a few days due to illness and a
home move, I have a large backlog of stuff to work on, and haven't gotten back
to this issue yet.

Meanwhile, I've been trying to summarize details that I had already found out
along the way, and details that have been discussed in other places that aren't
archived.

I'm also trying to understand why neither Fedora nor OpenSuse have run into
this problem.  Assuming it is glibc specific, then that explains why FreeBSD,
RTEMS, FreeRTOS, Zephyr, etc haven't hit the problem, as they likely aren't
using glibc and/or aren't using the same library scheme.  I know that there is
also a Debian port somewhere.  I'm not sure how far along they are, but they
apparently haven't hit this problem either.  So why has Serge hit it?

I'm also trying to understand the problem as best as I can before making any
change, as I want to avoid breaking any of the existing systems which are all
working with the current linker support.  That includes systems using the
upstream glibc and systems using the pre-upstream glibc, which may be using
different library directory conventions.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]