On 30 March 2015 at 23:55, Roman Yeryomin wrote:
> On 30 March 2015 at 22:21, John Crispin wrote:
>>
>>
>> On 30/03/2015 21:02, John Szakmeister wrote:
>>> Commit 988e3615e52b2cd9b9e07f4bbbd76494f7e0cb24 broke building
>>> e2fsprogs on an ARM platform. It looks like that in version 1.42.10
>>> t
On 30 March 2015 at 22:21, John Crispin wrote:
>
>
> On 30/03/2015 21:02, John Szakmeister wrote:
>> Commit 988e3615e52b2cd9b9e07f4bbbd76494f7e0cb24 broke building
>> e2fsprogs on an ARM platform. It looks like that in version 1.42.10
>> the decision was made to drop locally defined versions of b
On Mon, Mar 30, 2015 at 3:21 PM, John Crispin wrote:
[snip]
> fix in the making, will be pushed tomorrow ...
Thanks John!
-John
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-de
On 30/03/2015 21:02, John Szakmeister wrote:
> Commit 988e3615e52b2cd9b9e07f4bbbd76494f7e0cb24 broke building
> e2fsprogs on an ARM platform. It looks like that in version 1.42.10
> the decision was made to drop locally defined versions of both
> sync_file_range() and fallocate() because they we
Commit 988e3615e52b2cd9b9e07f4bbbd76494f7e0cb24 broke building
e2fsprogs on an ARM platform. It looks like that in version 1.42.10
the decision was made to drop locally defined versions of both
sync_file_range() and fallocate() because they were broken on 32-bit
platforms, and there was some issue
