From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Mark Wielaard <mark@klomp.org>
Cc: peterz@infradead.org, Hugh Dickins <hughd@google.com>,
linux-kernel@vger.kernel.org, x86@kernel.org
Subject: Re: Static call dependency on libelf version?
Date: Tue, 15 Sep 2020 10:02:29 -0500 [thread overview]
Message-ID: <20200915150229.75ilnm32a5fnjbja@treble> (raw)
In-Reply-To: <38388294c6ad7bf4abdb1b9a0bac9af5224c8fa6.camel@klomp.org>
On Tue, Sep 15, 2020 at 04:38:02PM +0200, Mark Wielaard wrote:
> Hi Josh,
>
> On Tue, 2020-09-15 at 09:17 -0500, Josh Poimboeuf wrote:
> > On Tue, Sep 15, 2020 at 01:24:17PM +0200, Mark Wielaard wrote:
> > > But all this is for ancient versions of elfutils libelf. So it is hard
> > > to say and my memory might be failing. If someone can confirm 0.158
> > > (which is 6 years old) works fine I would pick that as minimum version,
> > > otherwise simply go with 0.168 which is 4 years old and should be on
> > > most systems by now.
> >
> > I just discovered elf_version(), I assume that would allow us to check
> > and enforce the libelf version?
>
> No, sorry. That is for the ELF file format version, which is and has
> always been version 1 (and I suspect it will be for the next 20
> years).
Oh, right :-)
> There is /usr/include/elfutils/version.h which provides a
> _ELFUTILS_PREREQ(major, minor) macro if you need something during
> compile time.
Nice, I'll try that.
> Note that in theory libelf is a generic library (there are variants for
> Solaris and BSD with which we try to be [source] compatible), but the
> only actively maintained version is the elfutils one.
Yeah, we've occasionally had users using another variant of the library
which is 10+ years old. Not surprisingly it didn't work well.
--
Josh
next prev parent reply other threads:[~2020-09-15 23:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-15 7:50 Hugh Dickins
2020-09-15 9:30 ` peterz
2020-09-15 11:24 ` Mark Wielaard
2020-09-15 14:17 ` Josh Poimboeuf
2020-09-15 14:38 ` Mark Wielaard
2020-09-15 15:02 ` Josh Poimboeuf [this message]
2020-09-15 21:47 ` Josh Poimboeuf
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=20200915150229.75ilnm32a5fnjbja@treble \
--to=jpoimboe@redhat.com \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@klomp.org \
--cc=peterz@infradead.org \
--cc=x86@kernel.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
all inboxes | Powered by JetHome®