Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
By submitting this pull request, I confirm the following:
How familiar are you with the codebase?:
10
Update
ftl-build
containers todebian:buster
where applicable.Note: This sets the minimum supported kernel to Linux 3.2.0 (January 2012) for binaries built with these containers
We do not update the containers:
armv4t
:debian:buster
droppedarmv4t
compatibilityarmv6hf
: There is a bug indebian:buster
's cross-compilationlibc
missingfnctl64
for targetarmv6hf
We furthermore update
x64_64-musl
-container to latestalpine:3.12
Always clone and test-compile FTL's source from the protected branch
special/CI_development
. This ensures external contributions (and we ourselves) can see much more easily if changes/updates we do in the containers are good or not because the target architecture, FPU-requirements, minimum kernel versions, etc. are automatically checked during the container generation.Points 1 and 2 make this PR superseding #14 which was not accepted before as there were more changes to be done to the building system than were not very obvious without a test compilation (which is included by default now due to no. 3 above).