This fixes the issue where clippy failed to build for arm causing that
release to be incomplete.
We remove the host files from the install directory to reduce the final
size is minimal.
Update the android sdk build tools from 27.0.3 to 28.0.1, bringing
in d8 which is replacing dx.
This needs an update of the Docker image, so run scripts/update-docker.sh
to update it.
By defining CONTAINER_NAME one can now build from multiple containers:
CONTAINER_NAME=builder1 ./scripts/run-docker.sh
CONTAINER_NAME=builder2 ./scripts/run-docker.sh
...
* update ndk to 17
* bump NDK version in setup-android script
* libnl: fix for ndk r17
* libpixman: use clang's __builtin_shufflevector instead of __builtin_shuffle (#1)
Required to make package build with ndk17.
* fix as for arm
* ndk17 still uses ld.bfd on aarch64
* use -fno-integrated-as for clang only
* glib: remove patch unnecessary after ndk17
* torsocks: remove unneeded patch after ndk17
* subversion: fix build as clang++ now errors out for mismatched flags
* libpulseaudio: fix build with ndk17
https://github.com/termux/termux-packages/pull/2415#issuecomment-388296684
* gst-plugins-good: disable video4linux2
ioctl is defined as __overloadable in ndk17 headers which
conflicts with v4l2object's member ioctl
* libzmq: disable Werror to build with ndk17
* ltrace: hardcode symbol not available in ndk17
* busybox: build with clang for all arches except arm
* dropbear: build with clang instead of gcc
* gnupg: build with clang instead of gcc
* openssl: use clang for all arches except arm
* picolisp: build with clang instead of gcc
* valgrind: use clang on all arches except aarch64
* Revert "gst-plugins-good: disable video4linux2"
This reverts commit 43850b81ccf60033c25cb13dfd326c1b0528773a.
Already applied on base branch.
* libllvm: use default arm triple
Existing Vagrantfile lead to some problems here during provisioning:
1. setup-ubuntu.sh would fail
and after:
2. build-all.sh would run out of disk space
3. build-all.sh would exit due to permission issues
Issue 1 can be addressed by running sudo apt-get update before setup-ubuntu.sh in the Vagrantfile.
One way to address issue 2 is to use the vagrant-disksize plugin:
https://github.com/sprotheroe/vagrant-disksize
It can be installed by:
vagrant plugin install vagrant-disksize
Then modifying Vagrantfile to contain a line like:
config.disksize.size = '50GB'
causes the first partition to be enlarged to 50GB during provisioning. Combined with an appropriate invocation of resize2fs:
sudo resize2fs /dev/sda1
so that the filesystem in the partition is resized, the disk space issue seems alleviated.
Issue 3 can be addressed by changing the user from 'ubuntu' to 'vagrant' in the Vagrantfile -- at least that's what worked here.
Fredrik Fornwall
Henrik Grimler
Kevin Cotugno
Stephen
Laurent Arnoud
Henrik Grimler
Vishal Biswas
tomty89
sogaiu