On 01/02/2017 04:50 PM, Eric Masson wrote:
I get the following error while trying to generate an image for a WGT634U :
emss@vmwdebems:~/lede-imagebuilder-brcm47xx-legacy.Linux-x86_64$ make image
PACKAGES="aiccu fwknopd luci luci-app-firewall luci-app-fwknopd luci-app-sqm
luci-proto-ipv6 luci-pr
> On Jan 2, 2017, at 10:08 PM, Philip Prindeville
> wrote:
>
> Okay, resolved…. I needed to change the Package/perl-cgi/install macro in
> the Makefile to invoke perlmod/Install/NoStrip instead of perlmod/Install.
> Sigh.
>
> Would it be reasonable to add a global variable which disables t
> On Jan 2, 2017, at 9:59 PM, Philip Prindeville
> wrote:
>
>
>> On Jan 2, 2017, at 9:32 PM, Philip Prindeville
>> wrote:
>>
>> I just saw something bizarre.
>>
>> I had a Perl module (CGI v4.35) which contained the following:
>>
>> my $appease_cpants_kwalitee = q/
>> use strict;
>> use w
> On Jan 2, 2017, at 9:32 PM, Philip Prindeville
> wrote:
>
> I just saw something bizarre.
>
> I had a Perl module (CGI v4.35) which contained the following:
>
> my $appease_cpants_kwalitee = q/
> use strict;
> use warnings;
> #/;
>
> which is just a quoted string containing the lines that
I just saw something bizarre.
I had a Perl module (CGI v4.35) which contained the following:
my $appease_cpants_kwalitee = q/
use strict;
use warnings;
#/;
which is just a quoted string containing the lines that some sanity checking
code expects to see (albeit as actual code, and not embedded a
(forgot to send in plain text, sending again for the ML)
Hi Nick,
2017-01-02 17:02 GMT-08:00 Nick Kamenyitzky :
>
> Is there any reason that the sqm-scripts makefile has a git:// link
> instead of a https:// link? At my office git:// doesn't work but
> https:// does.
>
> Should this be something
Hi Jo,
> there hasn't been much progress on the planning since I didn't follow
> any mails for the last week or so :)
>
> I plan to factor in the various suggestions into the roadmap I initially
> posted and put the result into the wiki tomorrow.
Excellent! Once that's public, we can spread the
Is there any reason that the sqm-scripts makefile has a git:// link
instead of a https:// link? At my office git:// doesn't work but
https:// does.
Should this be something that is standardised or considered?
Kind Regards,
Nick Kamenyitzky
> On Jan 2, 2017, at 1:38 PM, Alberto Bursi wrote:
>
>
>
> On 01/02/2017 07:36 PM, Philip Prindeville wrote:
>>
>>
>> Right, this is why I’m trying to create a new target (or subtarget) called
>> “xeon” which is optimized for Xeon targets and leverages the on-chip
>> crypto-accelerators.
>
> On Jan 2, 2017, at 1:05 PM, Stefan Lippers-Hollmann wrote:
>
> Hi
>
> On 2017-01-02, Philip Prindeville wrote:
>>> On Jan 2, 2017, at 10:01 AM, Jo-Philipp Wich wrote:
>>>
>>> Hi,
>>>
The x86/64/config-default is missing the following switches:
CONFIG_MCORE2=y
> [...]
>> R
On 2017-01-03 00:41, Philip Prindeville wrote:
> And I’d like to do that.
>
> (a) we’d need to decide what benchmarks are meaningful… are the openssl
> encryption benchmarks sufficient?
I think it's a good start. However, please make sure you have the same
encryption acceleration drivers enabled
> On Jan 2, 2017, at 3:06 PM, Felix Fietkau wrote:
>
> On 2017-01-02 19:36, Philip Prindeville wrote:
>> Right, this is why I’m trying to create a new target (or subtarget)
>> called “xeon” which is optimized for Xeon targets and leverages the
>> on-chip crypto-accelerators.
>>
>> We’ve come a
The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped
automatically by the mailing list software.--- Begin Message ---
This patch updates musl to 1.1.16
On 2017-01-02 19:36, Philip Prindeville wrote:
> Right, this is why I’m trying to create a new target (or subtarget)
> called “xeon” which is optimized for Xeon targets and leverages the
> on-chip crypto-accelerators.
>
> We’ve come a long way since the Athalon-64 (k8) in 2004.
I think it should b
On 01/02/2017 07:36 PM, Philip Prindeville wrote:
>
>
> Right, this is why I’m trying to create a new target (or subtarget) called
> “xeon” which is optimized for Xeon targets and leverages the on-chip
> crypto-accelerators.
>
> We’ve come a long way since the Athalon-64 (k8) in 2004.
>
> -Phil
Hi
On 2017-01-02, Philip Prindeville wrote:
> > On Jan 2, 2017, at 10:01 AM, Jo-Philipp Wich wrote:
> >
> > Hi,
> >
> >> The x86/64/config-default is missing the following switches:
> >>
> >> CONFIG_MCORE2=y
[...]
> Right, this is why I’m trying to create a new target (or subtarget) called
> On Dec 31, 2016, at 6:23 PM, Philip Prindeville
> wrote:
>
> There’s a test for “ifeq ($(ARCH),i386) … endif” but I don’t see code for
> x86_64. Do we need something like:
>
> diff --git a/include/target.mk b/include/target.mk
> index 8211ba0..5e3aae6 100644
> --- a/include/target.mk
> +++
1) In a topology like this:
ISP
|
routerA
|
routerB
|
routerC
what options now exist in lede for getting an ipv6 subnet to routerC
from routerA after being provided by the ISP? (the basic PD allocation
from ISP to A seems to work)
Can routerB get one from routerA, then C from B?
dhcp-pd?
hnc
> On Jan 2, 2017, at 10:01 AM, Jo-Philipp Wich wrote:
>
> Hi,
>
>> The x86/64/config-default is missing the following switches:
>>
>> CONFIG_MCORE2=y
>
> That would break support for older x86_64 iirc.
>
>> CONFIG_MDIO=y
>> CONFIG_X86_USE_PPRO_CHECKSUM=y
>
> Those can probably go into x86/6
> On Jan 2, 2017, at 10:08 AM, Jo-Philipp Wich wrote:
>
>> Why not instead just add a profile attribute like:
>>
>> BUILDBOT_BUILD_ME:=no
>
> Because we want to have complete coverage. Experience has shown that
> untested subtargets quickly become stale and broken.
>
> ~ Jo
Then we need mor
Hi Rich,
there hasn't been much progress on the planning since I didn't follow
any mails for the last week or so :)
I plan to factor in the various suggestions into the roadmap I initially
posted and put the result into the wiki tomorrow.
The idea is to have a definitive timeline until Friday so
Hi,
> If this is going to be the road we travel down (I'm bikeshedding here)
> wouldn't a BUILDBOT_INTERVAL:=daily/3d/7d/14d make more sense?
it wouldn't as buildbot activity is distributed randomly and the master
currently lacks suitable scheduling logic to implement such behavior.
Besides tha
Hi,
> Pruning useful subtargets to solve a buildbot resource shortage seems
> like taking a sledgehammer to kill a fly.
Saving resources was only one of the considerations to cut back the
amount of sub targets.
The introduction of per-device/per-profile rootfs support in LEDE
allowed us to build
Hi,
> The x86/64/config-default is missing the following switches:
>
> CONFIG_MCORE2=y
That would break support for older x86_64 iirc.
> CONFIG_MDIO=y
> CONFIG_X86_USE_PPRO_CHECKSUM=y
Those can probably go into x86/64 directly, at least I see no reason why
not.
> [...]
> ARCH_SUFFIX is taken
for "Freifunk Leipzig" we are using Meshkit since years. yes, its done
via a VM. We are forced to compile the whole LEDE (or openwrt) by
ourself every month in order to have ALL packages properly. (f.i. to use
"luci2" or "rpcd-mod-alfred" or sound-drivers..)
i can recommend using our leipzig
The website team has been working on the LEDE Project site to prepare it for a
blast of new readers who will come when we make the first release. We think
it's in pretty good shape, but would welcome comments from the community.
Draft home page: https://lede-project.org/playground/start2
Draft
If I remember correctly, there was a window for submitting updates for the
initial Release Candidate. Where does that process stand?
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
Hello,
I get the following error while trying to generate an image for a WGT634U :
emss@vmwdebems:~/lede-imagebuilder-brcm47xx-legacy.Linux-x86_64$ make
image PACKAGES="aiccu fwknopd luci luci-app-firewall luci-app-fwknopd
luci-app-sqm luci-proto-ipv6 luci-proto-ppp tcpdump -dnsmasq
iputils-tr
On 01/02/2017 11:23 AM, Jo-Philipp Wich wrote:
> Hi,
>
>> Freifunk (or another german site about wifi) also has a webinterface for
>> the Image Builder. I would really like to have that too.
>
> Count me in, I also support this idea. I can lend a hand with
> implementing stuff.
>
> ~ Jo
>
Nice,
On 2017-01-02 06:36, Yousong Zhou wrote:
> So these default profiles are intended more for defining packages set
> or flavours, and along with that have the side effect of
> install-images for all devices?
It can also be used to define a profile for a specific group of devices
(by adding it to PROF
Hi,
> Freifunk (or another german site about wifi) also has a webinterface for
> the Image Builder. I would really like to have that too.
Count me in, I also support this idea. I can lend a hand with
implementing stuff.
~ Jo
___
Lede-dev mailing list
Hi Florian,
ACK from me on this one. I think it makes sense.
~ Jo
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
Magnus,
Thank you.
I found that libustream-mbedtls is forced to enabled in the new releases
and this conflicts with libustream-polarssl that I had already enabled
in my router's configuration.
I disabled libustream-polarssl (libustream-mbedtls cannot be disabled)
and now the code builds. P
Package: gcc-6
Version: 6.2.0-10
Severity: serious
X-Debbugs-CC: lede-dev@lists.infradead.org
There is a regression after gcc-6 6.2.0-6. I get following output when
trying to compile LEDE/OpenWrt "Please install a static zlib"
This is wrong
$ ls -ltr /usr/lib/x86_64-linux-gnu/libz.a
-rw-r--r-- 1
On Fri, 30 Dec 2016 06:52:32 -0800
Dana Myers wrote:
> On 12/29/2016 11:50 PM, Ralph Sennhauser wrote:
> > Hi Dana
> >
> > On Thu, 29 Dec 2016 12:30:37 -0800
> > Dana Myers wrote:
> >
> >> In reference to https://github.com/openwrt/packages/pull/3686
> >>
> >> We've added OpenWRT support for:
35 matches
Mail list logo
