From: Mark Wielaard <mjw@redhat.com>
To: Ulf Hermann <ulf.hermann@qt.io>
Cc: elfutils-devel@sourceware.org
Subject: Re: [PATCH] Check for existence of mempcpy
Date: Fri, 17 Feb 2017 10:26:00 -0000 [thread overview]
Message-ID: <1487327166.10240.35.camel@redhat.com> (raw)
In-Reply-To: <251603a0-9ee9-5387-7eac-c1636dfe9f61@qt.io>
On Fri, 2017-02-17 at 10:50 +0100, Ulf Hermann wrote:
> True. With other missing functions I tend to conditionally build the
> replacements into libeu.a as actual functions. That requires libeu.a
> to be linked into libdw.so, libelf.so, etc. I will create a followup
> patch that does the same with mempcpy.
If at all possible I would like elfutils to not turn into some
abstraction layer for broken non-GNU/Linux systems. I don't mind small
(mostly) obvious correct defines/checks or tweaks to help out people
using such broken systems. But if we need a lot more of these things I
think we should look if we can just import the necessary gnulib modules
to get portability functions.
Cheers,
Mark
next prev parent reply other threads:[~2017-02-17 10:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-16 9:10 Ulf Hermann
2017-02-17 9:46 ` Mark Wielaard
2017-02-17 9:50 ` Ulf Hermann
2017-02-17 10:26 ` Mark Wielaard [this message]
2017-02-17 12:16 ` Ulf Hermann
2017-02-23 11:40 ` Mark Wielaard
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=1487327166.10240.35.camel@redhat.com \
--to=mjw@redhat.com \
--cc=elfutils-devel@sourceware.org \
--cc=ulf.hermann@qt.io \
/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).