resize2fs creates a filesystem with unclean orphan file when resizing
to more than 32GB if the orphan_file option is enabled, resulting in
an unmountable storage partition after initial resize.
Explicitly disable the option until the issue is resolved.
Signed-off-by: Matthias Reichl <hias@horus.com>
When making the boodloader files optional I forgot to remove the code
that unconditionally copies the bootloader files which broke noobs
build for RPi4 and RPi5. Drop the code, the files are already copied
by the for loop above.
Signed-off-by: Matthias Reichl <hias@horus.com>
Package building honor's the strip flag so we can prevent executables
from being stripped.
But copying files to INSTALL ignored that flag which meant the flag
had practically no effect.
Fix this by using the same logic as we do in the meson strip handling in
line 170 and in config/functions.
Also add the missing quotes in scripts/build to align it with config/functions
Signed-off-by: Matthias Reichl <hias@horus.com>
Several packages and buildsystems (most notably cmake) badly trip
over CC="ccache gcc" so create local wrapper scripts in the build
dir and set CC/CXX to them to work around that - like we do for
host-gcc and gcc in toolchain.
Signed-off-by: Matthias Reichl <hias@horus.com>
fixup scripts/build local-cc wrapper
Timing detail reporting can be enabled by setting
TRACE_BUILD_TIMING=1
This enables timestamping collecting at various build stages so we
can easily analyze how long eg configure, make/build, install etc
steps take.
Signed-off-by: Matthias Reichl <hias@horus.com>
add flag "-o" to overwrite file on unzipping.
when a build is interrupted by some issues, it will cause a re-substitution problem after a rebuild the target whose source code come from a zip file (like target jzintv)
The buildsystem's Makefile hardcodes the location of the BUILD_DIR used
by the rest of the buildsystem. Add a script to handle what BUILD_DIR
might be set to.
Signed-off-by: Ian Leonard <antonlacon@gmail.com>
In case SYSTEM_SIZE was higher than 1024, mcopy would fail without the
failure being caught. The failure was probably due to invalid geometry
(number of sectors per track too high?). However mformat should be able
to determine the geometry on its own, when no geometry parameters are
supplied. After discussion on IRC with vpeter we came to this solution.
* create temporary folder in the target folder
* use sparse files to create image and partitions
* no extractions of the partitions from image
* modify mcopy alias to copy to the partition sparse file
* add `-o` switch to mcopy alias, so mcopy does not prompt in case of
existing file in the partition
* remove alias for mformat (is used only one time)
* catch errors for mformat/mcopy/mmd
* use mcopy alias when copying files to virtual appliance part1
* move DISK_LABEL setting closer to the part where it is used
* write MBR without test (it should be already present and if not, dd
will fail anyway and error is caught)
* update output when vmdk is created
Co-authored-by: Peter <peter.vicman@gmail.com>
Script uses arbitrary values for FAT32 partition and name of the
distribution. Using placeholders in the script and replacing them at
build time offers flexibility, i.e. no need to change arbitrary values
in script when SYSTEM_SIZE is changed.
