The "build" script was replacing a ~DATE~ with current date.
Now it uses $(SOURCE_DATE_EPOCH).
Fixes#17848
Signed-off-by: Luiz Angelo Daros de Luca <luizluca@gmail.com>
./configure scripts compiles&runs test so it detects darwin
C-functions and defines that can not be used for Linux target.
This patches expicitly specifies Linux-specific parameters that
can not be detected correctly on Darwin.
This patch removes 010-mandoc-1.14.5-fix-gnu-make.patch. mandoc
provides its own way to redefine specific parameters (using
configure.local file). Defines from this patch are moved to
generated configure.local file.
CONFIGURE_VARS are removed by this patch due to ./configure script
does not use ENV vars specified by CONFIGURE_VARS
This commit does not change compilation on Linux hosts (the resulted
binary is exactly the same as before applying this commit). Binary
compiled on MacOS host is exactly the same as compiled on Linux.
Files generated by ./configure (config.h and Makefile.local) are
exactly the same on Linux and MacOS build hosts
Signed-off-by: Sergey V. Lobanov <sergey@lobanov.in>
This includes fixes for:
* CVE-2022-23772: math/big: Rat.SetString may consume large amount of
RAM and crash
* CVE-2022-23806: crypto/elliptic: IsOnCurve returns true for invalid
field elements
Signed-off-by: Jeffery To <jeffery.to@gmail.com>
Fallback to use 'sdcard' image in case there is neither 'sysupgrade'
nor 'combined' image available.
This allows using 'auc' on targets where 'sdcard' image is also used
for sysupgrade (such as some mvebu-based devices with eMMC).
Signed-off-by: Daniel Golle <daniel@makrotopia.org>
Calling 'block umount' results in *all* devices listed in
/etc/config/fstab being unmounted.
Just call 'umount /dev/$devname' directly instead as that has the
desired effect.
Signed-off-by: Daniel Golle <daniel@makrotopia.org>
Accept both 'y' and 'Y' as positive confirmation when asking the user
if auc should proceed with requesting and installing an upgrade.
Signed-off-by: Daniel Golle <daniel@makrotopia.org>
Fixed the affected issue in the latest commit
daemon.err avahi-daemon[xxx]: mkdir("/run/avahi-daemon/"): No such file or directory
Signed-off-by: Hirokazu MORIKAWA <morikw2@gmail.com>
ipvsadm build fails on macos due to libipvs Makefiles uses system
`ar` that is not compatible with the objectes generated by OpenWrt
GCC Toolchain.
This commit adds patch to allow ar redefining
This commit modifes an old patch (removing CC=gcc is not required
due to it is redefinable)
Signed-off-by: Sergey V. Lobanov <sergey@lobanov.in>
In the build environment the autotools finds the `passwd` binary in
/usr/bin. But in the target image it is available under /bin instead.
Manually set the path to `passwd` binary to `/bin/passwd`
Signed-off-by: Rucke Teg <rucketeg@protonmail.com>
There is no need to remove root password from /etc/shadow as the
password in the file is blank anyway in the failsafe mode.
Signed-off-by: Rucke Teg <rucketeg@protonmail.com>
This seems to happen only on some distributions (Void, Arch):
/usr/lib/libgcc_s.so.1: file not recognized: file format not recognized
collect2: error: ld returned 1 exit status
libtool: error: error: relink 'libdns_sd.la' with the above command before installing it
Signed-off-by: Michal Vasilek <michal.vasilek@nic.cz>
DoH is enabled by default, but disabling it removes the need to link
against libnghttp2, which may be desirable more constrained
environments.
Signed-off-by: Noah Meyerhans <frodo@morgul.net>
tesseract build script checks /proc/cpuinfo file, but this file is
not exist or darwin. This check is used for getting optimized build
flags depends on CPU. This feature does not work in cross-compile
case and should be explicitly disabled.
This patch disables CPU detection using cmake option
BUILD_TRAINING_TOOLS=OFF.
Generated binaries (aarch64 target) are exactly the same on
Ubuntu 20.04 x86_64 and MacOS 11.6 arm64. Binaries generated on
Linux build host are not changed (the same checksums before and
after applying this patch).
Signed-off-by: Sergey V. Lobanov <sergey@lobanov.in>
When switching from cmake to autotools, the wrong logging was used for
the verbose compilations option. This commit fixes that.
Signed-off-by: Florian Eckert <fe@dev.tdt.de>