| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
| |
definition for the rest
|
| |
|
|
|
|
|
|
|
| |
This is made by a conversion made in
commit 8f8992a18d55c3abf28d4b6fc8036bd39d3dc1cf of definitions
Check there to know what exact versions of YBD and defs2bst was used
|
| |
|
|
|
|
| |
Keep the conversion though
|
|
|
|
|
| |
Drumroll... we actually boot the VM in QEMU, run a command, and
check its output is sane.
|
|
|
|
|
|
|
|
|
| |
This is the first thing I have ever written with asyncio and it
spits out lots of warnings and exceptions in some cases that I
don't really understand.
However the basics are there: if the VM boots and can run `uname -a`,
the test succeeds; otherwise it fails.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This element produces a disk image that boots in QEMU. It has a kernel,
BusyBox, and little else; but should be suitable as a basis for more
grand endeavours.
This disk image we produce is 53MB. I spent a while trying to get this
as small as possible and this is as far as I got:
* The boot partition seems to have a minimum size just over 32MB;
lower than that and SYSLINUX fails to write the boot sector. The
combined size of the initramfs and kernel is about 32MB, so I
imagine that's what limits us.
* The main partition is limited in size only by the amount of binaries
that we put there.
* We have a useless 40KB swap partition, which the x86image plugin
insists on creating for us. Again 40KB is the minimum size that
`mkswap` will allow. It's possible to override or modify the
x86image plugin to avoid swap altogether but I'm not sure of the
best way to proceed.
There are a few dependency cleanups in the bsp-generic stack; previously
we'd build the whole 'foundation' stack which took ages and wasn't
needed at all.
|
|
|
|
|
|
|
|
|
|
|
|
| |
The scripts are taken from
https://gitlab.com/BuildStream/buildstream-tests (branch build-gnome).
Those in turn were taken from
http://git.baserock.org/baserock/baserock/initramfs-scripts.git
We manually set the executable permissions in the init scripts
using chmod, because
https://gitlab.com/BuildStream/buildstream/issues/84
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This includes many fixes that result in us being able to produce a
minimal OS image or initramfs of a reasonable size. I have built an
initramfs of 16MB uncompressed with this change: still a bit bigger
than necessary, but much better than the comical ~700MB thing complete
with kernel source code and C++ compiler that I got before these
changes.
Note that the gnu-toolchain stack now puts all the toolchain binaries
into the 'devel' artifact. The 'runtime' artifact just contains
libraries needed to run programs that are built with that toolchain.
We should split this up further in future so that C programs don't
depend on libstdc++.
Special care is taken for GCC and GLIBC to handle the lib/ and lib64/
split that they do on some 64-bit platforms.
We also globally put /usr/src into the devel artifact, which is only
useful for the linux.bsp element at present but makes sense as a global
rule.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We intended to set the architecture triplet for systems we build
to something like x86_64-baserock-linux-gnu. This wasn't actually
happening though as nobody had passed the message on to the GCC and
Binutils build systems, so we got mixed defaults of
x86_64-pc-linux-gnu and x86_64-unknown-linux-gnu.
Both GCC and Binutils install files that have the target name
in their path, and it's useful when writing split rules if we
know in advance what that's actually going to be. Plus it looks
neater if we set the vendor field in the architecture triplet correctly!
|
|
|
|
|
|
|
|
|
| |
To hopefully fix a build issue that has randomly reared its head:
[3104/3492] Linking default/lib/tdb/tdbrestore
/usr/bin/ld: /usr/lib/gcc/x86_64-pc-linux-gnu/7.1.0/../../../libcom_err.a(error_message.o): relocation R_X86_64_32 against `.bss' can not be used when making a shared object; recompile with -fPIC
/usr/lib/gcc/x86_64-pc-linux-gnu/7.1.0/../../../libcom_err.a: error adding symbols: Bad value
collect2: error: ld returned 1 exit status
|
| |
|
|
|
|
|
|
|
|
| |
BuildStream changed its defaults in be08caa06d6b8ba780aa so that
autoreconf always runs.
A few components need fixing as a result, mostly those which were
not correctly depending on autotools
|
|
|
|
| |
It was still using --target-arch which BuildStream no longer supports.
|
|
|
|
|
| |
This version changes how artifact caches are specified, so the
project.conf file needs updating too.
|
|
|
|
| |
The component on it are already build in the IVI system
|
|
|
|
| |
The components on it are already build in the GDP system
|
| |
|
|
|
|
| |
They are not really used/maintained
|
|
|
|
| |
So we build the same systems in build-1 for ybd and buildstream
|
| |
|
|
|
|
|
|
|
|
|
| |
To hopefully fix a build issue that has randomly reared its head:
[3104/3492] Linking default/lib/tdb/tdbrestore
/usr/bin/ld: /usr/lib/gcc/x86_64-pc-linux-gnu/7.1.0/../../../libcom_err.a(error_message.o): relocation R_X86_64_32 against `.bss' can not be used when making a shared object; recompile with -fPIC
/usr/lib/gcc/x86_64-pc-linux-gnu/7.1.0/../../../libcom_err.a: error adding symbols: Bad value
collect2: error: ld returned 1 exit status
|
|
|
|
|
| |
This gains us support for `mkfs.ext4 -d`, which is great when making
disk images.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The approach from commit 56885a36e5c3830a6c6c7a663730a8a297a5825c was
neater, but it doesn't work due to this GitLab issue:
https://gitlab.com/gitlab-org/gitlab-ce/issues/20615
I can't see any way to make this work apart from putting the SHA1s
into the job before_script sections directly. I moved them upwards
to make it more obvious.
Of course once we stop using YBD we can clean this up nicely.
|
| |
|
|
|
|
|
| |
This version uses %{arch} instead of %{bst-arch}, and uses list
composition operations instead of pre- and post- commands.
|
|
|
|
|
|
|
|
|
|
|
|
| |
The initial implementation of architecture conditionals has been
removed, as the same behaviours can be implemented using the more
generic mechanism for conditionals that is being introduced for
BuildStream 1.0.
We now have two architecture options: build_arch and arch. They are
documented in project.conf. The first one controls the build sandbox
while the second controls the host and target of the binaries we
produce.
|
|
|
|
|
| |
This was meant to be added as part of MR !58, but of course I forgot
to `git add`.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Otherwise, cross builds can try and run a version of `ldconfig` that is
built for the target architecture rather than the host, resulting in
brokenness.
|
|
|
|
|
|
|
|
|
| |
This fixes cross-compilation of stage2-gcc against our stage3 base
sysroot.
If the `.la` files are not removed, Libtool insanity kicks in and we end
up with the x86_64 version of libstdc++ included in the cross-build
commandlines.
|
|
|
|
|
| |
This reduces the output size of bootstrap/stage3-sysroot.bst from 500MB
to 350MB.
|
| |
|
| |
|
| |
|
|\
| |
| |
| | |
sam/bootstrap-from-baserock-binaries
|
| |
| |
| |
| | |
Current master of all those
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
We do want to control what version of BuildStream are we using in the CI,
not as part as the image; an update can break the build and the same commit
that built today can break tomorrow
This reverts commit 3de7f8086cfc89e11ffdf88651ab415e661e2609.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This replaces the previous approach of using the Freedesktop SDK binaries.
We need to support more architectures than just x86_32 and x86_64, and in
general it's better to bootstrap from a minimal sysroot that we build and
control.
The binaries are hosted at https://ostree.baserock.org/releases and are
produced by a manual (but automatable) process that I will document in
subsequent commits from the `bootstrap/stage3-sysroot.bst` element.
|
| |
| |
| |
| |
| |
| | |
The objcopy tool that we built in stage2 doesn't have zlib support, so
it can't handle the `--compress-debug-sections` flag that BuildStream
passes by default.
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
These each produce a minimal (~300MB) sysroot containing BusyBox, the
GNU C/C++ toolchain, and a couple of other components necessary for
bootstrapping Baserock reference systems from the ground up.
Morph and YBD used tools from the host to bootstrap, which usually
worked fine but was occasionally disasterous (such as when GLIBC
broke ABI between releases). BuildStream is more strict and requires
you to provide binaries to seed its sandbox.
The stage2 sysroot can only be used to build the stage3 sysroot, as
the stage2 components are configured with a non-standard /tools prefix
and the stage3 build instructions have some special casing that is
necessary to work with that.
The stage3 sysroot can be used to build pretty much anything and is
used to seed Baserock reference builds on each platform.
|
| |
|
|
|
|
|
| |
libseccomp has architecture-specific parts, and the previous version
did not support ppc64l.
|
|
|
|
|
|
| |
This is done because ppc64l is having compatibility problems.
The updated version of libffi depends on libtool.
|