2006-08-08 14:42:48 +00:00
|
|
|
#
|
|
|
|
|
# Copyright (C) 2006 OpenWrt.org
|
|
|
|
|
#
|
|
|
|
|
# This is free software, licensed under the GNU General Public License v2.
|
|
|
|
|
# See /LICENSE for more information.
|
|
|
|
|
#
|
|
|
|
|
|
|
|
|
|
include $(TOPDIR)/rules.mk
|
|
|
|
|
|
|
|
|
|
PKG_NAME:=socat
|
[PATCH] Update and FIX socat
socat was bugged for ages now. It does compile, so probably no one
noticed. While running through its configure script, the build process
complains about some missing variables and gives a hint, that the user
should supply them manually. This does ONLY happen in a cross compiling
environment, otherwise the configure script guesses them right. I don't
know the purpose of these variables exactly, but they seem to be OS
dependent and NOT hardware dependent. I tested this on various
architectures and they were all the same, as long as linux is involved.
So I think its safe to specify them in the Makefile.
The point why they're important, is simply that socat compiles, but
exits with some sort of error right after invocation, if they weren't
present at compile time. There are numerous tickets around concerning
this bug. Newer Versions of socat won't even compile if they're missing,
maybe thats why it's kinda outdated by now.
However, this little patch should fix it.
Signed-off-by: Hendrik Bartusch <bartusch@exoz.net>
git-svn-id: svn://svn.openwrt.org/openwrt/packages@26728 3c298f89-4303-0410-b956-a3cf2f4a3e73
2011-04-19 19:14:02 +00:00
|
|
|
PKG_VERSION:=1.7.1.3
|
2009-01-08 13:48:48 +00:00
|
|
|
PKG_RELEASE:=2
|
2006-08-08 14:42:48 +00:00
|
|
|
|
|
|
|
|
PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.bz2
|
2006-10-30 13:51:50 +00:00
|
|
|
PKG_SOURCE_URL:=http://www.dest-unreach.org/socat/download/
|
[PATCH] Update and FIX socat
socat was bugged for ages now. It does compile, so probably no one
noticed. While running through its configure script, the build process
complains about some missing variables and gives a hint, that the user
should supply them manually. This does ONLY happen in a cross compiling
environment, otherwise the configure script guesses them right. I don't
know the purpose of these variables exactly, but they seem to be OS
dependent and NOT hardware dependent. I tested this on various
architectures and they were all the same, as long as linux is involved.
So I think its safe to specify them in the Makefile.
The point why they're important, is simply that socat compiles, but
exits with some sort of error right after invocation, if they weren't
present at compile time. There are numerous tickets around concerning
this bug. Newer Versions of socat won't even compile if they're missing,
maybe thats why it's kinda outdated by now.
However, this little patch should fix it.
Signed-off-by: Hendrik Bartusch <bartusch@exoz.net>
git-svn-id: svn://svn.openwrt.org/openwrt/packages@26728 3c298f89-4303-0410-b956-a3cf2f4a3e73
2011-04-19 19:14:02 +00:00
|
|
|
PKG_MD5SUM:=2081987fb0cb0290b8105574058cb329
|
2006-08-08 14:42:48 +00:00
|
|
|
|
2010-02-18 13:10:21 +00:00
|
|
|
PKG_INSTALL:=1
|
|
|
|
|
|
2006-08-08 14:42:48 +00:00
|
|
|
include $(INCLUDE_DIR)/package.mk
|
|
|
|
|
|
|
|
|
|
define Package/socat
|
|
|
|
|
SECTION:=net
|
|
|
|
|
CATEGORY:=Network
|
2007-06-13 20:56:25 +00:00
|
|
|
DEPENDS:=+libpthread
|
2006-08-08 14:42:48 +00:00
|
|
|
TITLE:=A multipurpose relay (SOcket CAT)
|
|
|
|
|
URL:=http://www.dest-unreach.org/socat/
|
|
|
|
|
endef
|
|
|
|
|
|
2007-10-14 04:32:56 +00:00
|
|
|
define Package/socat/description
|
2008-07-06 11:27:01 +00:00
|
|
|
SoCat (for SOcket CAT) establishes two bidirectional byte streams and
|
2007-10-14 04:32:56 +00:00
|
|
|
transfers data between them.
|
2008-07-06 11:27:01 +00:00
|
|
|
Data channels may be files, pipes, devices (terminal or modem, etc.), or
|
|
|
|
|
sockets (Unix, IPv4, IPv6, raw, UDP, TCP, SSL). It provides forking,
|
|
|
|
|
logging and tracing, different modes for interprocess communication and
|
2007-10-14 04:32:56 +00:00
|
|
|
many more options.
|
|
|
|
|
endef
|
|
|
|
|
|
2006-08-08 14:42:48 +00:00
|
|
|
define Build/Configure
|
2006-10-30 13:51:50 +00:00
|
|
|
$(call Build/Configure/Default, \
|
|
|
|
|
--disable-libwrap \
|
|
|
|
|
--disable-readline \
|
2007-06-13 20:56:25 +00:00
|
|
|
--disable-openssl \
|
2009-01-08 13:48:48 +00:00
|
|
|
--enable-termios \
|
2006-10-30 13:51:50 +00:00
|
|
|
, \
|
|
|
|
|
sc_cv_termios_ispeed="no" \
|
[PATCH] Update and FIX socat
socat was bugged for ages now. It does compile, so probably no one
noticed. While running through its configure script, the build process
complains about some missing variables and gives a hint, that the user
should supply them manually. This does ONLY happen in a cross compiling
environment, otherwise the configure script guesses them right. I don't
know the purpose of these variables exactly, but they seem to be OS
dependent and NOT hardware dependent. I tested this on various
architectures and they were all the same, as long as linux is involved.
So I think its safe to specify them in the Makefile.
The point why they're important, is simply that socat compiles, but
exits with some sort of error right after invocation, if they weren't
present at compile time. There are numerous tickets around concerning
this bug. Newer Versions of socat won't even compile if they're missing,
maybe thats why it's kinda outdated by now.
However, this little patch should fix it.
Signed-off-by: Hendrik Bartusch <bartusch@exoz.net>
git-svn-id: svn://svn.openwrt.org/openwrt/packages@26728 3c298f89-4303-0410-b956-a3cf2f4a3e73
2011-04-19 19:14:02 +00:00
|
|
|
sc_cv_sys_crdly_shift=9 \
|
|
|
|
|
sc_cv_sys_tabdly_shift=11 \
|
|
|
|
|
sc_cv_sys_csize_shift=4 \
|
2006-10-30 13:51:50 +00:00
|
|
|
)
|
2006-08-08 14:42:48 +00:00
|
|
|
endef
|
|
|
|
|
|
2010-02-18 13:10:21 +00:00
|
|
|
define Package/socat/install
|
2006-11-23 00:29:07 +00:00
|
|
|
$(INSTALL_DIR) $(1)/usr/bin
|
2007-12-09 18:59:01 +00:00
|
|
|
$(INSTALL_BIN) $(PKG_INSTALL_DIR)/usr/bin/socat $(1)/usr/bin/
|
2006-08-08 14:42:48 +00:00
|
|
|
endef
|
|
|
|
|
|
|
|
|
|
$(eval $(call BuildPackage,socat))
|