public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Eli Zaretskii <eliz@gnu.org>
Cc: Doug Evans <xdje42@gmail.com>, gdb-patches@sourceware.org
Subject: Re: Building the current snapshot on Windows with Guile
Date: Mon, 09 Jun 2014 21:04:00 -0000	[thread overview]
Message-ID: <87oay14wwx.fsf@gnu.org> (raw)
In-Reply-To: <83y4x614y6.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 09 Jun	2014 18:24:33 +0300")

Eli Zaretskii <eliz@gnu.org> skribis:

> 3. Running GDB, you see this on the first invocation:
>
>      ;;; note: auto-compilation is enabled, set GUILE_AUTO_COMPILE=0
>      ;;;       or pass the --no-auto-compile argument to disable.
>      ;;; compiling d:\usr\share\gdb/guile/gdb/boot.scm
>      ;;; compiling d:\usr\share\gdb/guile/gdb\init.scm
>      ;;; compiled D:\usr\eli/.cache/guile/ccache/2.0-LE-4-2.0/d/usr/share/gdb/guile/gdb/init.scm.go
>      ;;; compiled D:\usr\eli/.cache/guile/ccache/2.0-LE-4-2.0/d/usr/share/gdb/guile/gdb/boot.scm.go
>      GNU gdb (GDB) 7.7.50.20140608-cvs

I noticed that too (not MinGW-specific), and it’s annoying, indeed.

We should compile these files and install their .go.

Ludo’.

  parent reply	other threads:[~2014-06-09 21:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-09 15:24 Eli Zaretskii
2014-06-09 15:39 ` Joel Brobecker
2014-06-09 17:30   ` Eli Zaretskii
2014-06-14 18:01   ` Eli Zaretskii
2014-06-09 21:04 ` Ludovic Courtès [this message]
2014-06-10 19:55 ` Doug Evans
2014-06-10 20:26   ` Eli Zaretskii
2014-06-11 12:24   ` Ludovic Courtès
2014-06-11 14:59     ` Eli Zaretskii
2014-06-12  8:27       ` Ludovic Courtès
2014-06-12 17:15         ` Eli Zaretskii
2014-06-12 19:46           ` Ludovic Courtès
2014-06-12 19:58             ` Eli Zaretskii
2014-06-13  8:35               ` 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=87oay14wwx.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).