From: Thomas Wolff <towo@towo.net>
To: cygwin-apps@cygwin.com
Subject: Re: Removing cygwin32-*, cygwin64-*
Date: Sun, 14 Feb 2016 12:16:00 -0000 [thread overview]
Message-ID: <56C07023.40604@towo.net> (raw)
In-Reply-To: <r5rkbb9calicodqighe262igq7b4nuoj7m@4ax.com>
Am 09.02.2016 um 23:48 schrieb Andrew Schulman:
>> Is anyone using the cygwin32- and/or cygwin64-* cross-compiling
>> toolchain for anything besides cross-building cygwin itself? I would
>> like to remove most of these from the distro if at all possible.
> FWIW, I've tried to cross-compile some of my packages between i386 and x86_64,
> and it's never worked. The build always fails for one reason or another that I
> can't solve. So I gave up and no, I don't use them any more.
For a package maintainer, it's not only easier, but also useful for
testing, to simply install cygwin-32 and -64 in parallel.
No need for cross-building.
What about the mingw cross-compiling packages? Are they any good for
(never tried)?
Thomas
next prev parent reply other threads:[~2016-02-14 12:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-09 18:54 Yaakov Selkowitz
2016-02-09 19:48 ` Achim Gratz
2016-02-09 22:48 ` Andrew Schulman
2016-02-14 12:16 ` Thomas Wolff [this message]
2016-02-14 12:32 ` Tony Kelman
2016-02-13 6:59 ` Tony Kelman
2016-02-14 7:47 ` Achim Gratz
2016-03-17 10:18 ` Yaakov Selkowitz
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=56C07023.40604@towo.net \
--to=towo@towo.net \
--cc=cygwin-apps@cygwin.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).