Skip to content

Commit b54d49f

Browse files
tup: update to 0.8.
1 parent 3bd0364 commit b54d49f

File tree

2 files changed

+22
-18
lines changed

2 files changed

+22
-18
lines changed

srcpkgs/tup/patches/mips.patch

Lines changed: 17 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -1,22 +1,26 @@
1-
--- a/src/tup/platform.c 2018-09-27 22:18:09.000000000 +0200
2-
+++ b/src/tup/platform.c 2020-04-17 18:15:04.968819165 +0200
3-
@@ -56,6 +56,8 @@
4-
const char *tup_arch = "arm";
5-
#elif __aarch64__
6-
const char *tup_arch = "arm64";
1+
diff --git a/src/tup/platform.c b/src/tup/platform.c
2+
index 3ccc47cd..98454cef 100644
3+
--- a/src/tup/platform.c
4+
+++ b/src/tup/platform.c
5+
@@ -66,6 +66,8 @@ const char *tup_arch = "riscv32";
6+
const char *tup_arch = "loongarch64";
7+
#elif __s390x__
8+
const char *tup_arch = "s390x";
79
+#elif __mips__
810
+const char *tup_arch = "mips";
911
#else
1012
#error Unsupported cpu architecture. Please add support in tup/platform.c
1113
#endif
12-
--- a/tup.1 2018-09-27 22:18:09.000000000 +0200
13-
+++ b/tup.1 2020-04-17 18:16:08.702822453 +0200
14-
@@ -755,7 +755,7 @@
15-
TUP_PLATFORM is a special @-variable. If CONFIG_TUP_PLATFORM is not set in the tup.config file, it has a default value according to the platform that tup itself was compiled in. Currently the default value is one of "linux", "solaris", "macosx", "win32", or "freebsd".
14+
diff --git a/tup.1 b/tup.1
15+
index eaed9b9d..0840d595 100644
16+
--- a/tup.1
17+
+++ b/tup.1
18+
@@ -857,7 +857,7 @@ In this case, the @-variable "FOO" is explicitly set to "n".
19+
TUP_PLATFORM is a special @-variable. If CONFIG_TUP_PLATFORM is not set in the tup.config file, it has a default value according to the platform that tup itself was compiled in. Currently the default value is one of "linux", "solaris", "macosx", "win32", "freebsd" or "netbsd".
1620
.TP
1721
.B @(TUP_ARCH)
18-
-TUP_ARCH is another special @-variable. If CONFIG_TUP_ARCH is not set in the tup.config file, it has a default value according to the processor architecture that tup itself was compiled in. Currently the default value is one of "i386", "x86_64", "powerpc", "powerpc64", "ia64", "alpha", "sparc", "arm64", or "arm".
19-
+TUP_ARCH is another special @-variable. If CONFIG_TUP_ARCH is not set in the tup.config file, it has a default value according to the processor architecture that tup itself was compiled in. Currently the default value is one of "i386", "x86_64", "powerpc", "powerpc64", "ia64", "alpha", "sparc", "arm64", "arm", or "mips".
22+
-TUP_ARCH is another special @-variable. If CONFIG_TUP_ARCH is not set in the tup.config file, it has a default value according to the processor architecture that tup itself was compiled in. Currently the default value is one of "i386", "x86_64", "powerpc", "powerpc64", "ia64", "alpha", "sparc", "riscv32", "riscv64", "arm64", "arm" or "s390x".
23+
+TUP_ARCH is another special @-variable. If CONFIG_TUP_ARCH is not set in the tup.config file, it has a default value according to the processor architecture that tup itself was compiled in. Currently the default value is one of "i386", "x86_64", "powerpc", "powerpc64", "ia64", "alpha", "sparc", "riscv32", "riscv64", "arm64", "arm", "s390x", or "mips".
2024

2125
.SH "VARIANTS"
22-
Tup supports variants, which allow you to build your project multiple times with different configurations. Perhaps the most common case is to build a release and a debug configuration with different compiler flags, though any number of variants can be used to support whatever configurations you like. Each variant is built in its own directory distinct from each other and from the source tree. When building with variants, the in-tree build is disabled. To create a variant, make a new directory at the top of the tup hierarchy and create a "tup.config" file there. For example:
26+
Tup supports variants, which allow you to build your project multiple times with different configurations. Perhaps the most common case is to build a release and a debug configuration with different compiler flags, though any number of variants can be used to support whatever configurations you like. Each variant is built in its own directory distinct from each other and from the source tree. When building with variants, the in-tree build is disabled. To create a variant, make a new directory and create a "tup.config" file there. For example:

srcpkgs/tup/template

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,15 +1,15 @@
11
# Template file for 'tup'
22
pkgname=tup
3-
version=0.7.11
4-
revision=2
5-
hostmakedepends="fuse3-devel pkg-config"
6-
makedepends="fuse3-devel pcre-devel sqlite-devel"
3+
version=0.8
4+
revision=1
5+
hostmakedepends="fuse3-devel pkg-config pcre2-devel"
6+
makedepends="fuse3-devel pcre2-devel sqlite-devel"
77
short_desc="File-based build system"
88
maintainer="Orphaned <orphan@voidlinux.org>"
99
license="GPL-2.0-only"
1010
homepage="http://gittup.org/tup/index.html"
1111
distfiles="https://github.com/gittup/${pkgname}/archive/v${version}.tar.gz"
12-
checksum=be24dff5f1f32cc85c73398487a756b4a393adab5e4d8500fd5164909d3e85b9
12+
checksum=45ca35c4c1d140f3faaab7fabf9d68fd9c21074af2af9a720cff4b27cab47d07
1313

1414
do_configure() {
1515
sed -i "s/git describe/echo ${version}/" src/tup/link.sh

0 commit comments

Comments
 (0)