From: Bruno Haible <bruno@clisp.org>
To: bug-gnulib <bug-gnulib@gnu.org>
Cc: Reuben Thomas <rrt@sc3d.org>
Subject: Re: 'relocatable' project built without --enable-relocatable
Date: Tue, 23 Apr 2024 21:46:48 +0200 [thread overview]
Message-ID: <346536552.tGq8MHzOUc@nimes> (raw)
In-Reply-To: <CAOnWdoibyWTXy3U0mua3dgEG-45B2HhXu6JQwS2TgdpW_epciA@mail.gmail.com>
Reuben Thomas wrote:
> Could macros be similarly added for the other relocatable.h
> APIs, namely set_relocation_prefix and compute_curr_prefix? This would
> allow relocate-using code to be entirely #ifdef free.
How does or would the code you are talking about look like, with #ifs?
And would it be code for a library, or for a program?
I'm asking because no package I know of is using set_relocation_prefix
explicitly [1], nor is it documented by Gnulib [2].
Bruno
[1] https://codesearch.debian.net/search?q=+set_relocation_prefix+-path%3Arelocatable.c+-path%3Arelocatable.h+-path%3Aconfigure&literal=1&page=1
[2] https://www.gnu.org/software/gnulib/manual/html_node/Supporting-Relocation.html
next prev parent reply other threads:[~2024-04-23 19:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-23 10:27 'relocatable' project built without --enable-relocatable Reuben Thomas
2024-04-23 19:46 ` Bruno Haible [this message]
2024-04-23 19:58 ` Reuben Thomas
2024-04-23 23:24 ` Bruno Haible
2024-04-24 20:36 ` Reuben Thomas
2024-04-25 12:07 ` Bruno Haible
2024-04-25 12:22 ` Reuben Thomas
2024-04-23 23:51 ` Gnulib in Debian Bruno Haible
2024-04-24 11:26 ` Reuben Thomas
2024-04-24 13:56 ` Simon Josefsson via Gnulib discussion list
2024-04-24 19:15 ` Reuben Thomas
2024-04-25 13:29 ` GNULIB_REVISION Bruno Haible
2024-04-25 16:26 ` GNULIB_REVISION Simon Josefsson via Gnulib discussion list
2024-04-25 17:00 ` GNULIB_REVISION Paul Eggert
2024-04-25 17:43 ` GNULIB_REVISION Simon Josefsson via Gnulib discussion list
2024-04-25 18:49 ` GNULIB_REVISION Paul Eggert
2024-04-25 17:48 ` GNULIB_REVISION Collin Funk
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
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=346536552.tGq8MHzOUc@nimes \
--to=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
--cc=rrt@sc3d.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).