Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Doug Evans <xdje42@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
	 "gdb-patches\@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: Building the current snapshot on Windows with Guile
Date: Wed, 11 Jun 2014 12:24:00 -0000	[thread overview]
Message-ID: <87ha3rocq3.fsf@gnu.org> (raw)
In-Reply-To: <CAP9bCMQHCL7Riah5Z-M4Puo=qi1QLcv_Z6fVB8p=RdzLaNoUwQ@mail.gmail.com>	(Doug Evans's message of "Tue, 10 Jun 2014 12:55:09 -0700")

Doug Evans <xdje42@gmail.com> skribis:

> (*1): As Ludo suggested, we could compile these files during a gdb
> build, but that doesn't work in a cross-compilation scenario (without
> requiring more complexity in the build, which would be nice to avoid).
> Are these files guaranteed to be equivalent across configurations (I'm
> guessing not), and if not does guile provide a cross-compiler for them
> (I'm guessing not - could be wrong of course)?

It does provide a cross-compiler (info "(guile) Compilation"):

  guix compile --target=mips64el-linux-gnu foo.scm -o foo.go

But note that the interpretation of triplets might defer from that of
GDB.  In particular, for platforms that support several ABIs with
different word sizes, it recognizes some specific triplet
extensions–e.g., “mips64el-linux-gnuabi64” for the N64 ABI on MIPS.  See
<http://git.savannah.gnu.org/cgit/guile.git/tree/module/system/base/target.scm#n76>.

Ludo’.


  parent reply	other threads:[~2014-06-11 12:24 UTC|newest]

Thread overview: 13+ 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-14 18:01   ` Eli Zaretskii
2014-06-09 21:04 ` Ludovic Courtès
2014-06-10 19:55 ` Doug Evans
2014-06-10 20:26   ` Eli Zaretskii
2014-06-11 12:24   ` Ludovic Courtès [this message]
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=87ha3rocq3.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