From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin-apps@cygwin.com
Subject: Re: [ITA] mingw64-x86_64-curl, mingw64-i686-curl
Date: Sat, 22 Aug 2020 00:09:43 -0600 [thread overview]
Message-ID: <20e56419-02ef-e58f-3693-e0af4abc249f@SystematicSw.ab.ca> (raw)
In-Reply-To: <DB7PR02MB3996CAB553AFB60C35EE539FE75B0@DB7PR02MB3996.eurprd02.prod.outlook.com>
On 2020-08-21 09:28, Hamish McIntyre-Bhatty via Cygwin-apps wrote:
> On 21/08/2020 15:24, ASSI wrote:
>> Hamish McIntyre-Bhatty via Cygwin-apps writes:
>>> How does cross compiling for 32-bit Cygwin work? I think it'd be useful
>>> for me too - in one instance I've found that stripping debug symbols can
>>> take 3 times as long to run under 32-bit Cygwin.
>> I don't cross-compile to Cygwin, only to MingW. I believe there are
>> some packages that are cross-compiled from Linux, but with any of these
>> cross-compilation options you can't actually run the tests, so that is
>> the reason for not doing it for Cygwin (for me anyway). Also there's
>> quite a bunch of software out there that doesn't really like to be
>> cross-compiled and needs major effort to do so.
> Oh, I wasn't very clear. I meant using 64-bit Cygwin to compile for
> 32-bit Cygwin. Could be wrong but I'm pretty sure it's been mentioned
> before.
You could try installing packages starting with cygwin32:
cygwin32
cygwin32-binutils
cygwin32-binutils-debuginfo
cygwin32-default-manifest
cygwin32-gcc-ada
cygwin32-gcc-cilkplus
cygwin32-gcc-core
cygwin32-gcc-debuginfo
cygwin32-gcc-fortran
cygwin32-gcc-g++
cygwin32-gcc-objc
cygwin32-gcc-objc++
cygwin32-gettext
cygwin32-libbfd
cygwin32-libiconv
cygwin32-libtool
cygwin32-minizip
cygwin32-w32api-headers
cygwin32-w32api-runtime
cygwin32-zlib
download Cygwin sources and add to top of cygport, or do the equivalent of:
CROSS_HOST=i686-pc-cygwin
inherit cross
and try running cygport to see what happens.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in IEC units and prefixes, physical quantities in SI.]
next prev parent reply other threads:[~2020-08-22 6:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-20 16:49 Brian Inglis
2020-08-20 18:18 ` Achim Gratz
2020-08-20 19:47 ` Brian Inglis
2020-08-20 20:20 ` Hamish McIntyre-Bhatty
2020-08-20 20:36 ` Brian Inglis
2020-08-21 14:24 ` ASSI
2020-08-21 15:28 ` Hamish McIntyre-Bhatty
2020-08-22 6:09 ` Brian Inglis [this message]
2020-08-22 6:17 ` ASSI
2020-09-06 4:57 ` Brian Inglis
2020-09-06 6:46 ` Marco Atzeri
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=20e56419-02ef-e58f-3693-e0af4abc249f@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--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).