1
0
Fork 0
mirror of https://gitlab.alpinelinux.org/alpine/aports.git synced 2025-07-23 19:25:25 +03:00
aports/testing/tup/s390x_risc3264_support.patch
Prokop Randacek 3d3d3f1fc9 testing/tup: new aport
https://gittup.org/tup
A file-based build system
2023-03-06 14:09:05 +01:00

30 lines
2.3 KiB
Diff

diff --git a/src/tup/platform.c b/src/tup/platform.c
index f0e2bccd..eb39de48 100644
--- a/src/tup/platform.c
+++ b/src/tup/platform.c
@@ -58,6 +58,12 @@ const char *tup_arch = "sparc";
const char *tup_arch = "arm";
#elif __aarch64__
const char *tup_arch = "arm64";
+#elif __s390x__
+const char *tup_arch = "s390x";
+#elif (__riscv || __riscv__) && __riscv_xlen == 64
+const char *tup_arch = "riscv64";
+#elif (__riscv || __riscv__) && __riscv_xlen == 32
+const char *tup_arch = "riscv32";
#else
#error Unsupported cpu architecture. Please add support in tup/platform.c
#endif
diff --git a/tup.1 b/tup.1
index 208629fe..2ebc264d 100644
--- a/tup.1
+++ b/tup.1
@@ -765,7 +765,7 @@ In this case, the @-variable "FOO" is explicitly set to "n".
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".
.TP
.B @(TUP_ARCH)
-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".
+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", "s390x", "riscv32" or "riscv64".
.SH "VARIANTS"
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: