From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: RFC: usage of cygwin32-/cygwin64- cross-toolchains
Date: Fri, 10 Jan 2014 09:47:00 -0000 [thread overview]
Message-ID: <20140110094745.GD10296@calimero.vinschen.de> (raw)
In-Reply-To: <52CF85FC.2080201@users.sourceforge.net>
[-- Attachment #1: Type: text/plain, Size: 2192 bytes --]
On Jan 9 23:32, Yaakov (Cygwin/X) wrote:
> Now that we're long finished bootstrapping cygwin64, I was wondering
> to what degree (if any) are the cygwin32-* and cygwin64-* packages
> in either the Cygwin distro or the Fedora Cygwin repository are of
> actual use. If you are using any of these, please specify on which
> platform you are using them (i686/x86_64, Cygwin, F19, or if you
> want to move to F20) and to what extent (IOW "to build Cygwin
> package A/B/C which require libraries X/Y/Z"). This will help me
> best manage my time wrt keeping these updated.
I'm using the F19 version on F19 and F20. Updating to F20 would be
nice, but the F19 versions work fine on F20. You just have to tweak
the cygwin.repo file to get them.
Here's the list of packages I've installed right now:
cygport
cygwin-binutils-generic
cygwin-filesystem-base
cygwin32
cygwin32-binutils
cygwin32-cpp
cygwin32-crypt
cygwin32-crypt-static
cygwin32-filesystem
cygwin32-gcc
cygwin32-gcc-c++
cygwin32-gettext
cygwin32-gettext-static
cygwin32-libbfd
cygwin32-libiconv
cygwin32-libiconv-static
cygwin32-libltdl
cygwin32-libtool
cygwin32-ncurses
cygwin32-readline
cygwin32-w32api-headers
cygwin32-w32api-runtime
cygwin32-zlib
cygwin32-zlib-static
cygwin64
cygwin64-binutils
cygwin64-bzip2
cygwin64-cpp
cygwin64-crypt
cygwin64-crypt-static
cygwin64-expat
cygwin64-filesystem
cygwin64-gcc
cygwin64-gcc-c++
cygwin64-gettext
cygwin64-gettext-static
cygwin64-glib2
cygwin64-gmp
cygwin64-isl
cygwin64-libbfd
cygwin64-libedit
cygwin64-libffi
cygwin64-libiconv
cygwin64-libiconv-static
cygwin64-libltdl
cygwin64-libmpc
cygwin64-libtool
cygwin64-libxml2
cygwin64-mpfr
cygwin64-ncurses
cygwin64-openssl
cygwin64-pcre
cygwin64-ppl
cygwin64-readline
cygwin64-w32api-headers
cygwin64-w32api-runtime
cygwin64-zlib
cygwin64-zlib-static
fedora-cygwin-release
Thanks,
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2014-01-10 9:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-10 5:32 Yaakov (Cygwin/X)
2014-01-10 6:06 ` Christopher Faylor
2014-01-10 7:01 ` Yaakov (Cygwin/X)
2014-01-10 16:55 ` Christopher Faylor
2014-01-10 9:47 ` Corinna Vinschen [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=20140110094745.GD10296@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--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).