public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: Ulf Hermann <ulf.hermann@qt.io>
To: elfutils-devel@sourceware.org
Subject: Re: [PATCH] Check for existence of asprintf and vasprintf
Date: Wed, 22 Feb 2017 16:45:00 -0000	[thread overview]
Message-ID: <59040cc2-f681-7610-5115-9a7c6c94b6c9@qt.io> (raw)
In-Reply-To: <20170222163249.GW28432@vapier>

> imo, elfutils shouldn't be growing these fallback implementations itself.
> if you want to do this stuff, use gnulib instead.
> 
> then there is no ifdef hell in the source files, and you don't have to
> worry about testing whether the ifdef's are correct because gnulib did
> it all for you.

OK, so I won't post any more patches with replacement functions. I don't like the idea of using gnulib because the gnulib implementations are generally more complex and in order to maintain them I would have to track gnulib in addition to elfutils. Also I would have to review the licenses for each import. This is not something I'm excited to do for a few 3-line functions. But OK, I will consider it.

What about switching off functionality if certain conditions aren't met? For example the patch that allows us to build libelf and libdw if argp is not available. Are such changes acceptable? I have something similar for obstack, and possibly for fts.

Ulf

  reply	other threads:[~2017-02-22 16:45 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-22 12:50 Ulf Hermann
2017-02-22 14:40 ` Mike Frysinger
2017-02-22 16:01   ` Ulf Hermann
2017-02-22 16:32     ` Mike Frysinger
2017-02-22 16:45       ` Ulf Hermann [this message]
2017-02-22 17:04         ` Mike Frysinger
2017-02-22 17:43           ` Ulf Hermann
2017-02-22 18:57             ` Mike Frysinger
2017-02-23  7:27               ` John Ogness
2017-02-23  9:39               ` Ulf Hermann
2017-02-23 18:51                 ` Mike Frysinger
2017-02-24  9:42                   ` Ulf Hermann
2017-02-24 19:15                     ` Mike Frysinger
2017-02-23 10:18           ` Ulf Hermann
2017-02-23 11:04             ` Mark Wielaard
2017-02-22 16:38     ` Mark Wielaard
2017-02-23 10:46 ` Ulf Hermann

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=59040cc2-f681-7610-5115-9a7c6c94b6c9@qt.io \
    --to=ulf.hermann@qt.io \
    --cc=elfutils-devel@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).