Re: [PATCH 1/7] newlib: libm: merge machine/ trampoline up a level

[Jon Turney <jon.turney@dronecode.org.uk>]

On 28/01/2022 00:37, Mike Frysinger wrote:
> On 27 Jan 2022 15:28, Jon Turney wrote:
>> I hadn't noticed before, but there also seems to be something in this
>> series which seems to break building for x86.
> 
> i haven't been able to get an i686 or x86_64 build of newlib working at all.

Even on niche architectures like those, you'd think there was *someone* 
using newlib. :)

> like, not even before i landed any commits.  so it's been hard for me to test
> those targets specifically.  cygwin in particular doesn't work out of the box
> as building gcc blows up :(.

Yeah, gcc possibly requires some patches for that.

A copr with a cygwin toolchain exists, which that workflow probably 
serves as an example of how to use to setup a container to build for cygwin.

Or you could just fork that repo, or push to a topic branch on 
sourceware, and that CI should run on it.

> i sent you a small patch series which should fix this though.

Thanks.

Those seem to fix it, and make sense.

There might be some scope in [2/3] for using ${srcdir} relative paths, 
rather than making everything absolute?