From: "Keith Clifford" <kclifford@tranaptic.ca>
To: "'Hans-Bernhard Bröker'" <HBBroeker@t-online.de>, newlib@sourceware.org
Subject: RE: Newlib build fails
Date: Mon, 26 Jun 2023 15:00:54 -0700 [thread overview]
Message-ID: <065b01d9a879$ae477c90$0ad675b0$@tranaptic.ca> (raw)
In-Reply-To: <4cf65a8e-8f36-1891-e988-eadac34fa979@t-online.de>
Hi,
Originally, I did build it under MinGW using MSYS but it was becoming troublesome keeping it all working with the changes to MSYS and MinGW that were going on at the time. MinGW is nowhere nearly as well supported as Cygwin. Cygwin offers a much richer build/development environment. At least in theory, I should be able to run whatever I build in the Cygwin environment. Cygwin is maintained better. Other than one hiccup that had nothing to do with Cygwin, once I got the compilers building under Cygwin, I've had relatively little trouble continuing to build them compared to the difficulties I had had under MinGW.
Regards,
Keith
Keith Clifford
Cell: 250 888-4558
Email: kclifford@tranaptic.ca
Web: https://www.tranaptic.ca
-----Original Message-----
From: Newlib <newlib-bounces+kclifford=tranaptic.ca@sourceware.org> On Behalf Of Hans-Bernhard Bröker
Sent: June-25-23 4:52 AM
To: newlib@sourceware.org
Subject: Re: Newlib build fails
Am 24.06.2023 um 01:57 schrieb Keith Clifford:
> Hi,
>
> I am building newlib for a MinGW cross compiler tool chain for ARM,
> M68K, and PowerPC.
But why are you building it as a "canadian cross"? In other words, why would you use Cygwin to build this cross compiler, instead of MinGW itself?
next prev parent reply other threads:[~2023-06-26 22:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <054401d9a62e$7f6da9a0$7e48fce0$@tranaptic.ca>
2023-06-24 5:01 ` Brian Inglis
2023-06-25 11:52 ` Hans-Bernhard Bröker
2023-06-26 22:00 ` Keith Clifford [this message]
2023-10-15 10:23 ` Mike Frysinger
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='065b01d9a879$ae477c90$0ad675b0$@tranaptic.ca' \
--to=kclifford@tranaptic.ca \
--cc=HBBroeker@t-online.de \
--cc=newlib@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).