Skip to contentSkip to conversation

iodine: new package

PATCH New Gustavo Zacarias 2 participants 4 messages Feb 21, 2015

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 iodine: new package

---
 package/Config.in                                  |  1 +
 .../iodine/0001-disable-systemd-and-selinux.patch  | 29 ++++++++++++++++++++++
 package/iodine/Config.in                           |  9 +++++++
 package/iodine/iodine.hash                         |  2 ++
 package/iodine/iodine.mk                           | 21 ++++++++++++++++
 5 files changed, 62 insertions(+)
 create mode 100644 package/iodine/0001-disable-systemd-and-selinux.patch
 create mode 100644 package/iodine/Config.in
 create mode 100644 package/iodine/iodine.hash
 create mode 100644 package/iodine/iodine.mk
package/Config.in +1 -0
index a93faab..2894379 100644
@@ -1102,6 +1102,7 @@ endif
 	source "package/igh-ethercat/Config.in"
 	source "package/igmpproxy/Config.in"
 	source "package/inadyn/Config.in"
+	source "package/iodine/Config.in"
 	source "package/iperf/Config.in"
 	source "package/iperf3/Config.in"
 	source "package/iproute2/Config.in"
package/iodine/0001-disable-systemd-and-selinux.patch new file +29 -0
new file mode 100644
index 0000000..965abb7
@@ -0,0 +1,29 @@
+Disable selinux and systemd support since they check for host headers.
+
+Signed-off-by: Gustavo Zacarias <[email protected]>
+
+diff -Nura iodine-0.7.0.orig/src/osflags iodine-0.7.0/src/osflags
+--- iodine-0.7.0.orig/src/osflags	2015-02-20 14:59:00.799958145 -0300
++++ iodine-0.7.0/src/osflags	2015-02-20 15:05:54.791135141 -0300
+@@ -18,8 +18,8 @@
+ 		;;
+ 		Linux)
+ 			FLAGS="";
+-			[ -e /usr/include/selinux/selinux.h ] && FLAGS="$FLAGS -lselinux";
+-			[ -e /usr/include/systemd/sd-daemon.h ] && FLAGS="$FLAGS -lsystemd-daemon";
++			#[ -e /usr/include/selinux/selinux.h ] && FLAGS="$FLAGS -lselinux";
++			#[ -e /usr/include/systemd/sd-daemon.h ] && FLAGS="$FLAGS -lsystemd-daemon";
+ 			echo $FLAGS;
+ 		;;
+ 	esac
+@@ -34,8 +34,8 @@
+ 		;;
+ 		Linux)
+ 			FLAGS="-D_GNU_SOURCE"
+-			[ -e /usr/include/selinux/selinux.h ] && FLAGS="$FLAGS -DHAVE_SETCON";
+-			[ -e /usr/include/systemd/sd-daemon.h ] && FLAGS="$FLAGS -DHAVE_SYSTEMD";
++			#[ -e /usr/include/selinux/selinux.h ] && FLAGS="$FLAGS -DHAVE_SETCON";
++			#[ -e /usr/include/systemd/sd-daemon.h ] && FLAGS="$FLAGS -DHAVE_SYSTEMD";
+ 			echo $FLAGS;
+ 		;;
+ 	esac
package/iodine/Config.in new file +9 -0
new file mode 100644
index 0000000..6962cb8
@@ -0,0 +1,9 @@
+config BR2_PACKAGE_IODINE
+	bool "iodine"
+	select BR2_PACKAGE_ZLIB
+	help
+	  iodine lets you tunnel IPv4 data through a DNS server.
+	  This can be usable in different situations where
+	  internet access is firewalled, but DNS queries are allowed.
+
+	  http://code.kryo.se/iodine/
package/iodine/iodine.hash new file +2 -0
new file mode 100644
index 0000000..94eb5aa
@@ -0,0 +1,2 @@
+# From http://code.kryo.se/iodine/
+md5	fdbf3b81cd69caf5230d76a8b039fd99	iodine-0.7.0.tar.gz
package/iodine/iodine.mk new file +21 -0
new file mode 100644
index 0000000..57deb9e
@@ -0,0 +1,21 @@
+################################################################################
+#
+# iodine
+#
+################################################################################
+
+IODINE_VERSION = 0.7.0
+IODINE_SITE = http://code.kryo.se/iodine
+IODINE_DEPENDENCIES = zlib
+IODINE_LICENSE = MIT
+IODINE_LICENSE_FILES = README
+
+define IODINE_BUILD_CMDS
+	$(MAKE) CC="$(TARGET_CC)" ARCH=$(BR2_ARCH) -C $(@D)
+endef
+
+define IODINE_INSTALL_TARGET_CMDS
+	$(MAKE) -C $(@D) install DESTDIR="$(TARGET_DIR)" prefix=/usr
+endef
+
+$(eval $(generic-package))
Signature · 1 line
2.0.5
#1 lore raw

PATCH 1/1 iodine: new package

Dear Gustavo Zacarias,

Quoted 1 line · Gustavo Zacarias

Applied to next, though I have one question, see below.

package/iodine/iodine.mk line 14

Quoted 2 lines
package/iodine/iodine.mk new file +2 -0
+define IODINE_BUILD_CMDS
+	$(MAKE) CC="$(TARGET_CC)" ARCH=$(BR2_ARCH) -C $(@D)

Is passing ARCH actually needed? I see ARCH being defined as uname -m in src/Makefile, but it doesn't seem to be used anywhere.

If it's actually used, are we sure that the values of $(BR2_ARCH) match what iodine expect as ARCH values?

Thanks!

Thomas

Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
#2 lore raw

PATCH 1/1 iodine: new package

Quoted 10 lines · Thomas Petazzoni

package/iodine/iodine.mk line 14

Quoted 2 lines
package/iodine/iodine.mk new file +2 -0
+define IODINE_BUILD_CMDS
+	$(MAKE) CC="$(TARGET_CC)" ARCH=$(BR2_ARCH) -C $(@D)

Is passing ARCH actually needed? I see ARCH being defined as uname -m in src/Makefile, but it doesn't seem to be used anywhere.

If it's actually used, are we sure that the values of $(BR2_ARCH) match what iodine expect as ARCH values?

Thanks!

It's not really required, just to cover for the cosmetic/paranoid type ;) Regards.

#3 lore raw

PATCH 1/1 iodine: new package

Dear Gustavo Zacarias,

Quoted 1 line · Gustavo Zacarias

It's not really required, just to cover for the cosmetic/paranoid type ;)

Ok, thanks.

Thomas

Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com