public inbox for libabigail@sourceware.org
 help / color / mirror / Atom feed
From: "michi.henning at canonical dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/19705] Can't build from HEAD without change
Date: Fri, 01 Jan 2016 00:00:00 -0000	[thread overview]
Message-ID: <bug-19705-9487-io8ouqAtmc@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-19705-9487@http.sourceware.org/bugzilla/>

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

--- Comment #2 from Michi Henning <michi.henning at canonical dot com> ---
(In reply to dodji from comment #1)
> Thank you for taking the time to file this problem report.
>  
> > elfutils, libtool, libelf-dev, libdw-dev
> > 
> > It might be nice to mention these in the doc.
> 
> Right.  I guess you mean the COMPILING file in the source tree.  elfutils at
> least is mentioned at https://www.sourceware.org/libabigail/#compile.

No, I was looking at the instructions here:

https://www.sourceware.org/libabigail/

> As for libelf-dev and libdw-dev, they should be part of the development
> variant of elfutils, shouldn't they?  On my system, for instance, trying to
> install elfutils-devel will install the packages necessary for the libraries
> (and header files) of libelf and libdw.  Those two components are parts of
> the elfutils project anyway.

It looks like, on Ubuntu, libelf-dev doesn't drag in libdw-dev. Instead,
libdw-dev requires libelf-dev. When I tried to resolve the package
dependencies, I installed libelf-dev first and then found that I need to
install libdw-dev too.

> I am asking this just so that I can in the docs to install the development
> variants of the 'elfutils' package, without having to go into the specifics
> of how each distro splits up its things.

Yes, the different packaging for distros is a headache. It's not a big deal--I
mean, it wasn't exactly rocket science to figure out the missing dependencies
:-)

> Weird, obviously, I don't get this on my system.

I just followed the instructions on the home page and figured it would be best
to report this. There is nothing unusual in my Ubuntu installation as far as
compiler, linker, or library locations are concerned. It's all stock-standard.

> > +AM_LDFLAGS = -pthread
> 
> This hunk makes all test binaries link with pthread, even those that don't
> need it directly.  I'd rather have the tests that need pthreads *directly*
> to link with it, and only those.

Sure. I wasn't trying to provide a real fix here because I was more interested
in just getting things to compile so I could tinker with rc3. Having libabigail
link with pthreads sounds like a cleaner solution, yes.

> I have the same comment for the tools.  the only program using pthreads
> directly in the tools is abipkgdiff.  Thus, no other tool should link with
> pthreads.

Yes. I found that none of the tools linked, so I just threw -pthread in as a
global flag so I could move on.

> > -abinilint_LDFLAGS = $(abs_top_builddir)/src/libabigail.la
> > +abinilint_LDADD = $(abs_top_builddir)/src/libabigail.la
> 
> Ah, this one is a real typo.  Thanks for spotting that!

NP!

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

      parent reply	other threads:[~2016-02-24 22:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-01  0:00 [Bug default/19705] New: " michi.henning at canonical dot com
2016-01-01  0:00 ` [Bug default/19705] " dodji at redhat dot com
2016-01-01  0:00 ` michi.henning at canonical dot com [this message]

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-19705-9487-io8ouqAtmc@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).