From: Neil Jerram <neil@ossau.uklinux.net>
To: Andy Wingo <wingo@pobox.com>
Cc: "Ludovic Courtès" <ludo@gnu.org>, guile-devel@gnu.org
Subject: Re: [Guile-commits] GNU Guile branch, wip-1-8-mingw-build, updated. release_1-8-7-22-g7edad77
Date: Fri, 26 Mar 2010 22:17:10 +0000 [thread overview]
Message-ID: <87pr2q3ezd.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <m3aatvs2v7.fsf@pobox.com> (Andy Wingo's message of "Fri, 26 Mar 2010 13:07:24 +0100")
Andy Wingo <wingo@pobox.com> writes:
> We have a cross-compilation problem in general right now, no?
Not that I'm aware of; at least not for branch_release-1-8. I think the
problems that drove me to conclude that MinGW cross-compilation isn't
productive are all Windows-specific, to do with differences between the
emulated build environment and a real Windows environment.
> Thinking a little about this, I would think that you would need a C
> cross-compiler, and a Guile cross-compiler. So Guile's build needs a way
> to specify a Guile to use during the build process.
We have this: GUILE_FOR_BUILD.
However, that prompts me to realize that perhaps I'm not really
addressing your question properly. Because for my MinGW/Wine build I
actually had to suppress the use of GUILE_FOR_BUILD (see [1]). So
perhaps what I've been doing isn't actually cross-compiling in the sense
that you're thinking.
[1] http://git.savannah.gnu.org/gitweb/?p=guile.git;a=commit;h=c9e1f32768232495d1452a45110115ac7c035acd
>> I'll leave the wip-1-8-mingw-build branch in the repository, in case
>> it's of interest, and because I don't know if branches can be deleted.
>
> To delete, git push origin :wip-1-8-mingw-build. (I'm not suggesting
> that the branch be deleted.)
Ah yes, thanks.
Regards,
Neil
prev parent reply other threads:[~2010-03-26 22:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1NnhBU-0002dm-1u@vcs-noshell.in.savannah.gnu.org>
2010-03-06 22:22 ` [Guile-commits] GNU Guile branch, wip-1-8-mingw-build, updated. release_1-8-7-22-g7edad77 Ludovic Courtès
2010-03-07 22:30 ` Neil Jerram
2010-03-26 0:31 ` Neil Jerram
2010-03-26 12:07 ` Andy Wingo
2010-03-26 13:37 ` Thien-Thi Nguyen
2010-03-26 22:42 ` Neil Jerram
2010-03-26 22:17 ` Neil Jerram [this message]
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=87pr2q3ezd.fsf@ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=guile-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=wingo@pobox.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).