building newlib with recent versions of autotools

Daniel Alley daniel.alley6@gmail.com
Mon Feb 12 16:42:00 GMT 2018


Could you expand on what some of those side effects and breakages were?  I
know nothing at all about autotools unfortunately, but perhaps that
information might help someone else take a crack at the issue.

Do you know of any other developers within the gcc or autotools communities
that might be willing to help work through some of those issues?

On Sun, Feb 11, 2018 at 5:54 PM, Hans-Bernhard Bröker <HBBroeker@t-online.de
> wrote:

> Am 11.02.2018 um 06:05 schrieb Daniel Alley:
>
>> I looked through the mailing list archives and noticed that there was a
>> series of emails  about this in 2016 which made (what seems like, to an
>> uninformed observer), a fairly significant amount of progress towards
>> fixing the issue.  But the discussion seems to have abruptly ended without
>> much in the way of resolution, and it doesn't appear as though any actions
>> were taken.
>>
>
> On my end the effort essentially petered out because it turned out there
> were some serious side effects that broke parts of the build, at least for
> native build Cygwin+Newlib on Cygwin.  I never fully managed to fix those,
> so I gave up on the idea.
>
>
>



More information about the Newlib mailing list