public inbox for libabigail@sourceware.org
 help / color / mirror / Atom feed
From: "dodji at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/30034] [libabigail] Handle library splitting
Date: Mon, 26 Jun 2023 10:07:33 +0000	[thread overview]
Message-ID: <bug-30034-9487-q7XJ3AbRE7@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 #18 from dodji at redhat dot com ---
(In reply to David Marchand from comment #16)
> (In reply to dodji from comment #15)
> > I will let you test and play with the tree while I spit & polish it in the
> > background.  Please do not hesitate to provide me with the feedback you see
> > fit.
> > 
> 
> Well, for now, I hit a compilation issue on fedora37 :
> 
> ...
> =====================================================================
> 	Libabigail: 2.4.0
> =====================================================================
> 
> 		Here is the configuration of the package:
> 
>     Prefix                                         : /usr/local
>     Source code location                           : ..
>     C Compiler                                     : gcc
>     C++ Compiler		                   : g++
>     GCC visibility attribute supported             : yes
>     CXXFLAGS	   	     			   : -g -O2 -std=c++11
>     Python					   : python3
> 
>  OPTIONAL FEATURES:
>     C++ standard level                             : c++11
>     libdw has the dwarf_getalt function            : yes
>     Enable rpm support in abipkgdiff               : yes
>     Enable rpm/zstd in abipkgdiff testing          : yes
>     Enable abilint --show-type-use <type-id>       : no
>     Enable self comparison debugging               : no
>     Enable type canonicalization debugging         : no
>     Enable propagated canonical type debugging	   : no
>     Enable deb support in abipkgdiff               : no
>     Enable GNU tar archive support in abipkgdiff   : yes
>     Enable bash completion	                   : no
>     Enable fedabipkgdiff                           : no
>     Enable python 3				   : yes
>     Enable CTF front-end                           : yes
>     Enable BTF front-end                           : yes
>     Enable running tests under Valgrind            : yes
>     Enable build with -fsanitize=address    	   : no
>     Enable build with -fsanitize=memory    	   : no
>     Enable build with -fsanitize=thread    	   : no
>     Enable build with -fsanitize=undefined  	   : no
>     Generate html apidoc	                   : yes
>     Generate html manual	                   : yes
> ...
> 
> 
> ../../src/abg-ctf-reader.cc: In member function 'virtual void
> abigail::ctf::reader::initialize(const std::string&, const
> std::vector<char**>&, bool, bool)':
> ../../src/abg-ctf-reader.cc:291:5: error: 'reset' was not declared in this
> scope
>   291 |     reset(elf_path, debug_info_root_paths);
>       |     ^~~~~

Oh, sorry about that.  I have fixed the error and updated the branch.  You
shouldn't get this anymore.

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

  parent reply	other threads:[~2023-06-26 10:07 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
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 [this message]
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-q7XJ3AbRE7@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).