snailed
/
void-packages
2
0
Fork 0
Code Issues 1 Pull Requests 2 Actions Activity
void-packages/common/wrappers/uname.sh

14 lines
298 B
Bash
Raw Permalink Normal View History

common/wrappers: add date and uname wrappers. uname: overwrites the hostname in command uname with the string 'void'. date: uses the timestamp read from SOURCE_DATE_EPOCH as date.
2016-03-03 11:31:57 +01:00
#!/bin/sh
uname=$(/usr/bin/uname $@)
common: fix exit status of uname wrapper
2021-01-25 02:56:55 +01:00
rv=$?
uname.sh: fix cross `uname -m` when XBPS_ARCH is reseted From commit cf6e6f14d3, (wrappers/uname: report correct machine type on ethereal, 2020-02-10). Some template use `env -i` to reset environment variable for building host's binary file, thus the wrapped `uname -m` reports empty strings. Fix it by falling back to the value reported by `/usr/bin/uname -m`. We don't expect people cross-compile from i686-ethereal-chroot on top of x86_64 machine, it was expected to use for travis to native compile i686 only.
2020-03-23 11:34:39 +01:00
uname_m=$(/usr/bin/uname -m)
arch=${XBPS_ARCH%-musl}
# if XBPS_ARCH was reseted by `env -i` use original `/usr/bin/uname -m`
: ${arch:=$uname_m}
wrappers/uname: report correct machine type on ethereal We're using Ethereal chroot style on Travis CI. In that chroot style, `uname -m` reports x86_64 even if we're bootstrapped with i686 systems. Some i686 build that employ `uname -m` is failing on Travis CI, e.g: https://travis-ci.org/void-linux/void-packages/jobs/648010517#L5787 Change `uname` output to make Travis Output meaningful for i686.
2020-02-10 07:59:34 +01:00
echo "$uname" |
sed "s/\(^\| \)$(/usr/bin/uname -n)\($\| \)/\1void\2/" |
uname.sh: fix cross `uname -m` when XBPS_ARCH is reseted From commit cf6e6f14d3, (wrappers/uname: report correct machine type on ethereal, 2020-02-10). Some template use `env -i` to reset environment variable for building host's binary file, thus the wrapped `uname -m` reports empty strings. Fix it by falling back to the value reported by `/usr/bin/uname -m`. We don't expect people cross-compile from i686-ethereal-chroot on top of x86_64 machine, it was expected to use for travis to native compile i686 only.
2020-03-23 11:34:39 +01:00
sed "s/$uname_m/$arch/"
wrappers/uname: report correct machine type on ethereal We're using Ethereal chroot style on Travis CI. In that chroot style, `uname -m` reports x86_64 even if we're bootstrapped with i686 systems. Some i686 build that employ `uname -m` is failing on Travis CI, e.g: https://travis-ci.org/void-linux/void-packages/jobs/648010517#L5787 Change `uname` output to make Travis Output meaningful for i686.
2020-02-10 07:59:34 +01:00
common/wrappers/uname.sh: return with correct exit code.
2016-03-03 12:05:28 +01:00
exit $rv