| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
I'm not sure I agree with this complaint - it seems like foolish
standards-wonkery - but GNU cp supports -R too and this change will
fix CI on main.
|
| |\
| |
| |
| |
| | |
Update to crunchy 0.2.4, remove exception in reproducible_build
See merge request tpo/core/arti!3073
|
| | |
| |
| |
| | |
This should no longer be necessary.
|
| |/ |
|
| | |
|
| |
|
|
|
| |
Since it's using 1.86 now, there's no reason to downgrade these
packages.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
After upgrading to rust:1.86.0-alpine3.21, we got a new error:
```
osxcross: error: cannot find libc++ headers
```
To fix this, we change the linker to
`x86_64-apple-darwin16-clang++-stdc++`.
This invokes some osxcross magic that tells it to find the C++
headers in the stdc++ location... and possibly more.
|
| |
|
|
|
| |
This is a workaround for
https://github.com/eira-fransham/crunchy/pull/17
|
| |
|
|
|
|
|
|
|
|
| |
We generally recommend that people build with --features=full IRL,
so this better matches what we're hoping they come up with.
Additionally, it will help cases like #1964, where packagers would
like to use reproducible builds as inputs to their own packages.
Closes #1964
|
| |
|
|
|
| |
This is a workaround for
https://gitlab.torproject.org/tpo/core/arti/-/issues/1335
|
| |
|
|
|
| |
This is a workaround for
https://gitlab.torproject.org/tpo/core/arti/-/issues/1335
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
osxcross tries in various ways to detect which version of the compiler
we have, which version of the OS, which C++ standard library we use, and
many other things. With this variable set, osxcross seems able to detect
the environment provided by the SDK that we use.
The error messages from osxcross is as follows:
osxcross: error: cannot find libc++ headers
osxcross: error: while detecting target
This origins from its internal target detection code in target.cpp of
osxcross. This file contains a signficant amount of the detection for
paths of different versions of the macOS SDK's and macOS versions. All
of this is truly cursed.
In osxcross's main.cpp, the variable is read in:
if (char *p = getenv("MACOSX_DEPLOYMENT_TARGET")) {
target.OSNum = parseOSVersion(p);
unsetenv("MACOSX_DEPLOYMENT_TARGET");
}
and setting it thus forces the OS version to be parsed from the variable
instead of its (in our case failed) attempt at detecting the version
itself.
Fixes: tpo/core/arti#1394
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
This commit changes the shebang in all shell scripts from absolute
paths (such as `/bin/bash` or `/usr/bin/python3`) to the `/usr/bin/env`
binary with the accompanying interpreter as it's argument.
The reason for this are as follows:
- NixOS cannot work with absolute paths
- BSD systems install their packages in /usr/local/bin
|
| | |
|
| |
|
|
| |
We don't want any updates!
|
| |
|
|
| |
This makes it easier to test, and perform other kinds of stunts.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
fix #378
also fix unrelated error in nightly rustdoc CI
|
|
|
As per #309
Update all references. There is one remaining hit for
git-grep '\.sh\b'
namely "build.sh" in maint/reproducible_build, which I think is
the build script for osxcross - ie, an external project.
|
