[LEDE-DEV] [PATCH] musl: backport various post-1.1.15 fixes

[Koen Vandeputte]

On 2016-12-22 16:27, Felix Fietkau wrote:
> I think we should probably just update musl to current git instead, and
> avoid carrying so many patches.
>
> - Felix
>


Hi Felix,

This patch was born out of the discussion below:

Besides the method being used (patches vs HEAD bump),
what is your opinion on adding these fixes close to branch-day?



On 22/12/2016 13:19, Koen Vandeputte wrote:

> On 2016-12-21 20:13, Jo-Philipp Wich wrote:
>> - Are there any outstanding changes?
>>
>>     Is there important changes we should wait for before branching the
>>     release? Is there pending stuff in the staging trees which should
>>     absolutely go into the first release?
>>
> Bump musl to a newer head? (or better to backport some fixes?)
>
i thinkt hat bumping the libc shortly before the release is a really bad
idea. it might fix some problems but can introduce some regressions

> I see a lot of fixes since 1.1.15 on important parts which could
> influence stability as a lot of packages depend on musl:
>
backporting would be an option. could you provide a patch adding these
fixes ?

	John



-- 
Koen Vandeputte - Software Developer
koen.vandeputte at ncentric.com | +32499736158