| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
| |
If there is no staging-filler setting in a configuration file,
it defaults to the empty string, not None.
Reviewed-by: Jonathan Maw over the shoulder
|
|\
| |
| |
| |
| |
| | |
(I am not going through the normal patch review process for this.)
Reviewed-by: Lars Wirzenius
|
| | |
|
|/ |
|
|\ |
|
| |\
| | |
| | |
| | | |
Reviewed-by: Jonathan Maw <jonathan.maw@codethink.co.uk>
|
| |/
| |
| |
| |
| |
| | |
The absolute one made the test suite fail in my VM, and is not the
right thing to do anyway. $DESTDIR/usr/bin and $DESTDIR/bin are meant
to be the same directory here, not $DESTDIR/usr/bin and /bin.
|
|\ \
| |/
|/| |
|
| | |
|
| | |
|
| | |
|
|\ \
| | |
| | |
| | | |
Reviwed-by: Jonathan Maw <jonathan.maw@codethink.co.uk>
|
|/ /
| |
| |
| |
| | |
To remove need of configuring git to check new system .gitconfig file
added to morph/scripts and check set to use this file.
|
|\ \
| | |
| | |
| | | |
Reviewed-by: Jonathan Maw <jonathan.maw@codethink.co.uk>
|
|/ / |
|
|\ \
| | |
| | |
| | | |
Reviewed-by: Jonathan Maw <jonathan.maw@codethink.co.uk>
|
|/ /
| |
| |
| | |
morph.log will now show an INFO message rther than a ERROR
|
|\ \
| | |
| | |
| | | |
Reviewed-by: Jonathan Maw <jonathan.maw@codethink.co.uk>
|
|/ /
| |
| |
| |
| | |
The 'master' branch of baserock:baserock/morphs no longer requires
a staging filler.
|
|\ \
| | |
| | |
| | | |
Reviewed-by: Jonathan Maw <jonathan.maw@codethink.co.uk>
|
| | | |
|
|/ / |
|
|\ \ |
|
| | | |
|
| | | |
|
| | | |
|
|/ / |
|
|\ \
| | |
| | |
| | |
| | |
| | | |
'baserock/richardholland/add-metadata-dir-setting-to-branch-from-image'
Reviewed-by: Jonathan Maw <jonathan.maw@codethink.co.uk>
|
| | | |
|
| | |
| | |
| | |
| | | |
morph branch-from-image
|
| | | |
|
|\ \ \
| | | |
| | | |
| | | | |
Reviewed-By: concensus
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Define a specific set of 4 architectures that Morph supports, and only
expose that value to morphologies.
Since GNU triplets are very common we also expose a GNU triplet. Other
morphologies should work out their configuration based on MORPH_ARCH.
This commit also removes the morphlib.util.arch() function, which
detected the machine Morph is running on via 'uname -m'. Morph's
architecture names do not necessarily map to the output of 'uname -m'
so we should not rely on it anywhere.
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This is a kludge which I am only doing because we are removing this
plugin soon. Morph no longer has a way to detect the architecture that
it is running on and no longer needs one anywhere else.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
We can no longer build strata individually because we don't know
what architecture they are for.
|
|\ \ \ \
| |/ / /
| | | /
| |_|/
|/| |
| | |
| | | |
Conflicts:
morphlib/bins_tests.py
Reviewed-By: consensus
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This gives us some forward compatibility leeway to introduce new
build modes, as long as they are compatible with staging.
As suggested by Richard Maw.
|
| | |
| | |
| | |
| | |
| | | |
If for example /bin is a symlink, we shouldn't and can't mount the host
system's /bin over the top.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When building a stratum artifact it's easy to only include chunks that
were built in 'staging' mode. Constructing the staging area doesn't use
that code path, though, so we need an extra hack to filter out those
artifacts while building.
It may be neater to express stratum build-depends as actual
dependencies on the stratum artifact, rather than each of its
constituent chunks as we do now.
|
| | |
| | |
| | |
| | |
| | | |
This is necessary so that the build-essential stratum doesn't end up
containing three different compilers.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Morph no longer supports setting the prefix using the --prefix
argument / setting. This was only used in tests and during bootstrap.
If a chunk build-depends on a chunk within a stratum which has
a custom prefix, that prefix is appended to the PATH in the build
environment.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Allowed values:
staging: build with a staging chroot (default)
test: build with the host's tools
bootstrap: build with the host's tools, and do not include this
chunk in the final stratum artifact
In the past, 'normal mode' has been used to describe building a chunk
with the host's tools. We don't want that mode to ever be used,
because it is a huge hole in reproducability, but we need to keep it
around to avoid making Morph's cmdtest suite depend on Baserock.
Hopefully naming it 'test' should discourage potential abusers.
It is unfortunate that the build tests now take a separate code path
compared to real-world usage of Morph. However, this is necessary to
avoid a circular dependency between Morph's test suite and the
build-essential stratum in Baserock.
We do whole-build testing of Baserock, too, so the 'staging' code path
is still tested outside of Morph. However, testing a staging area
requires populating it with at minimum a working shell, and this is a
bit too complex to go in Morph's test suite.
|
| | |
| | |
| | |
| | |
| | |
| | | |
In the future we will allow this to be modified to provide a
cross-bootstrap mode, but for now we use the same target as
the host compiler.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Reorganise the build_artifact() and build_artifacts() functions to
allow more complex work when setting up chunk builds in
build_artifact().
The staging area now holds the BuildEnvironment object (the
environment variables that should be set during build). This makes sense
because all build commands should be run inside the staging area and
therefore through the StagingArea object.
The BuildEnvironment object is now considered immutable after it is
created. The environment is used in cache key computation when
computing what artifacts are required; if it changes after that point
we risk either computing different artifact keys for the same artifact
or missing data in the cache key that should be included in the hash.
Better to force changes into a separate 'extra_env' variable.
|
| | |
| | |
| | |
| | |
| | | |
This involved having a staging area with split personalities
and was generally a bit ugly.
|
| | |
| | |
| | |
| | |
| | |
| | | |
That means that bootstrapping Baserock is currently not possible with
this branch of Morph, but there's no reason it cannot be bootstrapped
using an older version of Morph instead.
|
| | |
| | |
| | |
| | |
| | |
| | | |
That means that bootstrapping Baserock is currently not possible with
this branch of Morph, but there's no reason it cannot be bootstrapped
using an older version of Morph instead.
|