- Sep 16, 2018
-
-
Tim-Philipp Müller authored
-
- Sep 07, 2018
- Aug 09, 2018
-
-
Nirbheek Chauhan authored
Upstream didn't support HTTPS, and is dead now. https://lwn.net/Articles/762264/
-
- Aug 07, 2018
-
-
Nirbheek Chauhan authored
Which is why we have shell.which.
-
Nirbheek Chauhan authored
The commit was cherry-picked from the master commit and pushed without fixing it so that it works with Python 2
-
Nirbheek Chauhan authored
It hangs randomly during configure, and makes unattended builds annoying. This is the workaround that people have been doing manually for years on Windows. Eventually, we will get rid of this entirely once we move to Meson.
-
Nirbheek Chauhan authored
Also move gettext-tools earlier in the list of build tools so it's available ASAP.
-
Nirbheek Chauhan authored
The curl that ships with the latest Windows 10 works fine, but people often have bad curl installations which can make bootstrap fail. Always Use urllib2 on Windows, and we should move to using it exclusively on all platforms.
-
- Jul 27, 2018
-
-
Nirbheek Chauhan authored
Release is done, and we should build the HEAD of the 1.14 branch again
-
- Jul 21, 2018
-
-
Nirbheek Chauhan authored
check_call doesn't always inherit the current environment, so it would run the wrong Perl because our PATH changes were ignored. However, this only happened in a `package` run where some other recipe was built beforehand. Instead, use `which()` now so that we read PATH directly. Also don't use environment variables to communicate the perl path, we already have that information in self.config.
-
- Jul 20, 2018
-
-
Jan Schmidt authored
Import a patch from upstream pixman to disable use of GCC __builtin_shuffle that was removed in Clang 5.0 Fixes the MacOS/iOS build
-
Jan Schmidt authored
-
Jan Schmidt authored
-
Edward Hervey authored
-
Tim-Philipp Müller authored
-
- Jun 30, 2018
-
-
-
Added Platform.Linux in or to Platform.android, before the check for Architecture.ARMv7. https://bugzilla.gnome.org/show_bug.cgi?id=796684
-
- Jun 22, 2018
-
-
-
Tim-Philipp Müller authored
-
Tim-Philipp Müller authored
Clone from github mirror since it's unclear what the https location is for the libav.org git repo. https://bugzilla.gnome.org/show_bug.cgi?id=743235
-
- May 19, 2018
-
-
Sebastian Dröge authored
-
- May 17, 2018
-
-
Tim-Philipp Müller authored
git protocol can be problematic in environments with restricted network access and is also less secure. https://bugzilla.gnome.org/show_bug.cgi?id=743235
-
Tim-Philipp Müller authored
No need to build them.
-
Tim-Philipp Müller authored
-
Tim-Philipp Müller authored
-
- May 04, 2018
-
-
For non-cross-compilation use-cases, we might end up building libraries in cerbero that should *not* be used by host commands. The case in point was the host "git" command picking up a mix of system libraries and of libraries that we built in cerbero. To avoid that, before running git commands switch to an environment which uses the "host" LD_LIBRARY_PATH environment https://bugzilla.gnome.org/show_bug.cgi?id=794830
-
- Apr 25, 2018
-
-
Sebastian Dröge authored
We have to properly check which of the prefixes is a parent directory of our file, not via string comparisions. Otherwise "/foo/x86" and "/foo/x86_64" or both considered parents of "/foo/x86_64/bar" and which one is stripped from the path depends on the order. Thanks to Mathieu Duponchelle for the non-ugly generator-based function for doing this check.
-
- Apr 17, 2018
- Apr 12, 2018
-
-
Matthew Waters authored
Fixes build error: Undefined symbols for architecture x86_64: "__aesni_cbc_encrypt", referenced from: _aes_encrypt in libaccelerated.a(aes-cbc-x86-aesni.o) _aes_decrypt in libaccelerated.a(aes-cbc-x86-aesni.o) "__aesni_ctr32_encrypt_blocks", referenced from: _aes_gcm_encrypt in libaccelerated.a(aes-gcm-x86-pclmul-avx.o) _aes_gcm_decrypt in libaccelerated.a(aes-gcm-x86-pclmul-avx.o) _aes_gcm_encrypt in libaccelerated.a(aes-gcm-x86-pclmul.o) _aes_gcm_decrypt in libaccelerated.a(aes-gcm-x86-pclmul.o) "__aesni_ecb_encrypt", referenced from: _x86_aes_encrypt in libaccelerated.a(aes-ccm-x86-aesni.o) _x86_aes_encrypt in libaccelerated.a(aes-gcm-x86-aesni.o) _aes_gcm_cipher_setkey in libaccelerated.a(aes-gcm-x86-pclmul-avx.o) _aes_gcm_setiv in libaccelerated.a(aes-gcm-x86-pclmul-avx.o) _aes_gcm_cipher_setkey in libaccelerated.a(aes-gcm-x86-pclmul.o) _aes_gcm_setiv in libaccelerated.a(aes-gcm-x86-pclmul.o) "__aesni_set_decrypt_key", referenced from: _aes_cipher_setkey in libaccelerated.a(aes-cbc-x86-aesni.o) "__aesni_set_encrypt_key", referenced from: _aes_cipher_setkey in libaccelerated.a(aes-cbc-x86-aesni.o) _aes_ccm_cipher_setkey in libaccelerated.a(aes-ccm-x86-aesni.o) _aes_gcm_cipher_setkey in libaccelerated.a(aes-gcm-x86-aesni.o) _aes_gcm_cipher_setkey in libaccelerated.a(aes-gcm-x86-pclmul-avx.o) _aes_gcm_cipher_setkey in libaccelerated.a(aes-gcm-x86-pclmul.o) ld: symbol(s) not found for architecture x86_64 clang: error: linker command failed with exit code 1 (use -v to see invocation)
-
Matthew Waters authored
-
Matthew Waters authored
Linking an android application for armv7 would result in undefined references with the 1.1.0h update because it seems configure can't seem to detect the max available arm architecture anymore. Fix by specifying on the configure command crypto/evp/e_aes.c:1084: error: undefined reference to 'aes_v8_set_encrypt_key' crypto/evp/e_aes.c:1044: error: undefined reference to 'aes_v8_set_decrypt_key' crypto/evp/e_aes.c:1060: error: undefined reference to 'aes_v8_encrypt' crypto/evp/e_aes.c:1060: error: undefined reference to 'aes_v8_ctr32_encrypt_blocks' crypto/evp/e_aes.c:1060: error: undefined reference to 'aes_v8_cbc_encrypt' crypto/evp/e_aes.c:1060: error: undefined reference to 'bsaes_ctr32_encrypt_blocks' crypto/evp/e_aes.c:1060: error: undefined reference to 'aes_v8_decrypt' crypto/evp/e_aes.c:1060: error: undefined reference to 'bsaes_cbc_encrypt' crypto/evp/e_aes.c:1831: error: undefined reference to 'aes_v8_set_decrypt_key' crypto/evp/e_aes.c:1840: error: undefined reference to 'aes_v8_set_encrypt_key' crypto/evp/e_aes.c:1823: error: undefined reference to 'aes_v8_set_encrypt_key' crypto/evp/e_aes.c:1851: error: undefined reference to 'aes_v8_decrypt' crypto/evp/e_aes.c:1851: error: undefined reference to 'aes_v8_encrypt' crypto/evp/e_aes.c:1851: error: undefined reference to 'bsaes_xts_encrypt' crypto/evp/e_aes.c:1851: error: undefined reference to 'bsaes_xts_decrypt' crypto/evp/e_aes.c:1446: error: undefined reference to 'aes_v8_set_encrypt_key' crypto/evp/e_aes.c:1504: error: undefined reference to 'bsaes_ctr32_encrypt_blocks' crypto/evp/e_aes.c:1504: error: undefined reference to 'aes_v8_encrypt' crypto/evp/e_aes.c:1504: error: undefined reference to 'aes_v8_ctr32_encrypt_blocks' crypto/evp/e_aes.c:2068: error: undefined reference to 'aes_v8_encrypt' crypto/evp/e_aes.c:2480: error: undefined reference to 'aes_v8_set_decrypt_key' crypto/evp/e_aes.c:2525: error: undefined reference to 'aes_v8_decrypt' crypto/modes/gcm128.c:790: error: undefined reference to 'gcm_init_neon' crypto/modes/gcm128.c:785: error: undefined reference to 'gcm_gmult_neon' crypto/modes/gcm128.c:785: error: undefined reference to 'gcm_ghash_neon' crypto/armcap.c:53: error: undefined reference to '_armv7_tick' crypto/armcap.c:167: error: undefined reference to '_armv7_neon_probe' crypto/armcap.c:181: error: undefined reference to '_armv8_sha256_probe' crypto/armcap.c:186: error: undefined reference to '_armv7_tick' crypto/armcap.c:177: error: undefined reference to '_armv8_sha1_probe' crypto/armcap.c:170: error: undefined reference to '_armv8_pmull_probe' crypto/armcap.c:173: error: undefined reference to '_armv8_aes_probe'
-
Matthew Waters authored
It fails to link inside an android application with relocation errors
-
Matthew Waters authored
It fails linking in an android application with relocation problems.
-
Matthew Waters authored
Modifying gnutls was chosen because for other architectures, the names are already slightly different and don't conflict with openssl whereas openssl's symbol names are all the same regardless of architecture. gnutls also only has 2 accelarated architectures to change compared to openssl's 5+.
-
Matthew Waters authored
It has problems with relocations when linking an app.
-
Matthew Waters authored
-
Matthew Waters authored
Fails to link with Android NDK's r16 binutils NDK bug report: https://github.com/android-ndk/ndk/issues/337
-
And move uri from ftp to https.
-
- Mar 23, 2018
-
-
Tim-Philipp Müller authored
-
Jan Schmidt authored
-