From: "dodji at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/30034] [libabigail] Handle library splitting
Date: Fri, 09 Jun 2023 12:29:38 +0000 [thread overview]
Message-ID: <bug-30034-9487-zg4MOCsH2z@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30034-9487@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30034
--- Comment #10 from dodji at redhat dot com ---
> > So, are you sure that librte_eal.so has ALL the split libraries
> > (resulting from splitting the former big library into smaller ones) as
> > dependencies? I mean, this really looks like a particular case of the
> > general problem of being able to compare sets of ABI corpora. Sure, I
> > understand how this particular use case is worth supporting (and I agree
> > we should support it), but in the grand scheme of things, I am wondering
> > if supporting /just/ this particular case makes sense.
>
> If EAL does not have all dependencies listed, that would break ABI for
> applications that are linked against and only knows of this library.
OK, so that is the way you have designed the splitting. Making a front library
(i.e, EAL) have all the others (resulting from the the split) as dependencies,
I just wanted to be sure. Thank you for confirming. So I am adding this use
case to the initial, generic & straightforward one. Thank you.
So, after reading your comments and talking privately with you, David, I have
updated the specification in the branch users/dodji/PR30034 at
https://sourceware.org/git/?p=libabigail.git;a=shortlog;h=refs/heads/users/dodji/PR30034.
You can navigate the changes by looking at the 3 individual commits that come
on top of the level of the master branch, or you can just look at the resulting
specification file which is still:
https://sourceware.org/git/?p=libabigail.git;a=blob;f=README-ABIDIFF-BINARIES-SET-SUPPORT.md;hb=refs/heads/users/dodji/PR30034
Please do let me know if I am still off by a lot here :-)
Thanks.
I
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-06-09 12:29 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-23 13:45 [Bug default/30034] New: " david.marchand at redhat dot com
2023-06-02 17:53 ` [Bug default/30034] " dodji at redhat dot com
2023-06-05 8:04 ` david.marchand at redhat dot com
2023-06-05 11:01 ` dodji at redhat dot com
2023-06-05 15:08 ` david.marchand at redhat dot com
2023-06-05 15:24 ` woodard at redhat dot com
2023-06-05 15:36 ` dodji at redhat dot com
2023-06-05 16:53 ` woodard at redhat dot com
2023-06-06 7:28 ` david.marchand at redhat dot com
2023-06-06 21:07 ` woodard at redhat dot com
2023-06-09 12:29 ` dodji at redhat dot com [this message]
2023-06-14 12:22 ` david.marchand at redhat dot com
2023-06-23 8:30 ` david.marchand at redhat dot com
2023-06-23 8:32 ` david.marchand at redhat dot com
2023-06-23 10:17 ` david.marchand at redhat dot com
2023-06-24 14:19 ` dodji at redhat dot com
2023-06-24 14:32 ` dodji at redhat dot com
2023-06-25 8:17 ` david.marchand at redhat dot com
2023-06-25 8:37 ` david.marchand at redhat dot com
2023-06-26 10:07 ` dodji at redhat dot com
2023-06-26 10:11 ` dodji at redhat dot com
2023-06-26 12:13 ` david.marchand at redhat dot com
2023-06-26 12:41 ` david.marchand at redhat dot com
2023-06-26 13:57 ` dodji at redhat dot com
2023-07-06 13:38 ` david.marchand at redhat dot com
2023-07-07 8:38 ` Dodji Seketeli
2023-07-07 8:39 ` dodji at seketeli dot org
2023-07-07 11:48 ` dodji at redhat dot com
2023-07-07 13:55 ` fweimer at redhat dot com
2023-07-07 18:18 ` dodji at redhat dot com
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-30034-9487-zg4MOCsH2z@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=libabigail@sourceware.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).