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.
13 lines
499 B
Makefile
13 lines
499 B
Makefile
# This BUILD_CONFIG option tests that target libraries built during
|
|
# stage3 would have generated the same executable code if they were
|
|
# compiled with -g0.
|
|
|
|
# It uses -g0 rather than -gtoggle because -g is default on target
|
|
# library builds, and toggling it where it's supposed to be disabled
|
|
# breaks e.g. crtstuff on ppc.
|
|
|
|
STAGE1_TFLAGS += -g0 -fcompare-debug=
|
|
STAGE2_TFLAGS += -fcompare-debug=
|
|
STAGE3_TFLAGS += -fcompare-debug=-g0
|
|
do-compare = $(SHELL) $(srcdir)/contrib/compare-debug $$f1 $$f2
|