From: Rafał Miłecki
This fixes upstream regression introduced in 1.4.40. It was reported &
debugged in https://redmine.lighttpd.net/issues/2793
This fix is queued for 1.4.46 in the personal/gstrauss/master upstream
branch.
Signed-off-by: Rafał Miłecki
---
thanks, i will try
Gesendet: Mittwoch, 22. Februar 2017 um 01:43 Uhr
Von: Ufo
An: Lede-dev@lists.infradead.org
Betreff: Re: [LEDE-DEV] Is there a Image for TP-Link TL-WA854RE (WiFi Range
Extender) ?
> On Sat, Feb 18, 2017 at 06:32:53PM +0100, Dennis Schneck
I think this patch needn't be reverted as it do fix the incorrect
setting of marking port4 as eth1.What we need is just another commit
to separate ar9331/ar934x devices from these to correct the port order
of the 4 lan ports.
Regards.
Chuanhong Guo
2017-02-21 2:39 GMT+08:00 John Crispin
> On Sat, Feb 18, 2017 at 06:32:53PM +0100, Dennis Schneck wrote:
>> Hello,
>> is there a Image for TP-Link TL-WA854RE ?
Am 18.02.17 um 19:40 schrieb Daniel Golle:
> As a hack or temporary work-around, this is easy to achieve though.
854v1:
On 02/21/2017 05:12 AM, Felix Fietkau wrote:
> On 2017-02-05 03:41, Florian Fainelli wrote:
>> In case we are building against a kernel that is too old and does not
>> support SYS_getrandom, error out with a message indicating so.
>>
>> Signed-off-by: Florian Fainelli
>>
Hello,
I tried to install latest LEDE to RB411AH board. Sysupgrade worked
fine, but device now do not boot at all. Bootloader claims that it
could not find kernel :(
I tracked down the situation and found that the kernel partition image
generated with assumption that any 64Mb NAND flash IC
Hi,
the issue is introduced by the commit 'opkg: switch to own fork to improve
memory usage' and makes current builds more
or less unusable.
If I revert this commit and go back the old opkg package, sysupgrade does
restore the previous configuration completely
and manually generated backups
>> Most work is already done against 17.01-rc2 and there is working
>> factory and sysupgrade images.
>
>Please, base your work on master branch.
Most work was done against master but later backported to rc2 in
terms of stability in packages. It is not a problem to revert it
back to master.
On 22 February 2017 at 01:01, Nathan Hintz wrote:
>
> Hi Yousong:
>
> Sorry for the spam. I've subscribed to the list hoping that is the reason my
> email replies are being bounced by lede-dev (I can send patches to the list
> using git send-mail just fine).
>
> Comments are
Hi,
I tried to compile Asterisk 11.x, then i got the following compile error:
Can someone give me a hint ?
Perry
checking for getloadavg... yes
checking for setenv... yes
checking for strcasestr... yes
checking for strndup... yes
checking for strnlen... yes
checking for strsep... yes
checking
May be this can help you
cd source
cp -r ./build_dir/hostpkg/libxml2-2.9.4/include/libxml staging_dir/host/include
https://github.com/openwrt/telephony/issues/133
Gesendet: Dienstag, 21. Februar 2017 um 17:49 Uhr
Von: "Perry Couprie"
An:
> Did you recompile lede? I need to do this with lede (stock).
Haven’t tried with latest lede.
Using OpenWRT CC, I do have to rebuild the kernel after changing
LXC_KERNEL_OPTIONS.
For CC, kernel namespaces are off by default.
-Jeff
___
Lede-dev
The fakeroot header is expected by the netgear bootloader in the last
64 bytes of the last block used by the uImage. With the current
linux-4.9 uImage being more than 128k smaller than the linux-4.4 uImage
the bootloader was unable to locate the rootfs ih_magic and was
refusing to load and start
Hello!
There's an issue with the stdlibc++ which prevents the Boost.Context
package from compiling.
It seems the stdlibc++ versions until 7.0 are not implementing the
exception_ptr if the target architecture does not support
ATOMIC_INT_LOCK_FREE >= 2. The bug reports can be found here:
->
I think it is only useful to know if kernel is behind or after a
specific version.
On Tue, Feb 21, 2017 at 9:17 AM, Rafał Miłecki wrote:
> On 20 February 2017 at 20:03, Mauro Mozzarelli wrote:
>> There is in some cases where kernel drivers have changed.
On 2017-02-05 03:41, Florian Fainelli wrote:
> In case we are building against a kernel that is too old and does not
> support SYS_getrandom, error out with a message indicating so.
>
> Signed-off-by: Florian Fainelli
> ---
> CMakeLists.txt | 15 +++
> 1 file
Dear All,
My apologies, press wrongly.
-Original Message-
From: Phyu The
Sent: Tuesday, February 21, 2017 5:50 PM
To: Jonas Gorski ; Mauro Mozzarelli
Cc: LEDE Development List ; Magnus Kroken
Subject: Re: [LEDE-DEV] Identifying kernel version (major) during build (.mk
file)
Dear
Dear Jonas,
If the granularity requires to specify the patchlevel, and if LEDE had more
than one Kernel 3 patchlevel instead of just 3-18, then I would have to
specify all of them in my makefile. Not only that, but also I would have to
modify my maskefile to include new Kernel 3 versions
18 matches
Mail list logo