From: Greg Troxel <gdt@ir.bbn.com>
To: Volker Grabsch <vog@notjusthosting.com>
Cc: guile-devel@gnu.org
Subject: Re: Portability fixes for win32 cross compiling
Date: Mon, 03 May 2010 08:31:05 -0400 [thread overview]
Message-ID: <rmivdb5w4ja.fsf@fnord.ir.bbn.com> (raw)
In-Reply-To: <20100503091747.GA439@flap> (Volker Grabsch's message of "Mon, 3 May 2010 11:17:47 +0200")
[-- Attachment #1: Type: text/plain, Size: 745 bytes --]
Volker Grabsch <vog@notjusthosting.com> writes:
> Volker Grabsch <vog@notjusthosting.com> schrieb:
>> Okay, I just implemented that approach and it seems to work fine.
>> There were several other issues I had to fix. Please have a look
>> at the attached patches (6 in total). All of them seem to be needed
>> to cross-compile guile for mingw32.
>
> Although I wan't able to fully solve all issues, my patches
> solved a lot of them. It would be really helpful if you could
> include (most of) them, as this would simplify things for
> anyone who'd like to finish my work.
>
> Or aren't you interested in restoring the ability of Guile
> to work with cross-compilers?
I haven't looked at your patches, but +1 for guile being cross buildable.
[-- Attachment #2: Type: application/pgp-signature, Size: 194 bytes --]
next prev parent reply other threads:[~2010-05-03 12:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-15 0:51 Portability fixes for win32 cross compiling Volker Grabsch
2010-04-15 14:12 ` Mike Gran
2010-04-15 20:58 ` Volker Grabsch
2010-04-21 20:22 ` Volker Grabsch
2010-05-03 9:17 ` Volker Grabsch
2010-05-03 12:31 ` Greg Troxel [this message]
2010-05-21 10:09 ` Andy Wingo
2010-05-22 13:44 ` Ludovic Courtès
2010-05-24 20:30 ` Volker Grabsch
2010-05-28 13:10 ` Ludovic Courtès
2010-05-28 14:56 ` Volker Grabsch
2010-06-08 22:01 ` Ludovic Courtès
2010-06-08 22:12 ` No Itisnt
2010-06-09 6:42 ` Andy Wingo
2010-07-28 12:40 ` Volker Grabsch
2010-05-28 13:15 ` Ludovic Courtès
2010-05-28 14:44 ` Volker Grabsch
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=rmivdb5w4ja.fsf@fnord.ir.bbn.com \
--to=gdt@ir.bbn.com \
--cc=guile-devel@gnu.org \
--cc=vog@notjusthosting.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).