From: Doug Evans <dje@google.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Pedro Alves <palves@redhat.com>,
gdb-patches <gdb-patches@sourceware.org>,
Doug Evans <xdje42@gmail.com>
Subject: Re: [PATCH] guile: Compile and install Scheme files.
Date: Sat, 19 Jul 2014 15:26:00 -0000 [thread overview]
Message-ID: <CADPb22RxK--3HUPkV1zpJHdAFf9XXr65tx4WjuOtQ8G234kfLw@mail.gmail.com> (raw)
In-Reply-To: <871tthh4uf.fsf@gnu.org>
On Sat, Jul 19, 2014 at 2:10 PM, Ludovic Courtès <ludo@gnu.org> wrote:
> Pedro Alves <palves@redhat.com> skribis:
>
>> Can we have a a comment somewhere (either in the sources, or in
>> the commit log), of _why_ we do this? E.g., is this for
>> performance, or for something else? When it is safe? Etc.
>
> Agreed, we’ll add a comment for that.
>
> Basically, Guile automatically compiles source files when it cannot find
> a pre-compiled file, but it’s just more convenient for the user if
> compiled files are installed in the first place.
I think the high order bit for the task at hand is silencing Guile
when gdb starts.
One hacky thought I had was redirecting stdout/err while we're
initializing Guile. 1/2 :-)
Long term, I think Guile changes are needed, but we need something in
the interim.
next prev parent reply other threads:[~2014-07-19 14:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-20 21:35 Ludovic Courtès
2014-07-12 12:37 ` Doug Evans
2014-07-15 9:53 ` Pedro Alves
2014-07-19 14:57 ` Ludovic Courtès
2014-07-19 15:26 ` Doug Evans [this message]
2014-07-19 16:14 ` Eli Zaretskii
2014-07-19 17:11 ` Doug Evans
2014-07-19 21:40 ` Eli Zaretskii
2014-07-19 17:06 ` Ludovic Courtès
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=CADPb22RxK--3HUPkV1zpJHdAFf9XXr65tx4WjuOtQ8G234kfLw@mail.gmail.com \
--to=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=ludo@gnu.org \
--cc=palves@redhat.com \
--cc=xdje42@gmail.com \
/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