Build (also) with gcc devshell config in CI #412
Labels
No labels
Area/build-packaging
Area/cli
Area/evaluator
Area/fetching
Area/flakes
Area/language
Area/profiles
Area/protocol
Area/releng
Area/remote-builds
Area/repl
Area/store
bug
crash 💥
Cross Compilation
devx
docs
Downstream Dependents
E/easy
E/hard
E/help wanted
E/reproducible
E/requires rearchitecture
imported
Needs Langver
OS/Linux
OS/macOS
performance
regression
release-blocker
RFD
stability
Status
blocked
Status
invalid
Status
postponed
Status
wontfix
testing
testing/flakey
ux
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: lix-project/lix#412
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
#410 revealed that we never actually build with the gcc devshell config in ci, which notably includes
-Denable-pch-std=false
, so we don’t know when stuff breaks hacking.md. i wonder if we can either align our ci with the config used in our docs, or at least create new builds that follow the docs as closely as possible?perhaps should be in the less-frequent CI runs? #142
either that or we just obtain more compute, and i think that circumstances are going to lead to us having a lot more compute soon enough.