From: Eli Zaretskii <eliz@gnu.org>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-user@gnu.org
Subject: Re: guile-2.0 on mingw: the sequel
Date: Mon, 26 Aug 2013 05:35:35 +0300 [thread overview]
Message-ID: <83a9k5gow8.fsf@gnu.org> (raw)
In-Reply-To: <87d2p18umg.fsf@gnu.org>
> From: ludo@gnu.org (Ludovic Courtès)
> Date: Sun, 25 Aug 2013 20:59:03 +0200
>
> > Why should this feature be limited to Windows builds of Guile? Why
> > not make it work for Posix platforms as well? Some other projects
> > already do, they use argv[0] and PATH search to find the place where
> > the executable is installed, and record relative file names from
> > there.
>
> This is not completely reliable when using argv[0] because argv[0] can
> be anything, though this can be work around on Linux-based systems with
> /proc/self/exe as done in
> <http://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/patches/guile-relocatable.patch>.
Indeed.
> Here’s a proposal: add a --enable-relocatable configure option, have it
> default to yes on MinGW and Cygwin (assuming there’s a method that works
> reliably on these), and default to no elsewhere; alternately, have it
> default to no everywhere.
>
> WDYT?
Sounds good to me, thanks.
next prev parent reply other threads:[~2013-08-26 2:35 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-22 20:25 guile-2.0 on mingw: the sequel Panicz Maciej Godek
2013-08-23 6:38 ` Eli Zaretskii
2013-08-23 9:29 ` Panicz Maciej Godek
2013-08-23 10:16 ` Eli Zaretskii
2013-08-23 20:14 ` Panicz Maciej Godek
2013-08-24 6:31 ` Eli Zaretskii
2013-08-24 8:05 ` Panicz Maciej Godek
2013-08-25 15:26 ` Eli Zaretskii
2013-08-25 16:59 ` Mark H Weaver
2013-08-25 17:47 ` Eli Zaretskii
2013-08-25 19:03 ` Ludovic Courtès
2013-08-25 19:34 ` Mark H Weaver
2013-08-27 21:51 ` Panicz Maciej Godek
2013-08-26 13:28 ` Eli Zaretskii
2013-08-23 15:13 ` Mark H Weaver
2013-08-23 15:34 ` Eli Zaretskii
2013-08-25 18:59 ` Ludovic Courtès
2013-08-25 21:19 ` Mark H Weaver
2013-08-26 2:35 ` Eli Zaretskii [this message]
2013-08-25 19:50 ` Mark H Weaver
2013-08-25 19:56 ` Mark H Weaver
2013-08-25 20:33 ` Eli Zaretskii
2013-08-25 20:40 ` Eli Zaretskii
2013-08-25 21:42 ` Mark H Weaver
2013-08-25 23:24 ` dsmich
2013-08-26 2:44 ` Eli Zaretskii
2013-08-26 5:56 ` Mark H Weaver
2013-08-26 6:26 ` Mark H Weaver
2013-08-26 13:10 ` Eli Zaretskii
2013-08-26 2:40 ` Eli Zaretskii
2013-08-25 20:32 ` Eli Zaretskii
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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83a9k5gow8.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=guile-user@gnu.org \
--cc=ludo@gnu.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).