From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug libelf/23903] Uses linux specifc mremap
Date: Fri, 23 Nov 2018 20:31:00 -0000 [thread overview]
Message-ID: <bug-23903-10460-LMRLV2tasH@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-23903-10460@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=23903
--- Comment #6 from Mark Wielaard <mark at klomp dot org> ---
It is fine for elfutils to have GNU/Linux specific code since that is the
primary target. But if other platforms provide needed functionality in a
different way then patches are obviously more than welcome. In the case of
mremap you could even get away with something that always fails. Which would
probably work just fine for Hurd, but for kfreebsd you really need to figure
out first why it seems to provide a mremap function but then fails while
linking. Otherwise it will be hard to know when/why to provide an alternative.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2018-11-23 20:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-20 20:28 [Bug libelf/23903] New: " kurt at roeckx dot be
2018-11-21 12:31 ` [Bug libelf/23903] " mark at klomp dot org
2018-11-21 19:21 ` kurt at roeckx dot be
2018-11-21 19:25 ` kurt at roeckx dot be
2018-11-23 9:11 ` mark at klomp dot org
2018-11-23 17:43 ` kurt at roeckx dot be
2018-11-23 20:31 ` mark at klomp dot org [this message]
2018-11-23 21:29 ` kurt at roeckx dot be
2019-08-03 20:17 ` bibi584762 at gmail dot com
2019-08-03 20:56 ` mark at klomp dot org
2019-08-04 6:30 ` bibi584762 at gmail dot com
2019-08-04 16:38 ` bibi584762 at gmail dot com
2019-08-04 16:47 ` bibi584762 at gmail dot com
2019-08-09 21:19 ` mark at klomp dot org
2019-08-26 14:29 ` mark at klomp dot org
2022-07-01 21:25 ` mark at klomp dot org
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-23903-10460-LMRLV2tasH@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--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).