Re: Newlib build fails

Re: Newlib build fails

[Brian Inglis]

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 config-ml.in 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

Re: Newlib build fails

[Hans-Bernhard Bröker]

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?

RE: Newlib build fails

[Keith Clifford]

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?

Re: Newlib build fails

[Mike Frysinger]

[-- Attachment #1: Type: text/plain, Size: 225 bytes --]

On 23 Jun 2023 16:57, Keith Clifford wrote:
> config-ml.in | 4 ++--

this file is maintained in the gcc tree, so you should send fixes to them.
we sync that file to the binutils/gdb/newlib trees after gcc merges fixes.
-mike

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]