From: Eli Zaretskii <eliz@gnu.org>
To: Doug Evans <dje@google.com>
Cc: ludo@gnu.org, palves@redhat.com, gdb-patches@sourceware.org,
xdje42@gmail.com
Subject: Re: [PATCH] guile: Compile and install Scheme files.
Date: Sat, 19 Jul 2014 21:40:00 -0000 [thread overview]
Message-ID: <83a9855l50.fsf@gnu.org> (raw)
In-Reply-To: <CADPb22T4GfC+COb95+LfBL_pkyF28+ZA0FDwPrV1TUUC1pW=OQ@mail.gmail.com>
> Date: Sat, 19 Jul 2014 18:06:53 +0100
> From: Doug Evans <dje@google.com>
> Cc: Ludovic Courtès <ludo@gnu.org>,
> Pedro Alves <palves@redhat.com>, gdb-patches <gdb-patches@sourceware.org>,
> Doug Evans <xdje42@gmail.com>
>
> On Sat, Jul 19, 2014 at 4:25 PM, Eli Zaretskii <eliz@gnu.org> wrote:
> >> Date: Sat, 19 Jul 2014 15:57:08 +0100
> >> From: Doug Evans <dje@google.com>
> >> Cc: Pedro Alves <palves@redhat.com>, gdb-patches <gdb-patches@sourceware.org>, Doug Evans <xdje42@gmail.com>
> >>
> >> I think the high order bit for the task at hand is silencing Guile
> >> when gdb starts.
> >
> > Why? If the *.scm files are compiled to begin with, Guile is silent
> > when GDB starts.
>
> Right. And that's the high order bit (main reason) why we're taking
> the route of precompiling them.
If we intend to precompile them (to which I agree), then we shouldn'
talk about redirecting the startup messages, because they won't be
there.
next prev parent reply other threads:[~2014-07-19 17:11 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
2014-07-19 16:14 ` Eli Zaretskii
2014-07-19 17:11 ` Doug Evans
2014-07-19 21:40 ` Eli Zaretskii [this message]
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=83a9855l50.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=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