about summary refs log tree commit diff
path: root/src/ci/docker/scripts/freebsd-toolchain.sh
AgeCommit message (Collapse)AuthorLines
2025-08-13Use ci-mirrors for binutils in freebsd-toolchain.shNikita Popov-1/+3
2025-02-05Revert "CI: build FreeBSD artifacts on FreeBSD 13.4"Alan Somers-3/+3
This reverts commit cf34545720986d99712e3b542e8f395360c75095. That commit led to a regression of https://github.com/rust-lang/rust/issues/132185 . So my analysis that the problem lay in FreeBSD 13.2's specific LLVM version was clearly wrong. Revert that commit until we can figure out the real root cause. Fixes #132185
2024-10-28CI: build FreeBSD artifacts on FreeBSD 13.4Alan Somers-3/+3
13.2 is EoL, and 13.3 will be EoL too in about 2 months. Plus, both suffer from a bug in LLVM's libunwind. It causes a segfault inside of std::backtrace::Backtrace::capture(). Fixes #132185
2024-10-27Revert "ci update freebsd version proposal, freebsd 12 being eol."David Carlier-4/+4
This reverts commit 1239c81c145d2bfb96f32856f377cd741d5c7256. Fix GH-132185 revert for now until early next year/FreeBSD 13.3 becomes EOL.
2024-09-28ci update freebsd version proposal, freebsd 12 being eol.David Carlier-4/+4
raising to the lowest still active supported freebsd version. From 13.1 (already eol too), freebsd introduces a cpu affinity layer with linux. It also introduces a api compatible copy_file_range which can be used like its linux's counterpart. The former is essential to build #120589, therefore breaks the backward compatibility with the previous FreeBSD releases.
2023-08-22ci: Update FreeBSD and illumos binutils to 2.40Fangrui Song-1/+1
The current old 2.25 seems to cause trouble to #106511. Install texinfo to dist-x86_64-freebsd/Dockerfile like other containers to fix ``` MAKEINFO doc/bfd.info /binutils/binutils-2.40/missing: 81: /binutils/binutils-2.40/missing: makeinfo: not found WARNING: 'makeinfo' is missing on your system. ```
2022-12-03std update libc version and freebsd image build dependenciesDavid CARLIER-1/+1
2022-06-10Update FreeBSD toolchain to 12.3Nikita Popov-4/+4
2021-12-15Pull in libdevstat on FreeBSDLaurențiu Nicola-1/+1
2021-11-02Pull in libkvm on FreeBSDLaurențiu Nicola-1/+1
2021-09-08update of the CI freebsd toolchainDavid Carlier-1/+1
adding libproctsta, for the upcoming libc update.
2020-11-06fix shellcheck error of SC2068Daiki Ihara-1/+1
2020-08-09Upgrade the FreeBSD toolchain to version 11.4Josh Stone-19/+5
FreeBSD 10 reached its end-of-life in October 2018, and that toolchain caused issues in the LLVM 11 upgrade (#73526) that are resolved with the toolchain from FreeBSD 11.
2019-11-12ci: move mirrors to https://ci-mirrors.rust-lang.orgPietro Albini-1/+1
2019-08-12ci: move mirrors to their standalone bucketPietro Albini-1/+1
Currently mirrors are stored in the rust-lang-ci2 S3 bucket along with CI toolchains. This is problematic for multiple reasons: - CI IAM credentials are allowed to both edit and delete those files. A malicious user gaining access to those credentials would be able to change our mirrored dependencies, possibly backdooring the compiler. - Contents of the rust-lang-ci2 bucket are disposable except for the mirrors' content. When we implement backups for S3 buckets we'd have to replicate just that part of the bucket, complicating the backup logic and increasing the chance of mistakes. A standalone bucket will be way easier to backup. This commit switches our CI to use the new rust-lang-ci-mirrors bucket.
2019-05-29Update all s3 URLs used on CI with subdomainsAlex Crichton-1/+1
Ensure that they're all forwards-compatible with AWS updates happening next year by ensuring the bucket name shows up in the domain name. Closes #61168
2019-04-04ci: Update FreeBSD tarball downloadsAlex Crichton-1/+5
These appear to have disappeared from the original server, so I acquired the contents from a different mirror and uploaded them to our S3 bucket
2018-12-25Remove licensesMark Rousskov-10/+0
2017-12-22Re-do the FreeBSD cross-builds to use Clang and libc++. Fixes #44433.Jed Davis-0/+103
The main goal here is to use FreeBSD's normal libc++, instead of statically linking the libstdc++ packaged with GCC, because that libstdc++ has bugs that cause rustc to deadlock inside LLVM. But the easiest way to use libc++ is to switch the build from GCC to Clang, and the Clang package in the Ubuntu image already knows how to cross-compile (given a sysroot and preferably cross-binutils), so the toolchain script now uses that instead of building a custom compiler. This also de-duplicates the `build-toolchain.sh` script.