public inbox for
 help / color / mirror / Atom feed
From: Brian Inglis <>
Cc: Keith Clifford <>
Subject: Re: Newlib build fails
Date: Fri, 23 Jun 2023 23:01:58 -0600	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <054401d9a62e$7f6da9a0$7e48fce0$>

On 2023-06-23 17:57, Keith Clifford wrote:
> I am building newlib for a MinGW cross compiler tool chain for ARM, M68K,
> and PowerPC. The build fails in all cases and I've included a patch that
> allows me to get the build to work.
> The pertinent details are:
> Newlib version:  4.3.0
> Build system: CYGWIN_NT-10.0-19045 Keith-PC 3.4.6-1.x86_64 2023-02-14 13:23
> UTC x86_64 Cygwin
> Host: MinGW
> Target: arm-eabi, m68k-elf, and powerpc-eabi   (see ${TARGET} below)
> Configure parameters: --target=${TARGET} --prefix=${PREFIX}
> The -print-multi-lib option for the respective built gcc generates output
> for which the end of line is "\r\n" and leaves the '\r' in the
> "flags" variable, in the following patch, confusing subsequent processing.

Mingw is a native Windows hosted compiler using CR-LF EoLs, as is the Git for 
Windows you are using, and the patch you generated appears to be double spaced 
with a bunch of blank lines.
If you built Cygwin-hosted cross-compilers and target binutils, and used Cygwin 
git, you would not have to deal with any CR-LF EoLs.

Take care. Thanks, Brian Inglis              Calgary, Alberta, Canada

La perfection est atteinte                   Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter  not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer     but when there is no more to cut
                                 -- Antoine de Saint-Exupéry

       reply	other threads:[~2023-06-24  5:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <054401d9a62e$7f6da9a0$7e48fce0$>
2023-06-24  5:01 ` Brian Inglis [this message]
2023-06-25 11:52 ` Hans-Bernhard Bröker
2023-06-26 22:00   ` Keith Clifford
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).