Hello,
Le 28/02/2012 13:05, Emmanuel Deloget a écrit :
SSL support adds a quite large dependency to lighttpd when compiled
in. On a 32 bit platform, libcrypto is roughly 1MB, to which one must
add the size of libssl (roughly 250KB). This is 2 to 5 times the size
of a typical lighttpd embedded
regards,
-- Emmanuel Deloget
[1] http://patchwork.openwrt.org/patch/1924/
Le 19/03/2012 15:05, Peter Wagner a écrit :
both packaes are build in a sepreate folders
so yes - you can select both packages.
But you can also building both and testing it ;)
/Peter
On Monday 19 March 2012 13:24:24
remedy to this situation using a simple yet effective solution:
removing the offending code, as it doesn't change anything in terms of
security and functionnality.
-- Emmanuel Deloget
[1] the write_pool() function ends up calling mix_pool_bytes_extract(),
which has the following comment
replace it with klish?
Best regards,
-- Emmanuel Deloget
[1] https://lists.openwrt.org/pipermail/openwrt-devel/2012-February/014277.html
[2] http://code.google.com/p/klish/
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https
without pushing out clish.
I'm fine with this. I'll let other (Viktar or anyone else) decide what
to do with clish.
Next message will contain a patch with a request to add klish to the
packages repository (this next message will not be CC'ed).
On Tue, Apr 10, 2012 at 10:47 AM, Emmanuel Deloget
The klish is a framework for implementing a CISCO-like CLI on a UNIX
systems. It is configurable by XML files. The KLISH stands for Kommand
Line Interface Shell.
klish is an active fork of the clish program created by Graeme
McKerrell.
Signed-off by: Emmanuel Deloget log...@free.fr
Index
easy to adopt old clish XML
configs for klish but the user must be ready for a little behaviour
differencies.
Thanks for the clarification - text updated (see below).
Thanks.
Best regards,
-- Emmanuel Deloget
---8-
The klish
Hello,
(working on trunk...)
It seems (to me; I can be wrong) that patch 100-do-not-use-implicit-rules.patch
for eglibc-2.12 is not needed, as this version already contains it.
Can someone confirm this before I send a patch / open a ticket?
Best regards,
-- Emmanuel Deloget
From: Mirko Vogt li...@nanl.de To: Emmanuel Deloget emmanuel.delo...@efixo.com,OpenWrt Development List openwrt-devel@lists.openwrt.org CC:
Hey Emmanuel,
I levelled up all versions of eglibc to it's latest revisions of its
respective branches ( https://dev.openwrt.org/changeset/31300
Le 17/04/2012 23:07, Luka Perkov a écrit :
On Tue, Apr 17, 2012 at 10:51:47PM +0200, Emmanuel Deloget wrote:
htmlhead
meta http-equiv=Content-Type content=text/html; charset=iso-8859-1
meta name=Generator content=Microsoft Exchange Server
!-- converted from text --
style!-- .EmailQuote { margin
.
Signed-off-by: Emmanuel Deloget log...@free.fr
Index: toolchain/eglibc/Config.in
===
--- toolchain/eglibc/Config.in (révision 31345)
+++ toolchain/eglibc/Config.in (copie de travail)
@@ -22,15 +22,19 @@
endchoice
+config
Le 19/04/2012 15:02, Mirko Vogt a écrit :
On 04/19/2012 11:43 AM, Emmanuel Deloget wrote:
Force the use of known revision for specific eglibc versions.
Eglibc revision can only be changed if the user selects the trunk
version.
Signed-off-by: Emmanuel Delogetlog...@free.fr
Index: toolchain
Le 19/04/2012 16:40, Mirko Vogt a écrit :
On 04/19/2012 04:00 PM, Emmanuel Deloget wrote:
Good catch. In fact, HEAD is likely to never be the right choice, even
in other packages. So maybe we can forbid it?
That's what I meant with:
Since fetching the latest HEAD of any external source
Hello,
snip things about PKG_VERSION and so on
Le 19/04/2012 18:40, Emmanuel Deloget a écrit :
I have no idea on how we can fix this, other than setting the correct
version numbers in the CONFIG_EGLIBC_VERSION.
I can provide a patch to fix the current state, but that would not make
much sense
failed. Please re-run make with V=99
to see what's going on
make: *** [package/base-files/compile] Erreur 1
Signed-off-by: Emmanuel Deloget log...@free.fr
Index: toolchain/eglibc/Config.version
===
--- toolchain/eglibc/Config.version
if the selected version is the eglibc trunk. Some labels
are modified in the process to clarify the system.
Signed-off-by: Emmanuel Deloget log...@free.fr
Index: toolchain/eglibc/Config.in
===
--- toolchain/eglibc/Config.in (révision
-by: Emmanuel Deloget log...@free.fr
Index: toolchain/eglibc/Config.version
===
--- toolchain/eglibc/Config.version (révision 31444)
+++ toolchain/eglibc/Config.version (copie de travail)
@@ -4,4 +4,4 @@
default 2.12.2
implementation in
Linux [2][3].
Sorry for the derailing. That were my 2 cents, you are free to discard
those arguments (or to mock them, if you feel you must do that :)).
Best regards,
-- Emmanuel Deloget
[1] https://www.google.fr/search?q=zigbee+soc
[2] http://lwn.net/Articles/452293/
[3] http
++ 4.7 refuses to compile a code that is
seemingly fine (although the specific error makes sense for the
C++ folks ; stuff about dependant type lookup is always very
dependant on the compiler and ameliorations in compilers may
very often break code in these areas).
Best regards,
-- Emmanuel
for the noise then...
-- Emmanuel Deloget
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
-SDP, OMAP4-Blaze, ...) may later be added if
needed.
Signed-off-by: Emmanuel Deloget log...@free.fr
Index: target/linux/omap4/pandaboard/config-default
===
--- target/linux/omap4/pandaboard/config-default(révision 0)
+++ target
.
Since libroxml is not yet in the OpenWRT package tree, it's not
yet possible to select this XML backend.
Signed-off-by: Emmanuel Deloget log...@free.fr
Index: packages/utils/klish/Config.in
===
--- packages/utils/klish/Config.in
Le 07/07/2012 09:13, Luka Perkov a écrit :
On Fri, Jun 29, 2012 at 06:06:17PM +0200, Emmanuel Deloget wrote:
Bump klish version to 1.6.0.
You should use buildvariants for this. Take a look at freecwmp:
packages/utils/freecwmp/Makefile
I will give a look to this in the next hours/days
maintainers) choices are, we're
going to accept and support them. But it might be good to at
least publish some kind of rationale document when a new
kernel is pushed in the tree.
Hoping I have not been too disruptive, best regard,
-- Emmanuel Deloget
[1] http://www.kroah.com/log/linux/stable
/2012
3.8: probable -longterm support by GKH, will be released on 08/??/2013
(roughly ; there is a delay of 4-5 month between two subsequent kernel
versions).
Best regards,
-- Emmanuel Deloget
___
openwrt-devel mailing list
openwrt-devel
Hello,
On 17/01/2014 19:27, Oskari Rauta wrote:
Hi.
I previously provided a patch for OpenWrt that enabled use of kernel 3.12.2y
which is a raspberry pi specific kernel.
Patch was a huge blob, 8 megabytes and was not integrated to mainstream. What
that patch did, was that it converted
)_ENABLE_SMALL),--enable-small)
Best regards,
-- Emmanuel Deloget
attachment: emmanuel_deloget.vcf___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
after the module it depends on.
* is insmoded before the modules that depends on it.
Once you added the correct lines, you can do another make menuconfig -
and your module will show up.
Best regards,
-- Emmanuel Deloget
___
openwrt-devel mailing list
a tiny one), fast, exists as a library, is
ACID-compliant, supports triggers and so on. It's C interface is both simple
and powerfull.
Thanks in advance,
Pietro.
Best regards,
-- Emmanuel Deloget
___
openwrt-devel mailing list
openwrt-devel
On 04/28/2011 12:49 PM, John Zavgren wrote:
Emmanuel:
Thanks for getting back to me on this issue. I haven't tried your
suggestions yet, however, I wonder why similar packages that don't
have the modifications you recommend seem to work they way I expect
them to.
For example, the package
(for
instance, upx).
It's now the time to write down a few questions :
+ Do you think that a configurable strip target (for example
Package/X/strip, which defaults to Package/strip/Default) makes sense ?
+ Do you have any other idea ?
Best regards,
-- Emmanuel Deloget
[1] https://dev.openwrt.org
to
package maintainers?
~ Jow
Best regards,
-- Emmanuel Deloget
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
On 06/17/2011 04:39 PM, Pawel Pastuszak wrote:
Hi gents,
I getting an hotplug complie error after i compiled the gcc 4.4.5
toolcahin with glibc 2.6.1, please not this is a trunk check out
PS. I am using Ubuntu 10.10.
snip
udevtrigger.c:(.text+0x538): undefined reference to `strlcpy'
kernel_xconfig only
if Patch 3/4 has been applied (both patch are modifying the same file,
and Patch 4/4 builds upon the tools that are added with Patch 3/4).
The patches with svn diff on svn://svn.openwrt.org/openwrt/trunk.
Best regards,
-- Emmanuel Deloget
.
Signed-off-by: Emmanuel Deloget emmanuel.delo...@efixo.com
(Warning)
Please note that this patch does not apply cleanly, although it applies.
I get the following warning (after I applied patches 1/4 to 3/4):
patching file include/toplevel.mk
Hunk #1 succeeded at 129 (offset 22 lines
several important makefiles
have been added back.
Best regards,
-- Emmanuel Deloget
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
This patch modifies the scripts/config/Makefile file to build the qconf
utility. qconf is not added to the target list unless the development
files of qt3 has been detected (we simply check for the presence of
the /usr/include/qt3 directory).
Signed-off-by: Emmanuel Deloget emmanuel.delo
-by: Emmanuel Deloget emmanuel.delo...@efixo.com
---
Changes since version 1:
* none
---
Index: include/toplevel.mk
===
--- include/toplevel.mk (revision 27257)
+++ include/toplevel.mk (working copy)
@@ -43,6 +43,8 @@
SUBMAKE:=umask
.
Signed-off-by: Emmanuel Deloget emmanuel.delo...@efixo.com
(Warning)
Please note that this patch does not apply cleanly, although it applies.
I get the following warning (after I applied patches 1/4 to 3/4):
patching file include/toplevel.mk
Hunk #1 succeeded at 129 (offset 22 lines).
patching
On 08/17/2011 12:21 AM, Hartmut Knaack wrote:
Hi Hauke,
sorry for snatching in.
If you need some kernel module do make menuconfig and select it if it
is there or add a module to packages/kernel/modules/.
Hauke
So what would be the most convenient way to submit changes (i.e.
patches) in
depends on the package).
So, honnest mistake or design choice? (i.e. what should I do with this
report?)
Best regards,
--
Emmanuel Deloget
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt
Le 29/08/2011 06:55, Philip Prindeville a écrit :
The name gpio-cs5535 used to refer to the drivers/char/ module, but in 3.1 it
refers to what had been drivers/gpio/cs5535-gpio in more recent kernels.
Have you checked on Linux 3.0 ? It seems to me that many drivers have
been moved (serial
patches - and not the patches in
PATCH_DIR (since this variable depends on the package).
So, honnest mistake or design choice? (i.e. what should I do with this
report?)
Best regards,
--
Emmanuel Deloget
___
openwrt-devel mailing list
openwrt-devel
as I can tell. With tabs, variable
definitions are not highlighted correctly (they are when 2 spaces are
used).
-- Emmanuel Deloget
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Le 03/10/2011 15:32, Florian Fainelli a écrit :
Hello,
Hi Florian,
On Thursday 23 June 2011 10:42:31 Emmanuel Deloget wrote:
This patchset brings back the support for the xconfig (and the
corresponding kernel_xconfig) top-level targets. Since these targets
depends on qt3 (and more precisely
Le 03/10/2011 15:32, Florian Fainelli a écrit :
Hello,
On Thursday 23 June 2011 10:42:31 Emmanuel Deloget wrote:
snip
Patch 1/4 to 3/4 in the series are necessary to add support for
make xconfig. Patch 4/4 will add support for make kernel_xconfig only
if Patch 3/4 has been applied (both patch
removed, and the series is now made of 3 patches
1/3, 2/3 and 3/3.
* patch 2/3 has been corrected (added a missing rule)
---
Changes since version 1:
* in Patch 4/4: the missing changes from several important makefiles
have been added back.
Best regards,
-- Emmanuel Deloget
the missing .moc file
Changes since Version 1: none
Signed-off-by: Emmanuel Deloget emmanuel.delo...@efixo.com
--
Index: scripts/config/Makefile
===
--- scripts/config/Makefile(révision 28361)
+++ scripts/config/Makefile(copie de
-by: Emmanuel Deloget emmanuel.delo...@efixo.com
--
Index: include/toplevel.mk
===
--- include/toplevel.mk(révision 28361)
+++ include/toplevel.mk(copie de travail)
@@ -43,6 +43,8 @@
SUBMAKE:=umask 022; $(SUBMAKE)
+have-qt3
/page__pid__31768__st__50#entry31768
Greetings.
--8
Best regards,
-- Emmanuel Deloget
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman
This patch reorders the functions sym_set_changed() and sym_set_all_changed()
to place them before sym_calc_value() where the later is used in order to avoid
a symbol redefinition warning.
Signed-off-by: Emmanuel Deloget log...@free.fr
Index: scripts/config/symbol.c
have been added back.
Best regards,
--
Emmanuel Deloget
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
This patch modifies the scripts/config/Makefile file to build the qconf
utility.
qconf is not added to the target list unless the development files of
qt3 has been detected (we simply check for the presence of the
/usr/include/qt3 directory).
Signed-off-by: Emmanuel Deloget emmanuel.delo
-by: Emmanuel Deloget emmanuel.delo...@efixo.com
Index: include/toplevel.mk
===
--- include/toplevel.mk (révision 28798)
+++ include/toplevel.mk (copie de travail)
@@ -43,6 +43,8 @@
SUBMAKE:=umask 022; $(SUBMAKE)
+have-qt3-dev
not on
the platform. This is not a problem - it might be built a bit earlier but
it's still built only once.
Cldt,
-- Emmanuel Deloget
--
Change the order in which package dependencies are considered while
building the packages
Le 12/15/2011 07:15 PM, Nico a écrit :
Hi,
On Thu, Dec 15, 2011 at 5:51 PM, Emmanuel Deloget
emmanuel.delo...@efixo.com wrote:
Hi everybody,
I recently faced an issue related to package dependencies that drove me
nuts. Consider the following case :
* I manage different platforms (let's
When we create the /bin/tar in $(IPKG_INSTROOT) link we want it to point to
/usr/bin/tar, and not to $(IPKG_INSTROOT)/usr/bin/tar as $(IPKG_INSTROOT)
is certainly not a valid path on the built rootfs.
Signed-off-by: Emmanuel Deloget log...@free.fr
Index: packages/utils/tar/Makefile
Le 01/24/2012 02:06 PM, Jonathan McCrohan a écrit :
On 24/01/12 08:22, Dave Taht wrote:
My principal critique of this workflow is that I tend to view svn as part
of the problem to a large extent. If I do a patch in my own (git) tree
to test with, I invariably have to rebase that tree when it
Hello,On this particular case, a gcc bug report exists because this specific warning should not show when no other diagnostics are issued. I can't link to the exact report right now but a simple google search should show it. IIRC gcc-4.7 may behave more correctly.So the correct treatment is either
is a dependency of another package).
Signed-off-by: Emmanuel Deloget log...@free.fr
Index: packages/net/lighttpd/Makefile
===
--- packages/net/lighttpd/Makefile (révision 30750)
+++ packages/net/lighttpd/Makefile (copie de travail)
@@ -9,7
these kernel_*config rules
have this $(_SINGLE) here?
* is there a way to have these CONFIG_* command line variables
correctly honored in this specific case?
* is this even legal (from an OpenWRT point of view)?
Best regards,
-- Emmanuel Deloget
kernel_oldconfig
and so on...
When used, they generate build errors because the kernel_*config targets
are not able to find the correct directories.
Signed-off-by: Emmanuel Deloget emman...@deloget.com
---
include/toplevel.mk | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/include
You should try Aliexpress - it seems they still have some 4900 (be aware
that prices might be a bit weird).
I also found one company in France that can sell it (integration-reseaux.com
).
BR,
-- Emmanuel Deloget
On Wed, Jul 1, 2015 at 9:00 PM, Bastian Bittorf bitt...@bluebottle.com
wrote
Hello,
Same here - this is really appreciated.
BR,
-- Emmanuel Deloget
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
anies uses to build firmwares for their consumer
products (we
do that at SFR on the 9box). Following and integrating OpenWRT changes is part
of my day to day job, and I must admit that a correct git repository - with the
corresponding tagged releases and branches are present - would be immensly
helpful.
BR,
-- Emmanuel Deloget
(P.S. this mail represent my personnal views, not the view of my employer).
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
ion, allowing the
developers to spend their time on the project itself - and not on the
maintenance of a foundation.
> Federico
>
BR,
-- Emmanuel Deloget
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
66 matches
Mail list logo
