From: Alan Modra <amodra@gmail.com>
To: Vladimir Mezentsev <vladimir.mezentsev@oracle.com>
Cc: "Andreas K. Hüttel" <dilfridge@gentoo.org>,
binutils@sourceware.org, toolchain@gentoo.org
Subject: Re: [PATCH, needs more eyes] Relink also libopcodes and libgprofng to newly built libiberty.a
Date: Thu, 2 Mar 2023 19:57:48 +1030 [thread overview]
Message-ID: <ZABsFAX/92vIc82K@squeak.grove.modra.org> (raw)
In-Reply-To: <c6748f0f-bd8a-5594-24d0-a25135e38cd5@oracle.com>
On Thu, Mar 02, 2023 at 12:10:52AM -0800, Vladimir Mezentsev wrote:
>
>
> On 3/1/23 21:11, Alan Modra wrote:
> > On Wed, Mar 01, 2023 at 02:17:54PM -0800, Vladimir Mezentsev via Binutils wrote:
> > > I think libtool added -L/usr/lib because gprofng and libsframe are linked
> > > with bfd/libbfd.la and
> > > libbfd.la has a wrong dependency:
> > >
> > > % grep L/usr/lib bfd/libbfd.la
> > > dependency_libs=' -lz -L/usr/lib -lzstd
> > > /dev/shm/bld-binutils-gdb/libsframe/libsframe.la -ldl'
> > Hmm, I used exactly the same configure line as you did, and I don't
> > see any -L in libbfd.la dependency_libs. Built on x86_64-linux-gnu
> > running Ubuntu 22.04.
>
> I build on OL8.
>
> grep dependency_libs in <your_build_area>/bfd/libbfd.la.
> It is a problem in my build.
>
> > $ find /usr/lib -name libzstd\*
>
> Why do you try to find it ?
> I wrote about build area.
To show you that I had both .a and .so for -lzstd. I'm assuming that
since -L/usr/lib comes before -lzstd in your dependency_libs that it
might be something to do with libzstd.
> > /usr/lib/i386-linux-gnu/libzstd.so.1
> > /usr/lib/i386-linux-gnu/libzstd.so.1.4.8
> > /usr/lib/x86_64-linux-gnu/libzstd.so
> > /usr/lib/x86_64-linux-gnu/libzstd.so.1
> > /usr/lib/x86_64-linux-gnu/libzstd.a
> > /usr/lib/x86_64-linux-gnu/pkgconfig/libzstd.pc
> > /usr/lib/x86_64-linux-gnu/libzstd.so.1.4.8
> >
--
Alan Modra
Australia Development Lab, IBM
next prev parent reply other threads:[~2023-03-02 9:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-28 22:49 Andreas K. Hüttel
2023-03-01 8:29 ` Jan Beulich
2023-03-01 22:17 ` Vladimir Mezentsev
2023-03-02 5:11 ` Alan Modra
2023-03-02 8:10 ` Vladimir Mezentsev
2023-03-02 9:27 ` Alan Modra [this message]
2023-03-15 20:51 ` Andreas K. Huettel
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=ZABsFAX/92vIc82K@squeak.grove.modra.org \
--to=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=dilfridge@gentoo.org \
--cc=toolchain@gentoo.org \
--cc=vladimir.mezentsev@oracle.com \
/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).