From: Andy Wingo <wingo@pobox.com>
To: Neil Jerram <neil@ossau.uklinux.net>
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 13:07:24 +0100 [thread overview]
Message-ID: <m3aatvs2v7.fsf@pobox.com> (raw)
In-Reply-To: <87fx3ngbyt.fsf@ossau.uklinux.net> (Neil Jerram's message of "Fri, 26 Mar 2010 00:31:38 +0000")
On Fri 26 Mar 2010 01:31, Neil Jerram <neil@ossau.uklinux.net> writes:
> Neil Jerram <neil@ossau.uklinux.net> writes:
>
> But anyway, following more careful thinking and feedback from the
> "Reconsideration of MinGW" thread, I think that that method of
> cross-building (i.e. with a cross-compiler and Wine on Linux) is pretty
> unfruitful and I don't propose to continue it.
We have a cross-compilation problem in general right now, no?
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.
> 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.)
> Is there a nice way of marking a branch as obsolete/historical, or of
> adding an explanatory note to it?
I don't know. It would only be for purposes of gitweb/cgit, I don't
think git has this concept.
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2010-03-26 12:07 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 [this message]
2010-03-26 13:37 ` Thien-Thi Nguyen
2010-03-26 22:42 ` Neil Jerram
2010-03-26 22:17 ` Neil Jerram
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=m3aatvs2v7.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=neil@ossau.uklinux.net \
/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).