From: Karl Trygve Kalleberg <karltk@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Cross compilation and mingw32
Date: Thu, 31 Oct 2002 14:26:44 +0100 [thread overview]
Message-ID: <20021031142644.2145e377.karltk@gentoo.org> (raw)
In-Reply-To: <20021031111629.GA7055@mefriss1.swan.ac.uk>
We have a submission of cross-compilation builds using MingW:
http://bugs.gentoo.org/show_bug.cgi?id=2626
If somebody could update the ebuilds to the most recent version of MingW,
and have them follow the latest policy (see
http://www.gentoo.org/~karltk/POLICY.txt and skel.ebuild), and run lintool
(dev-util/lintool-0.2.4 or later) on them, I'll squeeze them in ASAP.
We're currently working on a scheme for cross-compilers. The primary
testing candidate until now has been a cross-compiler for the
sh4-linux-gnu target, but we need more targets, so if anybody has the
necessary time, please don't hesistate to finish up set of working ebuilds
for mingw, and I'll take it from there.
Kind regards,
Karl T
prev parent reply other threads:[~2002-10-31 13:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-31 9:23 [gentoo-dev] Cross compilation and mingw32 James Michael DuPont
2002-10-31 10:32 ` Paul de Vrieze
2002-10-31 11:16 ` José Fonseca
2002-10-31 13:26 ` Karl Trygve Kalleberg [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20021031142644.2145e377.karltk@gentoo.org \
--to=karltk@gentoo.org \
--cc=gentoo-dev@gentoo.org \
/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