vasilito
48a924c561
The libredox 0.1.19 / redox_syscall 0.9.1 bump left 45 recipe lockfiles pinning libredox 0.1.18+rb0.3.1 and redox_syscall 0.9.0+rb0.3.1. The cookbook builds with --locked, so every affected recipe died with error: cannot update the lock file .../Cargo.lock because --locked was passed to prevent this which is what took out redox-driver-sys -- and with it every Red Bear driver -- during the redbear-full build. Regenerating the fork lockfiles was not enough; the recipes that consume the forks as path deps carry their own. This is step 6 of local/docs/FORK-BUMP-PATCHING-POLICY.md applied to the recipe layer. Also drop the hardcoded GCC version in recipes/libs/libstdcxx-v3: the literal include/c++/13.2.0 stopped resolving the moment the cross toolchain moved to 16.1.0, leaving -I pointing at a directory that does not exist. Now resolves the newest installed C++ header directory and fails loudly if there is none. Same failure class as the hardcoded 13.2.0 in mk/prefix.mk. Note: a few recipe-level Cargo.lock files (redox-driver-pci, cpufreqd, redbear-acmd/-ecmd/-ftdi) sit beside a recipe.toml whose [source] is path = "source", so they are not build inputs; redox-driver-pci's even references a redox-driver-core/Cargo.toml that does not exist. They are left alone rather than given meaning they do not have. redox-driver-sys now cooks clean.
23 lines
1.0 KiB
Plaintext
23 lines
1.0 KiB
Plaintext
This directory contains the GNU Compiler Collection (GCC).
|
|
|
|
The GNU Compiler Collection is free software. See the files whose
|
|
names start with COPYING for copying permission. The manuals, and
|
|
some of the runtime libraries, are under different terms; see the
|
|
individual source files for details.
|
|
|
|
The directory INSTALL contains copies of the installation information
|
|
as HTML and plain text. The source of this information is
|
|
gcc/doc/install.texi. The installation information includes details
|
|
of what is included in the GCC sources and what files GCC installs.
|
|
|
|
See the file gcc/doc/gcc.texi (together with other files that it
|
|
includes) for usage and porting information. An online readable
|
|
version of the manual is in the files gcc/doc/gcc.info*.
|
|
|
|
See http://gcc.gnu.org/bugs/ for how to report bugs usefully.
|
|
|
|
Copyright years on GCC source files may be listed using range
|
|
notation, e.g., 1987-2012, indicating that every year in the range,
|
|
inclusive, is a copyrightable year that could otherwise be listed
|
|
individually.
|