Re: [OpenWrt-Devel] [PATCH] network/utils/dante: Fix wrong md5sum for download
Hey all,
Last update to v1.4.1 did not update MD5SUM. Fixed in r48017.
Cheers,
--
-{Nico}
On Thu, Dec 17, 2015 at 11:14 PM, Lars <la...@systemli.org> wrote:
> hey,
>
> as with previous occasions of hashsum mismatches: why does it mismatch?
>
> cheers,
> lars
>
> On 17.12.2015 22:51, open...@daniel.thecshore.com wrote:
>> From: Daniel Dickinson <open...@daniel.thecshore.com>
>>
>> The md5sum in the Makefile doesn't match md5sum
>> of downloaded package which causes failure of builds
>> due to failure to get a successful download.
>> ---
>> package/network/utils/dante/Makefile | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/package/network/utils/dante/Makefile
>> b/package/network/utils/dante/Makefile
>> index b49ae72..ab05f8c 100644
>> --- a/package/network/utils/dante/Makefile
>> +++ b/package/network/utils/dante/Makefile
>> @@ -13,7 +13,7 @@ PKG_RELEASE:=1
>>
>> PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.gz
>> PKG_SOURCE_URL:=http://www.inet.no/dante/files/
>> -PKG_MD5SUM:=69b9d6234154d7d6a91fcbd98c68e62a
>> +PKG_MD5SUM:=68c2ce12119e12cea11a90c7a80efa8f
>>
>> PKG_MAINTAINER:=Jo-Philipp Wich <j...@openwrt.org>
>> PKG_LICENSE:=BSD-4-Clause
>>
>
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
>
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] uml: fix mac80211 hwim for uml
On Wed, Jun 24, 2015 at 1:45 AM, Martin Tippmann
martin.tippm...@gmail.com wrote:
A duplicate include guard prevents inclusion of barrier.h in UML build and
this prevents mac80211 from building.
This patch re-enables mac80211 hwsim and renames the include guard.
See https://lists.openwrt.org/pipermail/openwrt-devel/2015-June/033614.html
for details.
Signed-off-by: Martin Tippmann martin.tippm...@gmail.com
Applied (with a minor correction) in r46133!
Thanks,
--
-{Nico}
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] dosfstools: update to latest version
Hi Álvaro,
On Mon, Mar 16, 2015 at 5:26 PM, Álvaro Fernández Rojas
nolt...@gmail.com wrote:
update OS X patches to latest sent upstream
also fixes patch breakage due to different git revision
Any reason you're not using the release tarballs :
https://github.com/dosfstools/dosfstools/releases
Cheers,
--
-{Nico}
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] util-linux: fix pkgconfig files
On Sun, Mar 8, 2015 at 10:51 PM, Dirk Neukirchen dirkneukirc...@web.de wrote:
fixes a bug when other packages want to include libuuid
or other libs with pkgconfig they will use host paths
leading to unexpected build results
Thanks for reporting this issue! It was fixed in r44627, I chose to
patch it so that it could be pushed upstream.
Cheers,
--
-{Nico}
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [RFC] + [PATCH, V1] Reorder package dependencies
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 say platform1 and platform2)
* On platform1, packageX depends on pkgdep, which should be autoselected
when I select packageX.
* On platform2, packageX also depends on pkgdep, which should be
autoselected when I select packageX.
* On all other platforms, packageX shall not depends on anything.
The current solution is to handle that using the package dependencies
define Package/packageX
TITLE:=PackageX
MAINTAINER:=me
SECTIONS:=utils
CATEGORY:=Utils
URL:=http://somewhere/
DEPENDS:=+TARGET_platform1:pkgdep +TARGET_platform2:pkgdep
endef
Have you tried the following?
DEPENDS:=+(TARGET_platform1||TARGET_platform2):pkgdep
--
-{Nico}
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] bluez-utils build failure
Applied in r29523
Thanks,
--
-{Nico}
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] FFmpeg 0.8.7 version bump
Applied in r29525
Thanks,
--
-{Nico}
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] rsync 3.0.9 version bump
Applied in r29526
Thanks,
--
-{Nico}
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] correct description for libdbi
Applied in r29529 - without the release bump ;)
Thanks,
--
{Nico}
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] New package PyRRD
Added in r29402 with a different patch to allow building with distribute
Thanks,
--
-{Nico}
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] combined extended image
Added in r29358, with minor modifications
Thanks,
--
-{Nico}
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] New package PyRRD
Hi Roberto,
On Fri, Nov 25, 2011 at 2:09 PM, Roberto Riggio
roberto.rig...@create-net.org wrote:
On 11/15/2011 01:19 AM, Nico wrote:
Hi Roberto,
Hi,
On Mon, Oct 10, 2011 at 11:18 AM, Roberto Riggio
roberto.rig...@create-net.org wrote:
This patch is a port of the PyRRD package to openwrt. PyRRD is a wrapper
for
rrdtool for python. The API is so much better than the python bindings
for
rrd.
Signed-off-by: Roberto Riggioroberto.rig...@create-net.org
Is the patch adding ez-setup.py really needed? It is building fine
here without it.
without i get this:
Traceback (most recent call last):
File ./setup.py, line 1, in module
from setuptools import setup
ImportError: No module named setuptools
Try installing the distribute package, we can add that as a BUILD_DEPENDS.
Cheers,
--
-{Nico}
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] OpenSSL variant and init script for ngIRCd package
Hi Jiri the List,
Can you update the initscript to use the service_start service_stop
functions instead of start-stop-daemon ? You can find some doc in
/lib/functions.sh and usage in initscripts from other packages.
Thanks,
--
-{Nico}
On Thu, Nov 24, 2011 at 8:35 AM, Jiří Machálek machal...@gmail.com wrote:
This patch adds variant of IRC server ngIRCd package compiled with
OpenSSL support and init script.
Signed-off-by: Jiri Machalek machal...@gmail.com
---
Index: packages/net/ngircd/files/ngircd.init
===
--- packages/net/ngircd/files/ngircd.init (revision 0)
+++ packages/net/ngircd/files/ngircd.init (revision 0)
@@ -0,0 +1,13 @@
+#!/bin/sh /etc/rc.common
+#Copyright (c) 2011 Jiri Machalek machal...@gmail.com
+
+START=62
+APP=ngircd
+
+start () {
+ start-stop-daemon -S -x $APP
+}
+
+stop () {
+ start-stop-daemon -K -n $APP -s TERM
+}
Property changes on: packages/net/ngircd/files/ngircd.init
___
Added: svn:executable
+ *
Index: packages/net/ngircd/Makefile
===
--- packages/net/ngircd/Makefile (revision 29290)
+++ packages/net/ngircd/Makefile (working copy)
@@ -8,28 +8,44 @@
include $(TOPDIR)/rules.mk
PKG_NAME:=ngircd
-PKG_VERSION:=15
-PKG_RELEASE:=2
+PKG_VERSION:=18
+PKG_RELEASE:=1
PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.gz
PKG_SOURCE_URL:= \
ftp://ngircd.barton.de/pub/ngircd/ \
ftp://ftp.berlios.de/pub/ngircd/
-PKG_MD5SUM:=c183a85eba6fe51255983848f099c8ae
+PKG_MD5SUM:=4958c8b2d128cf3e9888af3f782892a1
PKG_INSTALL:=1
+PKG_BUILD_DIR:=$(BUILD_DIR)/$(PKG_NAME)-$(BUILD_VARIANT)/$(PKG_NAME)-$(PKG_VERSION)
+
include $(INCLUDE_DIR)/package.mk
+NGIRCD_DEPENDS:=+zlib
-define Package/ngircd
+define Package/ngircd/default
SECTION:=net
CATEGORY:=Network
SUBMENU:=Instant Messaging
- DEPENDS:=+zlib
- TITLE:=Next Generation IRC Server
URL:=http://ngircd.barton.de
endef
+
+define Package/ngircd
+$(call Package/ngircd/default)
+ DEPENDS:=$(NGIRCD_DEPENDS)
+ VARIANT:=nossl
+ TITLE:=Next Generation IRC Server
+endef
+
+define Package/ngircd-openssl
+$(call Package/ngircd/default)
+ DEPENDS:=$(NGIRCD_DEPENDS) +libopenssl
+ VARIANT:=ssl
+ TITLE:=Next Generation IRC Server (with OpenSSL support)
+endef
+
define Package/ngircd/description
ngIRCd is an Open Source server for the Internet Relay Chat (IRC), which
is developed and published under the terms of the GNU General Public
Licence.
@@ -37,15 +53,42 @@
not deduced from the grandfather of IRC daemons, the daemon of the
IRCNet.
endef
+define Package/ngircd-openssl/description
+ ngIRCd is an Open Source server for the Internet Relay Chat (IRC), which
+ is developed and published under the terms of the GNU General Public
Licence.
+ ngIRCd means next generation IRC daemon, it's written from scratch and
+ not deduced from the grandfather of IRC daemons, the daemon of the
IRCNet.
+endef
+
define Package/ngircd/conffiles
/etc/ngircd.conf
endef
+define Package/ngircd-openssl/conffiles
+/etc/ngircd.conf
+endef
+
+ifeq ($(BUILD_VARIANT),ssl)
+ CONFIGURE_ARGS += --with-openssl
+endif
+
define Package/ngircd/install
$(INSTALL_DIR) $(1)/usr/sbin
$(INSTALL_BIN) $(PKG_INSTALL_DIR)/usr/sbin/ngircd $(1)/usr/sbin/
$(INSTALL_DIR) $(1)/etc
$(INSTALL_CONF) $(PKG_INSTALL_DIR)/etc/ngircd.conf $(1)/etc/
+ $(INSTALL_DIR) $(1)/etc/init.d
+ $(INSTALL_BIN) ./files/ngircd.init $(1)/etc/init.d/ngircd
endef
+define Package/ngircd-openssl/install
+ $(INSTALL_DIR) $(1)/usr/sbin
+ $(INSTALL_BIN) $(PKG_INSTALL_DIR)/usr/sbin/ngircd $(1)/usr/sbin/
+ $(INSTALL_DIR) $(1)/etc
+ $(INSTALL_CONF) $(PKG_INSTALL_DIR)/etc/ngircd.conf $(1)/etc/
+ $(INSTALL_DIR) $(1)/etc/init.d
+ $(INSTALL_BIN) ./files/ngircd.init $(1)/etc/init.d/ngircd
+endef
+
$(eval $(call BuildPackage,ngircd))
+$(eval $(call BuildPackage,ngircd-openssl))
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] dnsmasq: update to 2.59 and use PKG_INSTALL
Hi Raphaël the List,
2011/10/27 Raphaël HUCK r...@cksum.org:
Hi all,
this patch updates dnsmasq to 2.59 and makes use of PKG_INSTALL.
Applied in r29329
Thanks,
--
-{Nico}
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] [packages] libupnp: Fix samples install and simplify Makefile
Hi John,
On Mon, Nov 21, 2011 at 11:12 AM, John Lee john.cy...@gmail.com wrote:
The original Makefile installed libtool wrapper scripts instead of the
real binaries. Increase PKG_RELEASE to trigger rebuild.
Signed-off-by: John Lee john.cy...@gmail.com
---
libs/libupnp/Makefile | 34 +++---
1 files changed, 3 insertions(+), 31 deletions(-)
diff --git a/libs/libupnp/Makefile b/libs/libupnp/Makefile
index 83bdb5e..904540d 100644
--- a/libs/libupnp/Makefile
+++ b/libs/libupnp/Makefile
@@ -9,7 +9,7 @@ include $(TOPDIR)/rules.mk
PKG_NAME:=libupnp
PKG_VERSION:=1.6.12
-PKG_RELEASE:=1
+PKG_RELEASE:=2
PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.bz2
PKG_SOURCE_URL:=@SF/pupnp
@@ -50,33 +50,6 @@ define Package/libupnp-sample/description
TVcontrolpoint tvdevice sample applications run inside /etc/upnp-tvdevice/
endef
-define Build/Configure
- $(call Build/Configure/Default, \
- --enable-shared \
- --enable-static \
- );
-endef
-
-TARGET_CFLAGS += $(FPIC)
-
-define Build/Compile/libupnp-sample
- $(MAKE) -C $(PKG_BUILD_DIR) \
- DESTDIR=$(PKG_INSTALL_DIR) \
- check
- $(MAKE) -C $(PKG_BUILD_DIR)/upnp/sample \
- DESTDIR=$(PKG_INSTALL_DIR) \
- upnp_tv_device upnp_tv_ctrlpt
-endef
-
-define Build/InstallDev
- $(INSTALL_DIR) $(1)/usr/include
- $(CP) $(PKG_INSTALL_DIR)/usr/include/upnp $(1)/usr/include/
- $(INSTALL_DIR) $(1)/usr/lib
- $(CP) $(PKG_INSTALL_DIR)/usr/lib/lib{ixml,threadutil,upnp}.{a,so*,la}
$(1)/usr/lib/
- $(INSTALL_DIR) $(1)/usr/lib/pkgconfig
- $(CP) $(PKG_INSTALL_DIR)/usr/lib/pkgconfig/libupnp.pc
$(1)/usr/lib/pkgconfig/
-endef
-
define Package/libupnp/install
$(INSTALL_DIR) $(1)/usr/lib
$(CP) $(PKG_INSTALL_DIR)/usr/lib/lib{ixml,threadutil,upnp}.so.*
$(1)/usr/lib/
@@ -84,10 +57,9 @@ endef
define Package/libupnp-sample/install
$(INSTALL_DIR) $(1)/usr/bin
- $(INSTALL_BIN) $(PKG_BUILD_DIR)/upnp/sample/tv_device $(1)/usr/bin
- $(INSTALL_BIN) $(PKG_BUILD_DIR)/upnp/sample/tv_ctrlpt $(1)/usr/bin
+ $(INSTALL_BIN) $(PKG_BUILD_DIR)/upnp/sample/.libs/* $(1)/usr/bin
$(INSTALL_DIR) $(1)/etc/upnp-tvdevice/web
- $(CP) $(PKG_BUILD_DIR)/upnp/sample/web/* $(1)/etc/upnp-tvdevice
+ $(INSTALL_DATA) $(PKG_BUILD_DIR)/upnp/sample/web/*
$(1)/etc/upnp-tvdevice
endef
$(eval $(call BuildPackage,libupnp))
--
1.7.4.1
Humm, that might be too much cleaning actually. Why are you removing
Build/InstallDev ? AFAIK, libupnp is still used by others packages...
--
-{Nico}
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] Provide a global section_enabled function
Hi Michael the List,
On Sat, Nov 19, 2011 at 9:43 PM, Michael Heimpold m...@heimpold.de wrote:
Since various packages implement such a function already on their own,
it seems reasonable to provide this a globally available function.
Yeah, it's on my todo with a couple of other functions, like
append_bool, append_string and the like...
Thanks,
--
-{Nico}
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] uci-12012009.7.tar.gz
Hi Mike,
The missing file was just uploaded to downloads.openwrt.org [1].
1. http://downloads.openwrt.org/sources/uci-12012009.7.tar.gz
--
-{Nico}
On Wed, Nov 16, 2011 at 9:43 PM, Mike Brady mikebr...@eircom.net wrote:
Just building backfire now, and it can't find uci-12012009.7.tar.gz.
--2011-11-16 20:37:23--
http://mirror2.openwrt.org/sources/uci-12012009.7.tar.gz
Resolving mirror2.openwrt.org... 46.4.11.11
Connecting to mirror2.openwrt.org|46.4.11.11|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2011-11-16 20:37:23 ERROR 404: Not Found.
Download failed.
--2011-11-16 20:37:23--
http://downloads.openwrt.org/sources/uci-12012009.7.tar.gz
Resolving downloads.openwrt.org... 78.24.191.177
Connecting to downloads.openwrt.org|78.24.191.177|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2011-11-16 20:37:23 ERROR 404: Not Found.
Shome mhistake?
Kind regards
Mike
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] mini_snmpd uci network interfaces support
Hi,
The 'disks' 'interfaces' options were changed to lists in r29182.
The 'interfaces' list option is now using names as defined in
/etc/config/network.
Cheers,
--
-{Nico}
On Mon, Nov 14, 2011 at 11:11 PM, ZioPRoTo (Saverio Proto)
ziopr...@gmail.com wrote:
Hello Nico,
I tested and reworked Gioacchino's mini_snmpd patch to support uci
interfaces names instead of real interface names.
please check and commit. I would commit myself but I do not have
permission for that folder
ciao :)
Saverio
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCHv2] [packages] tinc: Add uci config and init files
Patch looks good and works, i'd like to see this getting submitted.
Applied in r29137, initscript was changed in r29166 to use new service
functions.
--
-{Nico}
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] tor init script is broken
Hi Peter the List,
On Tue, Nov 15, 2011 at 2:40 AM, Peter Wagner tripo...@gmx.at wrote:
Hi,
the current tor init script that uses the new service wrapper is broken.
It is working fine here. From our discussion on IRC, I suspect your
issue was related to a free space problem on /tmp.
Anyway, looking at your patch, I thought it might me good to have tor
its initscript share the same idea of what the pid-file is (patch
enclosed)
What do you think ?
Cheers,
--
-{Nico}
From 244bc13134ed5de5e6c727b7a2435ceb47ef3fc9 Mon Sep 17 00:00:00 2001
From: nico n...@openwrt.org
Date: Tue, 15 Nov 2011 22:41:32 +0100
Subject: [PATCH] packages/tor: use pid-file from tor config-file
Signed-off-by: nico n...@openwrt.org
---
net/tor/Makefile |2 +-
net/tor/files/tor.init |9 -
2 files changed, 9 insertions(+), 2 deletions(-)
diff --git a/net/tor/Makefile b/net/tor/Makefile
index b1dc173..10afb50 100644
--- a/net/tor/Makefile
+++ b/net/tor/Makefile
@@ -9,7 +9,7 @@ include $(TOPDIR)/rules.mk
PKG_NAME:=tor
PKG_VERSION:=0.2.2.34
-PKG_RELEASE:=2
+PKG_RELEASE:=3
PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.gz
PKG_SOURCE_URL:=https://www.torproject.org/dist \
diff --git a/net/tor/files/tor.init b/net/tor/files/tor.init
index 42eff1a..6b8a1bf 100644
--- a/net/tor/files/tor.init
+++ b/net/tor/files/tor.init
@@ -3,7 +3,12 @@
START=50
-SERVICE_PID_FILE=/var/run/tor/tor.pid
+SERVICE_USE_PID=1
+
+lookup_pid_file() {
+ local f=$(cat /etc/tor/torrc |grep '^PidFile' |awk '{ print $2; }' 2/dev/null)
+ SERVICE_PID_FILE=${f:-/var/run/tor/tor.pid}
+}
start() {
user_exists tor 52 || user_add tor 52
@@ -21,9 +26,11 @@ start() {
mkdir -m 0755 -p /var/log/tor
chown tor:tor /var/log/tor
}
+ lookup_pid_file
service_start /usr/sbin/tor
}
stop() {
+ lookup_pid_file
service_stop /usr/sbin/tor
}
--
1.7.0.4
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] tor init script is broken
On Tue, Nov 15, 2011 at 11:46 PM, Peter Wagner tripo...@gmx.at wrote:
Hi {Nico} and the List,
i think this is a good idea. But some other things i would change too. The
default homefolder of tor is /var/lib/tor (tor creates only files in this
folder) so the homedir in /etc/passwd should be changed to that directory too.
And as every program creates a pid in /var/run without subfolders the touch
chown approch of a file is much nicer - imho. Also if a user would change the
the pid to /var/run/tor.pid in torrc tor would still not start. As the folder
is allready there it wouldnt be created and tor has no write previleges to
write into this folder. (if you use my updates patch - tor_v1.patch)
I think tor should create a pid in /var/run without a subfolder and setting
the --PidFile option that is also needed with your updated approach (see
tor_v1.patch). i would still prefer v2 patch as it ignores the value of torrc
and just creates a file in /var/run. it is simpler and as nearly no user cares
about the pid file it even uses less memory as no dir is created ;) and the
init file is much smaller and simpler.
I would perfer that tor gets stopped on shutdown because when extroot is used
it will result in an unclean umounted fs.
What do you think? :)
Sold :)
I'll add a note in the config-file stating the pid-file location is fixed
--
-{Nico}
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] add entry in /etc/shadow when user_add is used v2
Hi Peter,
A single lock for both /etc/passwd and /etc/shadow should be enough,
it was just there to prevent multiple initscripts from messing with
/etc/passwd at boot.
--
-{Nico}
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] New package PyRRD
Hi Roberto,
On Mon, Oct 10, 2011 at 11:18 AM, Roberto Riggio
roberto.rig...@create-net.org wrote:
This patch is a port of the PyRRD package to openwrt. PyRRD is a wrapper for
rrdtool for python. The API is so much better than the python bindings for
rrd.
Signed-off-by: Roberto Riggio roberto.rig...@create-net.org
Is the patch adding ez-setup.py really needed? It is building fine
here without it.
(Sorry for the loong delay in handling this)
--
-{Nico}
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] privoxy use new service wrapper
Applied in r29151
Thanks,
--
-{Nico}
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Avahi package problems
Hi,
On Tue, Nov 8, 2011 at 6:46 PM, Mike Brady mikebr...@eircom.net wrote:
Hi Jon. Thanks for the pointers. Yeah, I was a tiny bit surprised to hear
nothing. I didn't know how to contact the committers, TBH. Are you a
maintainer yourself?
I will try to fix it. From your experience, can you remind me which
binaries are needing DBUS enabled and which don't care ?
Thanks for your detailed explanation and your help,
--
-{Nico}
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] Create PID file for xinetd
2011/11/3 Stefan Agner ste...@agner.ch:
Create a pid file by default when starting xinetd (resolves #10342).
Signed-off-by: Stefan Agner ste...@agner.ch
Applied in r28748.
Thanks,
--
-{Nico}
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] packages freeradius2 fix some dependencies
On Fri, Nov 4, 2011 at 8:11 AM, lynxis lyn...@c-base.org wrote:
freeradius2: fix some dependencies
Signed-off-by: Alexander Couzens lyn...@c-base.org
Applied (with minor modifications) in r28752.
Thanks,
--
-{Nico}
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] upgrade baresip, restund, libre, librem to version 0.3.0
On Mon, Oct 31, 2011 at 10:01 PM, Alfred E. Heggestad a...@db.org wrote:
Hi,
(Resend, updated patch)
this patch upgrades the following packages to v0.3.0:
baresip v0.3.0 (Portable and modular SIP User-Agent with audio and video
support)
restund v0.3.0 (Modular STUN/TURN server)
libre v0.3.0 (Generic library for real-time communications with async IO
support)
librem v0.3.0 (Audio and video processing media library)
detailed changes can be found in package/docs/ChangeLog
(See http://www.creytiv.com/)
I have also removed the @BROKEN symbol, as all packages build fine here with
trunk r28297 for at least BRCM, AR7, x86 and UML architectures. I read on
the forum
that there was some problems building the programs but I did not find any
reports
on which architectures were failing or any build logs. would it be possible
to
get notified somehow if such a thing happens ?
Thanks to Jonas Gorski and Jo-Philipp Wich for valuable feedback on the
first patch
Please review and apply if OK.
Signed-Off-By: Alfred E. Heggestad
Applied in r28754-r28757 with the following modifications :
- add patches to avoid looking for host files in /usr/include,
/usr/local, etc...
- make baresip restund modular by packaging plugins
- use start-stop-daemon in baresip restund initscripts
Thanks,
--
-{Nico}
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] openl2tp - finally enable config file option
On Mon, Oct 17, 2011 at 7:34 PM, Bogdan Roman ab...@cam.ac.uk wrote:
Until now the openl2tpg package only allowed configuration through RPC by
using the l2tpconfig command, making many some tasks difficult. Discussion
exists at https://dev.openwrt.org/ticket/10164 . Enabling the config file
option requires working around the flex library ( (libfl) and a few compile
fixes. The following 2 patches enable the config file option in addition to
the RPC option. Tested against trunk r28428. Note that the openwrt openl2tp
package is still not fully finished, e.g. a proper init.d script and sample
conf files should be included, see build_dir/*/openl2tp-1.8/{etc,ipsec}/*. I
may sort that out as well later.
Signed-off-by: Bogdan Roman ab...@cam.ac.uk
Applied in r28758. As suggested by Eric, the package was also split in
2 variants:
- mini: only configuration file support
- full: configuration file and RPC support
I'm not sure what plugins are needed for each and what a sample
configuration would look like, feel free to submit more patches :)
Thanks,
--
-{Nico}
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] openl2tp - finally enable config file option
On Sat, Nov 5, 2011 at 12:40 AM, Nico n...@openwrt.org wrote:
I'm not sure what plugins are needed for each and what a sample
configuration would look like, feel free to submit more patches :)
I found some sample configuration files [1] from gentoo, if someone
want to start working on it...
1.
http://git.overlays.gentoo.org/gitweb/?p=user/bircoph.git;a=tree;f=net-dialup/openl2tp/files/examples
--
-{Nico}
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] pcre: update to 8.20
Hi Raphael,
Thanks for the update, but...
- don't update PKG_SOURCE_URL, the latest version is still available on SF
- if you want libpcrecpp to get built only if Advanced configuration
options (for developers) menuconfig option is set, just add a
dependency on @DEVEL to libpcrecpp
--
-{Nico}
2011/11/2 Raphaël HUCK r...@cksum.org:
Hi all,
this patch:
* updates pcre to 8.20
* updates PKG_SOURCE_URL
* fixes building libpcrecpp when DEVELOPER=1
Thanks,
-Raphaël
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] bison: update to 2.5
Hi Raphael,
I will handle it, it's on my batch of proposed updates [1].
1.
http://git.nico-and-co.net/?p=nico/openwrt.git;a=shortlog;h=refs/heads/proposed-updates
Thanks,
--
-{Nico}
2011/11/3 Raphaël HUCK r...@cksum.org:
Hi all,
this patch updates bison to 2.5.
Thanks!
-Raphaël
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] libpng: update to 1.2.46
Applied in r28740.
Thanks,
--
-{Nico}
2011/11/3 Raphaël HUCK r...@cksum.org:
Hi all,
this patch updates libpng to 1.2.46.
From the changelog:
*Fixed uninitialized memory read in png_format_buffer() (Bug
report by Frank Busse, related to CVE-2004-0421).
* Pass instead of '\0' to png_default_error() in png_err(). This
mistake was introduced in libpng-1.2.20beta01.
* Check for up-location !PNG_AFTER_IDAT when writing unknown chunks
before IDAT.
* Ported bugfix in pngrtran.c from 1.5.3: when expanding a paletted
image, always expand to RGBA if transparency is present.
* Check for integer overflow in png_set_rgb_to_gray().
Thanks!
-Raphaël
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] libevent 2.0.15 update patch - fixes tor compile error
Applied in r28741
Thanks,
--
-{Nico}
On Wed, Oct 26, 2011 at 5:02 PM, Peter Wagner tripo...@gmx.at wrote:
libevent 2.0.15 update patch - fixes tor compile error
Signed-off-by: Peter Wagner tripo...@gmx.at
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] tor 0.2.2.34 update patch
Applied in r28742
Thanks,
--
-{Nico}
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] combined extended image
Hi Marek,
I would suggest adding some kind of version field (2 bytes, value 01
or 10) just after the magic and bumping file names to 32 bytes as
well.
--
-{Nico}
On Wed, Nov 2, 2011 at 6:55 AM, Marek Lindner lindner_ma...@yahoo.de wrote:
Hi,
being a regular user of the combined image I'd like to propose changing
the format in order to render it more flexible. The main focus are the
embedded files: The new format shall be able to embedded numerous files
and their filenames. Furthermore, the type field shall make the image
identifiable even if the image name has been mangled.
thanks to some feedback the format was slightly improved: There is room for an
md5 checksum and the type field is longer.
Here is the updated format:
# Write image header followed by all specified files
# The header is padded to 64k, format is:
# CE magic word (Combined Extended Image) (2 bytes)
# TYPE short description of the target device (32 bytes)
# NUM FILES number of files following the header (2 byte)
# file1_name name of the first file (20 bytes)
# file1_length length of the first file encoded as zero padded 8 digit
hex (8 bytes)
# file1_md5 md5 checksum of the first file (32 bytes)
# fileN_name name of the Nth file (20 bytes)
# fileN_length length of the Nth file encoded as zero padded 8 digit hex
(8 bytes)
# fileN_md5 md5 checksum of the Nth file (32 bytes)
Regards,
Marek
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Remove empty packages/libs/json-c
Done in r28684
Thanks,
--
-{Nico}
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] Include zlib.pc (packageconfig) with zlib
Applied with a minor modification in [28591]
Thanks,
--
-{Nico}
2011/10/13 Espen Jürgensen espenjurgen...@gmail.com:
Compiling zlib produces zlib.pc (pkgconfig), but it is not currently
installed in staging_dir/usr/lib/pkgconfig. If it was included other
packages depending on zlib could easier be compiled.
Signed-off-by: Espen Jürgensen espenjurgen...@gmail.com
---
Index: trunk/package/zlib/Makefile
===
--- trunk/package/zlib/Makefile (revision 28430)
+++ trunk/package/zlib/Makefile (working copy)
@@ -56,6 +56,9 @@
mkdir -p $(1)/usr/lib
$(CP) $(PKG_INSTALL_DIR)/usr/lib/libz.{a,so*} \
$(1)/usr/lib/
+ mkdir -p $(1)/usr/lib/pkgconfig
+ $(CP) $(PKG_INSTALL_DIR)/usr/lib/pkgconfig/zlib.pc \
+ $(1)/usr/lib/pkgconfig
endef
# libz.so is needed for openssl (zlib-dynamic)
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] listener: new package
Applied with some modifications in [28592] and fixed in [28594]
Thanks,
--
-{Nico}
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] busybox 1.19.2 update patch
Humm, my bad, it was inadvertently disabled... Thanks for spotting it !
--
-{Nico}
On Mon, Oct 24, 2011 at 7:03 AM, Liu Yu Fei, Eric
hoveringnowi...@gmail.com wrote:
May I ask why rdate is missed in this version?
Liu Yu Fei, Eric
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] busybox 1.19.2 update patch
Fixed in [28547]
--
-{Nico}
On Mon, Oct 24, 2011 at 9:31 AM, Nico n...@openwrt.org wrote:
Humm, my bad, it was inadvertently disabled... Thanks for spotting it !
--
-{Nico}
On Mon, Oct 24, 2011 at 7:03 AM, Liu Yu Fei, Eric
hoveringnowi...@gmail.com wrote:
May I ask why rdate is missed in this version?
Liu Yu Fei, Eric
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [patch] Update package mosquitto 0.12 - 0.13
Updated in [28558]
Thanks,
--
-{Nico}
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH 1/2] new package: libmpeg2
Added libmpeg2 (with minor modifications and a patch to disable
altivec on powerpc) in [28534].
Thanks!
--
-{Nico}
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] Include all libraries with libevent
Fixed in [28537]
Thanks!
--
-{Nico}
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH 2/2] new package: libmpeg2
Enabled gst-mod-mpeg2dec in [28542] and you fixed it in [28543]
Thanks!
--
-{Nico}
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] wget 1.13.4 update patch
Applied in [28519]
Thanks !
--
-{Nico}
On Wed, Oct 19, 2011 at 11:47 AM, Peter Wagner tripo...@gmx.at wrote:
Hi,
this patch updates wget to 1.13.4 as
1.12.2 is affected by this CVE
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2010-2252
Wget: User-assisted file creation or overwrite
/Peter Wagner
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] update iptables to 1.4.12.1
Humm, there is now a single xtables-multi providing
ip{,6}tables{,-save,-restore} and depending on libip4tc, lib6tc
libxtables. Not sure how we should deal with that, possible solutions
would be :
1) merge iptables, ip6tables, libip4tc, lib6tc libxtables in a single package
2) add another xtables package, providing xtables-multi, make it
depend on lib4tc, libip6tc libxtables, and add dependency on it to
iptables ip6tables
What do you think ?
--
-{Nico}
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] busybox 1.19.2 update patch
Applied in [28513], with a minor modification (groups applet disabled)
and patches refreshed
Thanks!
--
-{Nico}
On Thu, Oct 13, 2011 at 8:13 PM, Peter Wagner tripo...@gmx.at wrote:
Hi Noco,
this is the updated patch.
/Peter
On Donnerstag, 13. Oktober 2011 19:59:41 Nico wrote:
Hi Peter,
I started working on an update too, but your patch seems really good
and comprehensive.
Some suggestions :
1. Can you rename upstream patches in the 000-*.patch serie to
000-upstream_*.patch ?
2. Can you change the following new options default to n (to remain
conservative)
- BUSYBOX_CONFIG_FEATURE_MESG_ENABLE_ONLY_GROUP
- BUSYBOX_CONFIG_FEATURE_SKIP_ROOTFS
- BUSYBOX_CONFIG_FEATURE_UDHCP_8021Q
- BUSYBOX_CONFIG_PSTREE
- BUSYBOX_CONFIG_PWDX
- BUSYBOX_CONFIG_SETSERIAL
Thanks,
--
-{Nico}
On Thu, Oct 13, 2011 at 6:21 PM, Peter Wagner tripo...@gmx.at wrote:
Hi,
this patch updates busybox to 1.19.2.
all patches are refreshed.
/Peter Wagner
Signed-off-by: Peter Wagner tripo...@gmx.at
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] hiawatha: update to 7.7
Applied in [28479], thanks !
--
-{Nico}
2011/10/13 Raphaël HUCK r...@cksum.org:
Hi all,
this patch updates hiawatha to 7.7. Changelog:
* First parameter of Alias can now contain subdirectories.
* Improved stability for connections with SSL client authentication.
* Bugfix: BanOnFlooding was broken.
Thanks!
-Raphaël
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] mini_snmpd uci network interfaces support
Hi Gioacchino,
Your patch will also rename mini-snmpd to eigen-mini-snmpd, which is a
totally unrelated change ? Why ?
--
-{Nico}
On Sat, Oct 15, 2011 at 3:50 PM, Gioacchino Mazzurco
gmazzurc...@gmail.com wrote:
Last fixed patch ;)
Please use only that and ignore the two patch before
On Saturday 15 October 2011 10:39:13 Gioacchino Mazzurco wrote:
Better patch also more openwrt styled makefile
On Friday 14 October 2011 12:23:45 Gioacchino Mazzurco wrote:
I have done a patch that make mini_snmpd more uci style
+Instead of one option with comma separated interfaces now use uci list
+Intestad of use only real interface name now can use also uci interface
name the init script check if the interface name specified is from uci
than traslate it to real name interface if not check if the interface
exist then add it if not exist print an error message and ignore the
interface
suggestion are welcomed ;)
On Friday 14 October 2011 11:04:20 you wrote:
Hey all!
I see that in mini_snmpd config you have to use a list of real name
interfaces comma separated, that not the uci style...
I am thinking to write a patch to use uci list instead of option and
more over you can use uci network name also instead of real name
interface only
What do you thinks about that ?
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] busybox 1.19.2 update patch
Hi Peter,
I started working on an update too, but your patch seems really good
and comprehensive.
Some suggestions :
1. Can you rename upstream patches in the 000-*.patch serie to
000-upstream_*.patch ?
2. Can you change the following new options default to n (to remain
conservative)
- BUSYBOX_CONFIG_FEATURE_MESG_ENABLE_ONLY_GROUP
- BUSYBOX_CONFIG_FEATURE_SKIP_ROOTFS
- BUSYBOX_CONFIG_FEATURE_UDHCP_8021Q
- BUSYBOX_CONFIG_PSTREE
- BUSYBOX_CONFIG_PWDX
- BUSYBOX_CONFIG_SETSERIAL
Thanks,
--
-{Nico}
On Thu, Oct 13, 2011 at 6:21 PM, Peter Wagner tripo...@gmx.at wrote:
Hi,
this patch updates busybox to 1.19.2.
all patches are refreshed.
/Peter Wagner
Signed-off-by: Peter Wagner tripo...@gmx.at
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] Fix md5 hash for distribute package
It seems the original tarball was uploaded again to
http://pypi.python.org/pypi/distribute/ on 2011-09-22, after our
Makefile was updated.
Anyway, it is fixed in [28396]. Also, the matching tarball was
uploaded to http://downloads.openwrt.org/sources/ to prevent this from
happening again.
--
-{Nico}
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Problem adding a new package
Hi,
You should have at least a
define Package/foo/install
...
endef
section in your Makefile for anything to happen.
--
{Nico}
On 23/09/10 14:33, Stephen Thornton wrote:
Hi
Find attached a tarball of the noddy example I'm using. I'm using
kamikaze 8.09.2 BTW. And yes, I have selected the package in
menuconfig :-)
cheers
Steve
On 23 Sep 2010, at 13:22, Jonas Gorski wrote:
Hi,
On 23 September 2010 14:16, Stephen Thornton
st...@dowhatthouwilt.com wrote:
it works just fine for my kernel-mod) but when I hit make it refuses to
build the package (same for make V=99).
Foo666-2:trunk steve$ make package/matrix-apd/compile V=99
make[1]: Entering directory `/Volumes/Development/trunk'
make[2]: Entering directory
`/Volumes/Development/trunk/package/matrix-apd'
make[2]: Nothing to be done for `compile'.
make[2]: Leaving directory
`/Volumes/Development/trunk/package/matrix-apd'
make[1]: Leaving directory `/Volumes/Development/trunk'
Foo666-2:trunk steve$
A quick question: Did you select the package in menuconfig? IIRC
packages don't get built if they aren't selected to be build.
Regards,
Jonas
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] dnsmasq bogus nxdomains
Applied in r22592 with example in config.
Thanks,
--
-{Nico}
On 16/07/10 22:52, mickey wrote:
Am 16.07.2010 22:24, schrieb edgar.sol...@web.de:
sweet, simple and effective.
Thanks to the authors of dnsmasq for supporting this feature.
You should put the example configuration on
the wiki as well for others suffering the symptoms.
Shall i just put the example configuration or include the patch, too?
Btw, I am about to submit a patch to LuCI, too. It adds bogusnxdomain to
the webif in order to ease the handling for the enduser.
thanks ede
HTH,
mickey
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] openwrt on guruplug (kirkwood)
Hey Roland,
On 08/02/2010 02:57 PM, Roland Mieslinger wrote:
Hi,
first of all thanks for the feedback, but I'm stuck again.
There are few device specific kernel modules (eg. wireless, bluetooth)
what's the correct way to deal with them? I assume they should be built
as separate packages, as not all kirkwood based devices need them.
Exactly, if they are not packaged, they should be packaged in
package/kernel/modules/*.mk
I've changed the following files:
package/kernel/modules/crypto.mk
- HW AES accelerator
package/kernel/modules/block.mk
- SATA
package/kernel/modules/other.mk
- MMC Card reader
- Bluetooth, firmware req.
package/kernel/modules/wireless.mk
- wireless µAP, firmware req.
The following issues are left:
1) Firmware
Both bluetooth and wireless requires firmware files to be loaded. The
whole firmware is a set of four files. It would be wrong to bundle the
firmware with either bluetooth or wireless, as this would created a
additional dependency. Instead I'm trying to create a firmware package,
but I found no example of a copy only files package (a package without
need for compiling etc.). Can someone point me to an example?
Humm, why not add the firmware files to their respective kmod- packages ?
2) UBIFS/UBI Block Device
The default root filesystem for guruplug is UBIFS, which is a
appropriate choice, considering the 512MB NAND Flash available. UBIFS
isn't available, and changing this in package/kernel/modules/fs.mk and
package/kernel/modules/block.mk is the wrong way. Instead it should be
possible to choose UBIFS as root file system (like ext2, jffs2 or
squashfs) in Traget Images. Is this task already ongoing?
UBIFS root filesystems are already supported, look at the xburst target
and the ubifs feature.
Another issue is that boot from UBIFS requires CRC16 static in the
kernel, not as module. The package kmod-crc16 is no longer available for
this, but kmod-bluetooth requires kmod-crc16. How can this be solved?
Look at ./package/kernel/modules/001-depends.mk to see how this specific
issue is handled for the xburst target.
--
-{Nico}
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [OpenWrt] #7628: dibbler-server init script broken
On 07/17/2010 01:15 PM, Gioacchino Mazzurco wrote:
Please fix this is very simple, and the fix is already submitted
2010/7/16 OpenWrt openwrt-devel@lists.openwrt.org
mailto:openwrt-devel@lists.openwrt.org
#7628: dibbler-server init script broken
---+
Reporter: gmazzurc...@… | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone:
Component: packages | Version: Trunk
Keywords: |
---+
dibbler server init script miss start argument on odibbler-server
invoking
#!/bin/sh /etc/rc.common
START=90
STOP=90
start() {
[ -d /var/lib/dibbler ] || mkdir -p /var/lib/dibbler
dibbler-server
}
stop() {
killall -9 dibbler-server
}
should be
#!/bin/sh /etc/rc.common
START=90
STOP=90
start() {
[ -d /var/lib/dibbler ] || mkdir -p /var/lib/dibbler
dibbler-server start
}
stop() {
dibbler-server stop
}
Applied in https://dev.openwrt.org/changeset/22245
Thanks,
--
-{Nico}
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [OpenWrt-Tickets] [OpenWrt] #7269: grub notbuilding for x86
Thierry MUSEUX - www.fwt.fr - wrote:
Problem not solved, same thing with last trunk 21343
I am on debian x86_64
Why in configure:
checking build system type... x86_64-pc-linux-gnu
It is solved.
You have to investigate why your 64-bits build system refuses to build a
32-bits app (see ./build_dir/grub-0.97/config.log). Depending on the
distro you're using, you might need to install additional packages like
gcc-multilib (Debian/Ubuntu) or gcc.i686 libgcc.i686 (CentOS/Fedora/RHEL).
I'm working on Prereq check to spot that before attempting to build...
Cheers,
--
-{Nico}
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [OpenWrt-Tickets] [OpenWrt] #7269: grub notbuilding for x86
Thierry,
Can you try the attached patch ?
--
-{Nico}
Nico wrote:
Thierry MUSEUX - www.fwt.fr - wrote:
Problem not solved, same thing with last trunk 21343
I am on debian x86_64
Why in configure:
checking build system type... x86_64-pc-linux-gnu
It is solved.
You have to investigate why your 64-bits build system refuses to build a
32-bits app (see ./build_dir/grub-0.97/config.log). Depending on the
distro you're using, you might need to install additional packages like
gcc-multilib (Debian/Ubuntu) or gcc.i686 libgcc.i686 (CentOS/Fedora/RHEL).
I'm working on Prereq check to spot that before attempting to build...
Cheers,
--
-{Nico}
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Index: package/grub/Makefile
===
--- package/grub/Makefile (revision 21305)
+++ package/grub/Makefile (working copy)
@@ -67,5 +67,16 @@
$(CP) $(PKG_INSTALL_DIR)/usr/sbin/* $(1)/usr/sbin/
endef
+ifeq ($(HOST_ARCH),x86_64)
+ define Require/working-gcc32
+ echo 'int main(int argc, char **argv) { return 0; }' | \
+ gcc -x c -o $(TMP_DIR)/a.out - -m32 -lc
+ endef
+endif
+
+$(eval $(call Require,working-gcc32, \
+ Please install 32 bits development files. \
+))
+
$(eval $(call HostBuild))
$(eval $(call BuildPackage,grub))
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Backfire 10.03 Released
OpenWrt Release 10.03, codename Backfire. The OpenWrt team will humbly like to announce the final version of the 10.03 release, codenamed Backfire. ___ __ | |.-.-.-.| | | |..| |_ | - || _ | -__| || | | || _|| _| |___|| __|_|__|__||||__| || |__| W I R E L E S S F R E E D O M Backfire (10.03, r20728) -- * 1/3 shot KahluaIn a shot glass, layer Kahlua * 1/3 shot Bailey's on the bottom, then Bailey's, * 1/3 shot Vodka then Vodka. --- The OpenWrt 10.03 backfire source code can be checked out at: svn://svn.openwrt.org/openwrt/branches/backfire/ Further information on how to checkout the Backfire source code is found at: https://dev.openwrt.org/wiki/GetSource Highlights and changes since last stable release: * Linux 2.6.32 long term support kernel, uClibc 0.9.30 * Support for mac80211 based drivers, such as ath5k, ath9k and b43 * Support for alternative libc implementations * New web server uhttpd (busybox httpd now disabled, as default) * Extended support for X.org with GTK+, QT etc. * New switch configuration format for Broadcom devices. See: http://wiki.openwrt.org/doc/uci/network#switch * New wpa-supplicant and hostapd multicall binary wpad * Initial mac80211 wireless support for Broadcom radios * Modular preinit system * Optional support for rootfs on external media * Support for the TRX v2 format required by newer devices such as the Linksys WRT54G3GV2-VF * New /etc/openwrt_release machine-readable file with detailed release version information New platforms: * Atheros AP81: Ubiquiti Router Station Pro, TP-Link TL-WR1043ND, Netgear WNDR3700, etc. (ar71xx) * Broadcom ADSL modem/router chipsets (brcm63xx) * Cavium Networks Octeon based boards (octeon) * Cobalt Networks MIPS-based servers (cobalt) * Infineon Danube/TwinPass with open DSL VoIP drivers (ifxmips) * Ingenic XBurst: QI Ben NanoNote (xburst/qi-lb60) * Intel Tolapai SoC (x86/ep80579) * Marvell Kirkwood: SheevaPlug, GuruPlug, OpenRD... (kirkwood) * Marvell Orion SoC (orion) Known Issues: * Currently 5 GHz channels do not work with mac80211 based drivers due to DFS regulatory issues. More detailed information available at: https://dev.openwrt.org/milestone/Backfire%2010.03 Special thanks to marcant.net for offering buildbot assistance Yours truly, -- The release management team Andy Boyett Nicolas Thill ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Backfire 10.03-rc3 - ASUS WL-500g Premium V2 USB
Michael Conrad wrote:
Hi,
The OpenWrt Team is pleased to announce the third and last release
candidate (RC3) of the next stable release, codenamed Backfire. Testing
of this build will help refine the code in preparation of the final
release.
I have tested usb support for the ASUS WL-500gP V2 today, but no
success with brcm-2.4 and brcm47xx.
In addition to the software included into the squashfs-image, I have
installed following packages
pciutils
usbutils
kmod-usb2
kmod-usb-serial-pl2303
I have attached some output from opkg, lspci, lsusb and dmesg for
brcm47xx target. It looks like, that the loading of the usb modules
fail (unknown symbols).
opkg was not installing the packages in the right order, this has been
fixed in r20686 [1].
1. https://dev.openwrt.org/changeset/20686
--
-{Nico}
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Backfire 10.03-rc3
*** Release Candidate 3 *** The OpenWrt Team is pleased to announce the third and last release candidate (RC3) of the next stable release, codenamed Backfire. Testing of this build will help refine the code in preparation of the final release. Binaries can be downloaded at http://downloads.openwrt.org/backfire/10.03-rc3/ OpenWrt Trunk has now been branched and named backfire within the repository. The Backfire branch source code can be checked out at svn://svn.openwrt.org/openwrt/branches/backfire/ Changes since Backfire RC2: * support for Infineon Danube/TwinPass (ifxmips) * support for Intel Tolapai SoC (ep80579) * experimental ImageBuilder files back again * new /etc/openwrt_release machine-readable file with detailed release informations Known Issues: * Encounters of spurious log messages every second on some brcm-2.4 brcm47xx installs * Kernel modules missing on ixp4xx * There have been reports that sysupgrade can fail on brcm-2.4 and brcm47xx under certain conditions More detailed information available at https://dev.openwrt.org/milestone/Backfire%2010.03-rc3 Special thanks to marcant.net [1] for offering buildbot assistance 1. http://marcant.net/ Yours truly, -- The release management team Andy Boyett Nicolas Thill ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] busybox 1.16.0 update patch
Hi Peter,
I just updated busybox to v1.16.1 in r20661 [1], using your 1.16.0 patch
as a base, thanks !
1. https://dev.openwrt.org/changeset/20661
Cheers,
--
-{Nico}
Peter Wagner wrote:
Hi,
this is my busybox update patch...
please apply
greets
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Backfire 10.03-rc2
*** Release Candidate 2 *** The OpenWrt Team would like to announce a second release candidate (RC2) of the next major release, codenamed Backfire. Testing of this build will help refine the code in preparation of RC3 and the final release. Binaries can be downloaded at http://downloads.openwrt.org/backfire/10.03-rc2/ Changes since Backfire RC1: * Kernel updated to 2.6.32.10 * New web server (uhttpd) for the web interface, supporting SSL/TLS and CGI, replaces busybox httpd applet * Support for .trx v2 firmware image format added (needed for Linksys WRT54G3GV2-VF) New packages: * cyassl * px5g * uhttpd New targets: * kirkwood (Marvell Kirkwood: SheevaPlug, GuruPlug, OpenRD...) * xburst (Ingenic XBurst: QI Ben NanoNote) Known Issues: * Encounters of spurious log messages every second on some brcm-2.4 brcm47xx installs * Kernel modules missing on ixp4xx * Under rare circumstances, certain LuCI pages may crash due to a bug in the Lua VM More detailed informations available at https://dev.openwrt.org/milestone/Backfire%2010.03-rc2 Note: due to some last minute build problems, ifxmips is not included in RC2, but will be included in RC3 and final Backfire release. Special thanks to marcant.net [1] for offering buildbot assistance :) 1. http://marcant.net/ Yours truly, -- The release management team Andy Boyett Nicolas Thill ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Backfire 10.03-rc1
Right, 2.6.32 is preferred and will probably be supported for 2-3 years
[1]. However, targets proven to be stable at 2.6.30.10 won't be get
updated to 2.6.32.x for Backfire. Such updates will probably later in a
Backfire 10.03.1 point-release.
1. http://thread.gmane.org/gmane.linux.kernel/939800
--
-{Nico}
On 25/03/10 22:14, Matthias Buecher / Germany wrote:
Do I understand correctly that kernel 2.6.32.9 is one of the preferred
kernels for Backfire, and not 2.6.30.10?
(see https://dev.openwrt.org/changeset/20410 and Nico's [2])
Just want to make sure.
Maddes
P.S.:
Will install it onto my LinkSys WRT350Nv2 this weekend if time permits.
On 24.03.2010 18:15, Nico wrote:
Backfire 10.03-rc1 is still based on trunk @ 20254. In Backfire
10.03-rc1 milestone in Trac [1], you can find the diff used attached
[2] at the end of the page.
1. https://dev.openwrt.org/milestone/Backfire%2010.03-rc1
2.
https://dev.openwrt.org/attachment/milestone/Backfire%2010.03-rc1/backfire-10.03-rc1-trunk-r20254.diff
Regards,
--
-{Nico}
Bruno Wolff III wrote:
On Wed, Mar 24, 2010 at 17:10:25 +0100,
Nico n...@openwrt.org wrote:
*** Release Candidate 1 ***
The OpenWrt Team would like to announce a release candidate (RC1) of the
next major release, codenamed Backfire. Testing of this build will help
refine the code in preparation of the final release.
Binaries can be downloaded at
http://downloads.openwrt.org/backfire/10.03-rc1/
Is there a separate branch for backfire or is it trunk?
(I want some extra things built in, and so am interested in doing builds
that use the same code as backfire but with a couple of different build
options.)
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Backfire 10.03-rc1
It seems 2.6.32.10 applies on all targets at 2.6.32.9, so I have no
problem switching to 2.6.32.10. Ideally, it would be great if all
targets at 2.6.32.x could be switched to the same version (coherency)
and such updates be committed before Friday evening.
--
-{Nico}
On 25/03/10 22:44, Matthias Buecher / Germany wrote:
Sorry, a typo, meant 2.6._32_.10 not .30.10.
On 25.03.2010 22:15, Matthias Buecher / Germany wrote:
Do I understand correctly that kernel 2.6.32.9 is one of the preferred
kernels for Backfire, and not 2.6.30.10?
(see https://dev.openwrt.org/changeset/20410 and Nico's [2])
Just want to make sure.
Maddes
P.S.:
Will install it onto my LinkSys WRT350Nv2 this weekend if time permits.
On 24.03.2010 18:15, Nico wrote:
Backfire 10.03-rc1 is still based on trunk @ 20254. In Backfire
10.03-rc1 milestone in Trac [1], you can find the diff used attached
[2] at the end of the page.
1. https://dev.openwrt.org/milestone/Backfire%2010.03-rc1
2.
https://dev.openwrt.org/attachment/milestone/Backfire%2010.03-rc1/backfire-10.03-rc1-trunk-r20254.diff
Regards,
--
-{Nico}
Bruno Wolff III wrote:
On Wed, Mar 24, 2010 at 17:10:25 +0100,
Nico n...@openwrt.org wrote:
*** Release Candidate 1 ***
The OpenWrt Team would like to announce a release candidate (RC1) of the
next major release, codenamed Backfire. Testing of this build will help
refine the code in preparation of the final release.
Binaries can be downloaded at
http://downloads.openwrt.org/backfire/10.03-rc1/
Is there a separate branch for backfire or is it trunk?
(I want some extra things built in, and so am interested in doing builds
that use the same code as backfire but with a couple of different build
options.)
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Backfire 10.03-rc1
*** Release Candidate 1 *** The OpenWrt Team would like to announce a release candidate (RC1) of the next major release, codenamed Backfire. Testing of this build will help refine the code in preparation of the final release. Binaries can be downloaded at http://downloads.openwrt.org/backfire/10.03-rc1/ Highlights: * brcm-2.4 updated to 2.4.37 kernel * other targets updated to 2.6.30 or 2.6.32 * gcc updated to 4.3.3 for arm/mips targets, 4.4.3 for powerpc * uClibc updated to 0.9.30.1 * b43 wireless driver for Broadcom 11g chipsets on the 2.6 kernel * ath9k wireless driver for Atheros 11n chipsets * support for many new ar71xx devices * magicbox target folded into ppc40x New targets: * brcm63xx - Broadcom ADSL modem/routers chipset * cobalt - MIPS-based servers from Cobalt Networks * octeon - Cavium Networks Octeon * orion - Marvell Orion devices Known Issues: * ipv6 resolution via uClibc can produce segfaults (already fixed, but not available in this release) * busybox httpd occaisionally segfaults or hangs, but luci uses lucid instead of httpd by default. kill -9 should be used if it refuses to die * luci is still being worked on for this release, some pages may be broken More detailed informations available at https://dev.openwrt.org/milestone/Backfire%2010.03-rc1 Note: After a long development phase, Broadcom wireless should now be working on brcm47xx, start testing. This would finally move all OpenWrt platforms to current 2.6 kernels. Special thanks to eNovance http://www.enovance.com [1] for making uploads a breeze :) 1. http://www.enovance.com/ Yours truly, -- The release management team Andy Boyett Nicolas Thill ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] disable ipk stripping
Hi Vipul,
There is a Binary stripping method option under Global build
settings where you can choose how binaries should be stripped (or not).
Cheers,
--
-{Nico}
On 23/03/10 03:59, Vipul M Sawant wrote:
Hello,
I am trying to compile the clamav package for kamikaze x86. The
compile process is stripping the binaries - rstrip.sh:
/home/vsawant/Documents/projects/routers/openwrtsrc/build_dir/target-i386_uClibc-0.9.30.1/clamav-0.95.3/ipkg-x86/clamav/usr/sbin/clamscan:executable.
How to disable the strip to debug the binaries using gdb?
Thanks,
Vipul
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Announcing the Wireless Battle Mesh v3 (02-06 June 2010, Bracciano, Italy)
== Announcing the Wireless Battle of the Mesh v3 (02-06 June 2010, Bracciano, Italy) == The next 'Wireless Battle of the Mesh' will take place from Wed 2nd till Sun 6th of June in Bracciano (near Rome), Italy. The event aims to bring together people from across Europe to test the performance of different routing protocols for ad-hoc networks, like Babel, B.A.T.M.A.N., and OLSR. This third WBM will be improving the testbed conditions for mesh protocols with standardized testing procedures that will be reported after the event for the wireless communities. On the development side, a flashing tool will be presented to simplify the deployment of such wireless networks based on OpenWrt stable release and packages for each protocol. If you are a mesh networking enthusiast, community networking activist, or have an interest in mesh networks you have to check this out! Informations about the event are gathered at: http//battlemesh.org/ Location The event will take place in the camping Porticciolo in Bracciano, Italy. along the border of the lake of Bracciano, just North-West of Rome. Registration Registrations will be available at different hackerspaces (Fusolab, HSBXL, /tmp/lab, metalab, CCC, ...) and on the official website for the event at http://battlemesh.org Fees Every participant needs to donate 50 EUR (this should cover the costs for the camping, and the infrastructure). To finance this event, we ask you to pay when subscribing (paypal, bank transfer or cash). Contact === * Web: http://battlemesh.org/BattleMeshV3 * Email: conta...@ninux.org * IRC: irc.freenode.net #battlemesh ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [patch] firewall feature
Just to be clear, it's not intended to be a selectable feature, it will
just be defined if CONFIG_NETFILTER is defined in the target kernel
config, like it is for the GPIO, PCI or USB features.
What do you mean by migrate to the DEVICE_TYPE ?
--
-{Nico}
Imre Kaloz wrote:
On Mon, 01 Mar 2010 07:19:02 +0100, Nico n...@openwrt.org wrote:
Hi,
Any objections adding a firewall feature ? That would help preventing
netfilter related modules and utilities from being build on systems
where CONFIG_NETFILTER is not set ?
Systems should either drop that setting or migrate to the DEVICE_TYPE,
there's no need for another feature for this, IMHO.
Imre
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [patch] firewall feature
Hi devs,
Any objections adding a firewall feature ? That would help preventing
netfilter related modules and utilities from being build on systems
where CONFIG_NETFILTER is not set ?
Proposed patch attached
Regards,
--
-{Nico}
Index: include/target.mk
===
--- include/target.mk (revision 19922)
+++ include/target.mk (working copy)
@@ -138,6 +138,9 @@
.SILENT: $(TMP_CONFIG)
.PRECIOUS: $(TMP_CONFIG)
+ifneq ($(CONFIG_NETFILTER),)
+ FEATURES += firewall
+endif
ifneq ($(CONFIG_GENERIC_GPIO),)
FEATURES += gpio
endif
Index: target/Config.in
===
--- target/Config.in (revision 19922)
+++ target/Config.in (working copy)
@@ -17,6 +17,9 @@
config DISPLAY_SUPPORT
bool
+config FIREWALL_SUPPORT
+ bool
+
config GPIO_SUPPORT
bool
Index: scripts/metadata.pl
===
--- scripts/metadata.pl (revision 19922)
+++ scripts/metadata.pl (working copy)
@@ -154,6 +154,7 @@
/broken/ and $ret .= \tdepends BROKEN\n;
/audio/ and $ret .= \tselect AUDIO_SUPPORT\n;
/display/ and $ret .= \tselect DISPLAY_SUPPORT\n;
+ /firewall/ and $ret .= \tselect FIREWALL_SUPPORT\n;
/gpio/ and $ret .= \tselect GPIO_SUPPORT\n;
/pci/ and $ret .= \tselect PCI_SUPPORT\n;
/pcie/ and $ret .= \tselect PCIE_SUPPORT\n;
Index: package/arptables/Makefile
===
--- package/arptables/Makefile (revision 19922)
+++ package/arptables/Makefile (working copy)
@@ -22,7 +22,7 @@
SECTION:=net
CATEGORY:=Network
TITLE:=ARP firewalling software
- DEPENDS:=+kmod-arptables
+ DEPENDS:= @FIREWALL_SUPPORT +kmod-arptables
URL:=http://ebtables.sourceforge.net
endef
Index: package/ebtables/Makefile
===
--- package/ebtables/Makefile (revision 19922)
+++ package/ebtables/Makefile (working copy)
@@ -22,7 +22,7 @@
define Package/ebtables
SECTION:=net
CATEGORY:=Network
- DEPENDS:=+kmod-ebtables
+ DEPENDS:= @FIREWALL_SUPPORT +kmod-ebtables
TITLE:=Ethernet bridge firewall administration utility
URL:=http://ebtables.sourceforge.net/
endef
Index: package/ipset/Makefile
===
--- package/ipset/Makefile (revision 19922)
+++ package/ipset/Makefile (working copy)
@@ -19,7 +19,7 @@
include $(INCLUDE_DIR)/package.mk
define Package/ipset/Default
- DEPENDS:= @LINUX_2_6 @(!(TARGET_ps3||TARGET_pxcab)||BROKEN)
+ DEPENDS:= @FIREWALL_SUPPORT @LINUX_2_6
endef
define Package/ipset
Index: package/iptables/Makefile
===
--- package/iptables/Makefile (revision 19922)
+++ package/iptables/Makefile (working copy)
@@ -33,6 +33,7 @@
SECTION:=net
CATEGORY:=Network
URL:=http://netfilter.org/
+ DEPENDS:= @FIREWALL_SUPPORT
endef
define Package/iptables/Module
Index: package/kernel/modules/netfilter.mk
===
--- package/kernel/modules/netfilter.mk (revision 19922)
+++ package/kernel/modules/netfilter.mk (working copy)
@@ -16,6 +16,7 @@
KCONFIG:=$(KCONFIG_IPT_CORE)
FILES:=$(foreach mod,$(IPT_CORE-m),$(LINUX_DIR)/net/$(mod).$(LINUX_KMOD_SUFFIX))
AUTOLOAD:=$(call AutoLoad,40,$(notdir $(IPT_CORE-m)))
+ DEPENDS:= @FIREWALL_SUPPORT
endef
define KernelPackage/ipt-core/description
@@ -319,7 +320,7 @@
define KernelPackage/ip6tables
SUBMENU:=$(NF_MENU)
TITLE:=IPv6 modules
- DEPENDS:=+kmod-ipv6
+ DEPENDS:= @FIREWALL_SUPPORT +kmod-ipv6
KCONFIG:=$(KCONFIG_IPT_IPV6)
FILES:=$(foreach mod,$(IPT_IPV6-m),$(LINUX_DIR)/net/$(mod).$(LINUX_KMOD_SUFFIX))
AUTOLOAD:=$(call AutoLoad,49,$(notdir $(IPT_IPV6-m)))
@@ -340,6 +341,7 @@
CONFIG_IP_NF_ARPFILTER \
CONFIG_IP_NF_ARP_MANGLE
AUTOLOAD:=$(call AutoLoad,49,$(notdir $(patsubst %.$(LINUX_KMOD_SUFFIX),%,$(wildcard $(LINUX_DIR)/net/ipv4/netfilter/arp*.$(LINUX_KMOD_SUFFIX)
+ DEPENDS:= @FIREWALL_SUPPORT
endef
define KernelPackage/arptables/description
@@ -352,7 +354,7 @@
define KernelPackage/ebtables
SUBMENU:=$(NF_MENU)
TITLE:=Bridge firewalling modules
- DEPENDS:=...@linux_2_6
+ DEPENDS:= @FIREWALL_SUPPORT @LINUX_2_6
FILES:=$(foreach mod,$(EBTABLES-m),$(LINUX_DIR)/net/$(mod).$(LINUX_KMOD_SUFFIX))
KCONFIG:=CONFIG_BRIDGE_NETFILTER=y \
$(KCONFIG_EBTABLES)
@@ -425,7 +427,7 @@
define KernelPackage/nfnetlink
SUBMENU:=$(NF_MENU)
TITLE:=Netlink-based userspace interface
- DEPENDS:=...@linux_2_6 +kmod-ipt-core
+ DEPENDS:= @FIREWALL_SUPPORT @LINUX_2_6 +kmod-ipt-core
FILES:=$(LINUX_DIR)/net/netfilter/nfnetlink.$(LINUX_KMOD_SUFFIX)
KCONFIG:=CONFIG_NETFILTER_NETLINK
AUTOLOAD:=$(call AutoLoad,48,nfnetlink)
@@ -440,7 +442,7 @@
define KernelPackage/nfnetlink/Depends
SUBMENU:=$(NF_MENU)
- DEPENDS
Re: [OpenWrt-Devel] How to strip correctly?
Yeah, i agree with Luigi, best option right now is to prevent upstream Makefile from stripping binaries as we have our own (configurable) way of doing it... -- Nico Luigi Mantellini wrote: My opinion is to remove stripping from source makefiles and use only OpenWRT mechanism to generate stripped elf. my2EuroCents, luiig On Fri, Sep 25, 2009 at 1:17 PM, Matthias Buecher / Germany m...@maddes.net wrote: Some packages have strip errors with the original makefile (e.g. sslh, proftpd). Now I want to know how to handle this correctly for OpenWrt. Possible solutions: #1 Remove strip with a patch as stripping is handled separately by OpenWrt (is it?) #2 Fix strip with a patch by using OpenWrt's $(STRIP) substitution. (how this has to look like if no strip is selected?) #3 Install binutils-multiarch (here Debian) to make it build with regular strip. (package not yet a pre-requisition) Your answers will make my future patches more correct and fitting the OpenWrt development guide line? Kind regards Matthias Maddes Bücher -- http://www.maddes.net/ Home: Earth / Germany / Ruhr-Area ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Regarding external cross-toolchain
Hi Luigi et all, External toolchain support, based on my previous patches and your additions, was committed in r17682. Here's what I changed : - use target name for naming build staging directories, instead on unknown gcc/libc versions - use the same way of specifying libraries in ./package/base-files for external native toolchains - make the toolchain options menu disappear when external toolchain support is selected I'll check the changes in ./package later today as it seems some of them have no effects (in hotplug uci iirc) Thanks again for your help ! Regards, -- Nico Luigi Mantellini wrote: I lost some word... Hi All, I rebased the patch on the last tr...@17618. I hope to see the external-toolchain patch in the main line. best regards, luigi On Sun, Sep 20, 2009 at 5:15 PM, Luigi Mantellini luigi.mantellini...@gmail.com wrote: Hi All, I rebased the patch on the last tr...@17618 the external-toolchain patch in the main line. best regards, luigi On Thu, Sep 10, 2009 at 12:56 AM, Luigi Mantellini luigi.mantellini...@gmail.com wrote: Thanks :D On Thu, Sep 10, 2009 at 12:17 AM, Nicon...@openwrt.org wrote: Hi Luigi, There were no particular reasons preventing external toolchain support from hitting trunk apart from a constant lack of time on my side... I'll try my best to have it commited by the end of the week. Thanks for your help and support ! Regards, -- Nico Luigi 'Comio' Mantellini wrote: Hi List, Hi Nico, find the attached my contribute. Starting from nico's patch I build this patchset that adds the ability to use use an external toolchain (rebased on r17459). I compiled a simple ppc440 target with and without the external toolchain usage and it seems to work fine. As external toolchain I used the CodeSourcery G++lite 4.3-50 for Power EABI (http://www.codesourcery.com/sgpp/lite/power/portal/release603). Find also the config.external and config.normal configs to look my board setup. My wish is to see this patch in the main-line as soon possible because is very important for my job. Any feedback is welcome. best regards, luigi Il domenica 6 settembre 2009 20:26:46 Luigi Mantellini ha scritto: Hi List, as in the past I will ask again opinions regarding the optional support for external cross-toolchain. Reading the dev.openwrt.org I see: OpenWrt is currently being used in industrial control systems, small robots, sensor networks, home control solutions, VoIP systems, both wired and wireless networks and a whole lot more. I'm working on network devices and usually I receive from my vendors the BSP and toolchain that is considered official and safe for the BSP. My suppliers usually don't accent to support BSP (and anwser to my questions) if I don't use the provided toolchain. From these considerations, My opinion is that external target-specific toolchian should be supported by OpenWRT avoiding to compile everytime the toolchain. In past Nico sent a set of patch for support this feature but I think that are not included yet in the mainline. Nico, can you provide me your last patches? and explain if them will be included or not? thanks in advance and best regards, luigi ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel -- Luigi 'Comio' Mantellini RD - Software Industrie Dial Face S.p.A. Via Canzo, 4 20068 Peschiera Borromeo (MI), Italy Tel.: +39 02 5167 2813 Fax: +39 02 5167 2459 web: www.idf-hit.com mail: luigi.mantell...@idf-hit.com -- Luigi 'Comio' Mantellini RD - Software Industrie Dial Face S.p.A. Via Canzo, 4 20068 Peschiera Borromeo (MI), Italy Tel.: +39 02 5167 2813 Fax: +39 02 5167 2459 web: www.idf-hit.com mail: luigi.mantell...@idf-hit.com ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Regarding external cross-toolchain
Hi Luigi, There were no particular reasons preventing external toolchain support from hitting trunk apart from a constant lack of time on my side... I'll try my best to have it commited by the end of the week. Thanks for your help and support ! Regards, -- Nico Luigi 'Comio' Mantellini wrote: Hi List, Hi Nico, find the attached my contribute. Starting from nico's patch I build this patchset that adds the ability to use use an external toolchain (rebased on r17459). I compiled a simple ppc440 target with and without the external toolchain usage and it seems to work fine. As external toolchain I used the CodeSourcery G++lite 4.3-50 for Power EABI (http://www.codesourcery.com/sgpp/lite/power/portal/release603). Find also the config.external and config.normal configs to look my board setup. My wish is to see this patch in the main-line as soon possible because is very important for my job. Any feedback is welcome. best regards, luigi Il domenica 6 settembre 2009 20:26:46 Luigi Mantellini ha scritto: Hi List, as in the past I will ask again opinions regarding the optional support for external cross-toolchain. Reading the dev.openwrt.org I see: OpenWrt is currently being used in industrial control systems, small robots, sensor networks, home control solutions, VoIP systems, both wired and wireless networks and a whole lot more. I'm working on network devices and usually I receive from my vendors the BSP and toolchain that is considered official and safe for the BSP. My suppliers usually don't accent to support BSP (and anwser to my questions) if I don't use the provided toolchain. From these considerations, My opinion is that external target-specific toolchian should be supported by OpenWRT avoiding to compile everytime the toolchain. In past Nico sent a set of patch for support this feature but I think that are not included yet in the mainline. Nico, can you provide me your last patches? and explain if them will be included or not? thanks in advance and best regards, luigi ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Automatically remounting USB devices on Reboot?
Hi Kunal, Remove storage devices are automagically mounted by a script, /sbin/usbstorage, via hotplug when a device is plugged in. I didn't test the change you're proposing on a real device with USB support, but I guess automounting with mount -a and having /sbin/usbstorage run aside will conflict at some point. A better option would be to let /sbin/usbstorage be aware of mountpoints defined in /etc/fstab. I know an enhanced automounter is on its way, I'll try to get more infos and keep you posted. Regards, -- Nico Kunal Punjabi wrote: We just ported our platform over to OpenWRT and have it running. I found that temporary storage devices like USB do not get mounted when the OpenWRT router is rebooted, although the drives were properly mounted prior to the reboot. This seems to happen because usbfs is invoked after fstab does a mount -a, in effect the mount point isn't found. The fix for this would be to move S20fstab later on in the initialization sequence..after S39usb. That would make sure the mount -a gets executed after S39, and not before or even in it. Is such a reorder acceptable, i.e. can I move S20fstab **after** S39USB? Is it likely to be accepted when we push our changes upstream (to the openwrt sources)? Or was OpenWRT designed to NOT automatically mount non-persistent storages like usb on reboot? Thanks Kunal ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] OpenWRT and User Mode Linux (UML)
Hi Benjamin, UML binaries are built with the host toolchain and are meant to run on the host they were built on, so we thought it was easier for us (and less error-prone) to let everyone build their own. If anyone is interested and can lend some VMs, I can work on some DEB/RPM image packaging. Regards, -- Nico Benjamin Henrion wrote: Hi, See here for my experience with OpenWRT and UML: http://zoobab.wikidot.com/openwrt-and-user-mode-linux Please note that UML is not provided as a binary on the downloads.openwrt.org, and I wonder why. Best, -- Benjamin Henrion bhenrion at ffii.org FFII Brussels - +32-484-566109 - +32-2-4148403 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] Netfilter Netlink package extension
Hi Fabian, I already reverted the change on libnetfilter-* libraries and added the missing netfilter netlink interface modules in 8.09. I'll add the missing NFLOG NFQUEUE kernel and userland support later. Thanks! -- Nico Fabian Hugelshofer wrote: Hi all, To use the Netfilter NFLOG and NFQUEUE targets, kernel modules and iptables libraries xt_NFLOG and xt_NFQUEUE are needed. I added these to the corresponding Netfilter kernel packages and created new iptables module packages. This patch also adds support for connection tracking events for module nf_ct_netlink. Changeset 15335 removes packages libnetfilter-conntrack, libnetfilter-log and libnetfilter-queue from 8.09 because the kernel modules do not exist in 8.09. Please consider reverting this change. I have been using these packages already before the kernel packages were added. Cheers, Fabian [PATCH] Extend Netfilter Netlink packages - Add kernel modules for NFLOG and NFQUEUE targets - Add packages for iptables NFLOG and NFQUEUE libraries - Enable connection tracking events for ctnetlink - Increase priority for the Netlink modules to 49 (nfnetlink is loaded at 48). - Update Copyright Signed-off-by: hugelshofer2...@gmx.ch Index: include/netfilter.mk === --- include/netfilter.mk (revision 15354) +++ include/netfilter.mk (working copy) @@ -1,5 +1,5 @@ # -# Copyright (C) 2006-2008 OpenWrt.org +# Copyright (C) 2006-2009 OpenWrt.org # # This is free software, licensed under the GNU General Public License v2. # See /LICENSE for more information. @@ -275,6 +275,18 @@ $(eval $(call nf_add,IPT_ULOG,CONFIG_IP_NF_TARGET_ULOG, $(P_V4)ipt_ULOG)) +#nfnetfilter log + +$(eval $(call nf_add,NFNETLINK_LOG,CONFIG_NETFILTER_NETLINK_LOG, $(P_XT)nfnetlink_log)) +$(eval $(call nf_add,NFNETLINK_LOG,CONFIG_NETFILTER_XT_TARGET_NFLOG, $(P_XT)xt_NFLOG)) + + +# nfnetfilter queue + +$(eval $(call nf_add,NFNETLINK_QUEUE,CONFIG_NETFILTER_NETLINK_QUEUE, $(P_XT)nfnetlink_queue)) +$(eval $(call nf_add,NFNETLINK_QUEUE,CONFIG_NETFILTER_XT_TARGET_NFQUEUE, $(P_XT)xt_NFQUEUE)) + + # userland only IPT_BUILTIN += $(IPT_CORE-y) $(IPT_CORE-m) IPT_BUILTIN += $(IPT_CONNTRACK-y) @@ -292,5 +304,7 @@ IPT_BUILTIN += $(IPT_NATHELPER-y) IPT_BUILTIN += $(IPT_NATHELPER_EXTRA-y) IPT_BUILTIN += $(IPT_ULOG-y) +IPT_BUILTIN += $(NFNETLINK_LOG-y) +IPT_BUILTIN += $(NFNETLINK_QUEUE-y) endif # __inc_netfilter Index: package/iptables/Makefile === --- package/iptables/Makefile (revision 15354) +++ package/iptables/Makefile (working copy) @@ -1,5 +1,5 @@ # -# Copyright (C) 2006-2008 OpenWrt.org +# Copyright (C) 2006-2009 OpenWrt.org # # This is free software, licensed under the GNU General Public License v2. # See /LICENSE for more information. @@ -217,6 +217,28 @@ TITLE:=IPset extension endef +define Package/iptables-mod-nflog +$(call Package/iptables/Module, +kmod-nfnetlink-log) + TITLE:=NFLOG Target +endef + +define Package/iptables-mod-nfqueue/description + iptables extensions for user-space packet logging via NFNETLINK. + Includes: + - libxt_NFLOG +endef + +define Package/iptables-mod-nfqueue +$(call Package/iptables/Module, +kmod-nfnetlink-queue) + TITLE:=NFQUEUE Target +endef + +define Package/iptables-mod-nfqueue/description + iptables extensions for user-space packet queueing via NFNETLINK. + Includes: + - libxt_NFQUEUE +endef + define Package/iptables-utils $(call Package/iptables/Module, ) TITLE:=iptables save and restore utilities @@ -339,5 +361,7 @@ $(eval $(call BuildPlugin,iptables-mod-nat-extra,$(IPT_NAT_EXTRA-m))) $(eval $(call BuildPlugin,iptables-mod-iprange,$(IPT_IPRANGE-m))) $(eval $(call BuildPlugin,iptables-mod-ulog,$(IPT_ULOG-m))) +$(eval $(call BuildPlugin,iptables-mod-nflog,$(NFNETLINK_LOG-m))) +$(eval $(call BuildPlugin,iptables-mod-nfqueue,$(NFNETLINK_QUEUE-m))) $(eval $(call BuildPackage,ip6tables)) $(eval $(call BuildPackage,ip6tables-utils)) Index: package/kernel/modules/netfilter.mk === --- package/kernel/modules/netfilter.mk (revision 15354) +++ package/kernel/modules/netfilter.mk (working copy) @@ -1,5 +1,5 @@ # -# Copyright (C) 2006-2008 OpenWrt.org +# Copyright (C) 2006-2009 OpenWrt.org # # This is free software, licensed under the GNU General Public License v2. # See /LICENSE for more information. @@ -417,13 +417,16 @@ SUBMENU:=$(NF_MENU) TITLE:=Netfilter LOG over NFNETLINK interface DEPENDS:=...@linux_2_6 +kmod-nfnetlink - FILES:=$(LINUX_DIR)/net/netfilter/nfnetlink_log.$(LINUX_KMOD_SUFFIX) - KCONFIG:=CONFIG_NETFILTER_NETLINK_LOG - AUTOLOAD:=$(call AutoLoad,48,nfnetlink_log) + KCONFIG:=$(KCONFIG_NFNETLINK_LOG) + FILES:=$(foreach mod,$(NFNETLINK_LOG-m
Re: [OpenWrt-Devel] External cross toolchain
Any objections committing the patch to trunk ? -- Nico Nico wrote: Luigi 'Comio' Mantellini wrote: Thanks Nico, I will integrate asap on my experimental tree. I noticed a mistake row 262: + ifndef ($(CONFIG_NATIVE_TOOLCHAIN),) should be: + ifneq ($(CONFIG_NATIVE_TOOLCHAIN),) You're right, there was a couple of mistakes in my previous patch. I updated it [1]. Anyway, it should be great if a toolchain prepared using OpenWRT can be exported to others developers. Have you tried building the SDK? It should embed the toolchain (and the set of files required to build packages). 1. http://nico-and-co.net/void/patches/openwrt-r14216-external_toolchain_v3.diff -- Nico On Monday 26 January 2009 18:36:32 Nico wrote: Hi Luigi, I have a patch [1] for external toolchains support, it will allow you to select your target name (powerpc-unknow-linux-gnu), toolchain commands prefix, toolchain binaries libraries path (for toolchains installed in unusual locations and needing custom PATH LD_LIBRARY_PATH). Let me know if it works for you :) 1. http://nico-and-co.net/void/patches/openwrt-r14204-external_toolchain.patch -- Nico Luigi 'Comio' Mantellini wrote: Hi ML, I need your help to understand the actual status of external toolchain support. In my environment, there are a lot of developers that works on an building environment openwrt-based. Openwrt is a good choice to manage my builds and : I am happy to have chosen one year ago. The big problem that I observed is that OpenWRT doesn't support in a clean-way the external toolchains. the NATIVE_TOOLCHAIN option seems to not resolve my problems because it disables CROSS_COMPILE defines and I don't like the openwrt behaviour when this option is enabled. I want understand if are there anybody that shares my observation (or I'm not able to use native_toolchain in best way) and if a work on this topic can be appreciated by community. Kindly, give me any suggestion or opinion in order to understand what is needed to do and what I can do. thanks in advance, luigi ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] External cross toolchain
Luigi 'Comio' Mantellini wrote: Thanks Nico, I will integrate asap on my experimental tree. I noticed a mistake row 262: + ifndef ($(CONFIG_NATIVE_TOOLCHAIN),) should be: + ifneq ($(CONFIG_NATIVE_TOOLCHAIN),) You're right, there was a couple of mistakes in my previous patch. I updated it [1]. Anyway, it should be great if a toolchain prepared using OpenWRT can be exported to others developers. Have you tried building the SDK? It should embed the toolchain (and the set of files required to build packages). 1. http://nico-and-co.net/void/patches/openwrt-r14216-external_toolchain_v3.diff -- Nico On Monday 26 January 2009 18:36:32 Nico wrote: Hi Luigi, I have a patch [1] for external toolchains support, it will allow you to select your target name (powerpc-unknow-linux-gnu), toolchain commands prefix, toolchain binaries libraries path (for toolchains installed in unusual locations and needing custom PATH LD_LIBRARY_PATH). Let me know if it works for you :) 1. http://nico-and-co.net/void/patches/openwrt-r14204-external_toolchain.patch -- Nico Luigi 'Comio' Mantellini wrote: Hi ML, I need your help to understand the actual status of external toolchain support. In my environment, there are a lot of developers that works on an building environment openwrt-based. Openwrt is a good choice to manage my builds and : I am happy to have chosen one year ago. The big problem that I observed is that OpenWRT doesn't support in a clean-way the external toolchains. the NATIVE_TOOLCHAIN option seems to not resolve my problems because it disables CROSS_COMPILE defines and I don't like the openwrt behaviour when this option is enabled. I want understand if are there anybody that shares my observation (or I'm not able to use native_toolchain in best way) and if a work on this topic can be appreciated by community. Kindly, give me any suggestion or opinion in order to understand what is needed to do and what I can do. thanks in advance, luigi ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] External cross toolchain
Hi Luigi, I have a patch [1] for external toolchains support, it will allow you to select your target name (powerpc-unknow-linux-gnu), toolchain commands prefix, toolchain binaries libraries path (for toolchains installed in unusual locations and needing custom PATH LD_LIBRARY_PATH). Let me know if it works for you :) 1. http://nico-and-co.net/void/patches/openwrt-r14204-external_toolchain.patch -- Nico Luigi 'Comio' Mantellini wrote: Hi ML, I need your help to understand the actual status of external toolchain support. In my environment, there are a lot of developers that works on an building environment openwrt-based. Openwrt is a good choice to manage my builds and : I am happy to have chosen one year ago. The big problem that I observed is that OpenWRT doesn't support in a clean-way the external toolchains. the NATIVE_TOOLCHAIN option seems to not resolve my problems because it disables CROSS_COMPILE defines and I don't like the openwrt behaviour when this option is enabled. I want understand if are there anybody that shares my observation (or I'm not able to use native_toolchain in best way) and if a work on this topic can be appreciated by community. Kindly, give me any suggestion or opinion in order to understand what is needed to do and what I can do. thanks in advance, luigi ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [Patch] Support for newer Sierra UMTS cards
Dirk Nehring wrote: these cards are already included in 2.6.27, but needed in older kernel (2.6.25, 2.6.26). Easy patch, please apply. Applied in [12447], thanks! -- Nico ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] use the in-kernel hostap-driver
Hi Alexandros, Alexandros C. Couloumbis a écrit : According to the hostap driver author, : http://hostap.epitest.fi/ Host AP driver was added into the main kernel tree in Linux v2.6.14. The version in the kernel tree should be used instead of this external hostap-driver package. The external releases are only for older kernel versions and all the future development will be in the main kernel tree. This patch enebles the in-kernel hostap driver. the package/hostap-driver has to be removed first. Your patch is not needed, using in-kernel hostap modules is exactly what is being done on a 2.6 target in package/hostap-driver. -- Nico ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Problems building glib
Michael Geddes wrote: There's some weirdness in the Makefile I just don't understand (snippet below). What on earth is this trying to achieve!? Doing a make install clean in the 'Configure' target seems a rather strange thing to be doing. I might just see if I can not compile this. //.ichael G --8--- define Build/Configure mkdir -p $(PKG_BUILD_DIR)/build/$(GNU_HOST_NAME) ( cd $(PKG_BUILD_DIR); CONFIG_SITE= \ ./configure \ --target=$(GNU_HOST_NAME) \ --host=$(GNU_HOST_NAME) \ --build=$(GNU_HOST_NAME) \ --prefix=$(PKG_BUILD_DIR)/build/$(GNU_HOST_NAME) \ --disable-shared \ --enable-static \ --enable-debug=no \ ); $(MAKE) -C $(PKG_BUILD_DIR) install clean $(call Build/Configure/Default, \ --enable-shared \ --enable-static \ --enable-debug=no \ , \ CPPFLAGS=CPPFLAGS -I$(STAGING_DIR)/usr/lib/libiconv/include \ CPPFLAGS=CPPFLAGS -I$(STAGING_DIR)/usr/lib/libintl/include \ LDFLAGS=LDFLAGS -L$(STAGING_DIR)/usr/lib/libiconv/lib \ LDFLAGS=LDFLAGS -L$(STAGING_DIR)/usr/lib/libintl/lib \ glib_cv_stack_grows=no \ glib_cv_uscore=no \ ac_cv_path_GLIB_GENMARSHAL=$(PKG_BUILD_DIR)/build/$(GNU_HOST_NAME)/bin/glib-genmarshal \ ); endef -8- The build is done in 2 passes, it first builds glib for the host to have a 'glib-genmarshal' utility working on the host system, and then it builds glib for the target, telling configure to use the 'glib-genmarshal' that was just built before. -- Nico ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] libnl exporting headers if kernel 2.6.25
You can use the CompareKernelPatchVer macro, defined in ./include/kernel.mk. A typical use can be found in ./package/fuse/Makefile. Regards, -- Nico Hauke Mehrtens wrote: If kernel is *not* 2.6.23 or 2.6.24 the headers of libnl where not exported, but hostapd needs the headers to build. This patches corrects the problem. x86 image doesn't build without this patch. Or is there a better way to detect an image for kernel 2.6? -- Hauke Mehrtens ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] gettext package
Zintis wrote: Is it bug or feature that „libintl.h” is located at -I$(STAGING_DIR)/usr/lib/libintl/include and not in -I$(STAGING_DIR)/usr/include ? Hi Zintis, This is more like a feature, just to prevent other autoconf-based packages to automagically detect and use it. Regards, -- Nico ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
