| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This required making sure that fhs-dirs is depended on by anything
which would stage on top of it, as the directory symlinks must come
first.
In this commit the dependencies are listed explicitly, probably
there is a way to do this without being as wordy.
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
This is because otherwise we end up using the sysrooted
/tools/sbin/ldconfig, causing the gcc build to fail as it
does not find libz.so which is otherwise properly located
if /sbin/ldconfig is used.
|
| |
| |
| |
| |
| | |
Because the GNOME sdk is no longer there, and ldconfig from stage2
is in /tools/sbin.
|
| |\
| | |
| | |
| | |
| | | |
Don't use ssh urls in the aliases when not needed
See merge request !1
|
| |/ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This huge commit is a manual conversion, notes on what was
needed:
o project.conf defines the arch specific stuff which was
previously hardcoded into YBD, so the stage1 target and target
etc are all defined by the build-essential project.conf
o Direct and easy changes for git source representation
o Added stage1.bst & stage2.bst "stacks", everything built in
stage2 build-depends on stage1.bst, and the final build-essential
products build-depend on stage2.bst (note build-depend means
to depend _only_ for building, not propagated forward).
o Instead of using host tools we build on the GNOME flatpak
sdk/platform bundles
o Some build-essential morph files use $(dirname $(pwd)) for a sysroot,
which is weird, it means the morph files rely on building at one directory
below the slash sysroot - in buildstream we build in /buildstream/build
which is two - had to replace these with $(dirname $(dirname $(pwd))) instead
o Remove the devices sections from the fhs-dirs elements, not allowed
to create static device nodes in buildstream.
|
| |
| |
| |
| | |
This is on by default for any autotools or supporting build system.
|
| |
| |
| |
| |
| | |
Pull in a different org.gnome.Sdk branch depending on the
build architecture.
|
| |
| |
| |
| |
| | |
Pull in a different org.gnome.Platform branch depending on the
build architecture.
|
| | |
|
| | |
|
| |
| |
| |
| | |
introspection.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
And it also builds glade for the hell of it.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
If USE_BUILD_LIBS is enabled, the build fails under BuildStream. This
seems to be because files get installed to $DESTDIR/buildstream/build
which are then included in the artifacts. (This breaks subsequent builds
as the /buildstream/build/ dir is expected to be empty until source is
checked out.)
https://gitlab.com/BuildStream/buildstream/issues/74 is the relevant
BuildStream issue.
|
|
|
|
|
|
|
| |
These presumably aren't needed since they are probably not even
accessible during the normal operation of a system (as there can be a
tmpfs mounted over the top). YBD doesn't raise any error about this
but BuildStream does.
|
|
|
|
|
| |
It's obsolete and full of security holes. And it fails to compile under
BuildStream for some reason but let's see if we can just get rid of it.
|
| |
|
|
|
|
| |
This removes the dependency on WebKitGtk1.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
For some reason the configure scripts fail to pass `-std=gnu99` to GCC
even though the code uses C99 features (and presumably GNU extensions,
although I haven't checked that).
This was leading to compile failures like this in Epiphany:
ephy-filters-manager.c: In function 'remove_old_adblock_filters':
ephy-filters-manager.c:207:5: error: 'for' loop initial declarations are only allowed in C99 or C11 mode
for (GList *l = current_files; l != NULL; l = l->next) {
^
ephy-filters-manager.c:207:5: note: use option -std=c99, -std=gnu99, -std=c11 or -std=gnu11 to compile your code
ephy-filters-manager.c: In function 'update_adblock_filter_files':
ephy-filters-manager.c:244:3: error: 'for' loop initial declarations are only allowed in C99 or C11 mode
for (guint i = 0; filters[i]; i++) {
^
Makefile:797: recipe for target 'libephymisc_la-ephy-filters-manager.lo' failed
make[4]: *** [libephymisc_la-ephy-filters-manager.lo] Error 1
And similar things in GNOME Control Centre.
|
| |
|
| |
|
|
|
|
|
| |
This makes life easier when converting to BuildStream, as BuildStream
doesn't set DESTDIR in the environment.
|
| |
|
| |
|
|
|
|
|
|
| |
GNU gzip was added as qtwebengine depends on the --rsyncable option,
which Busybox doesn't provide. It is more logical to put it in the
same stratum as bzip2 though.
|
|
|
|
|
|
|
|
|
|
| |
See: https://bugs.webkit.org/show_bug.cgi?id=167643
Without this, the build log building with GCC 7 is 1GB in size
due to huge amounts of this kind of thing:
/WebKitGtk.build/Source/JavaScriptCore/b3/B3ArgumentRegValue.cpp:29:1: warning: this use of "defined" may not be portable [-Wexpansion-to-defined]
#if ENABLE(B3_JIT)
|
|
|
|
| |
This isn't actually needed, but it's done now.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
These need to be upgraded together:
- GCC 5.3 fails to build against GLIBC 2.25 due to use of putc() which
triggeres a compile warning. As we seem to build with -Werror this
causes the build to break.
- GLIBC 2.22 fails to build with GCC 7.1 due to int-in-bool-context
errors.
Note that GLIBC 2.22 also fails to build against GLIBC 2.25, failing
with this error:
/tools/include/limits.h:145:17: error: missing binary operator before token "("
#if __GLIBC_USE (IEC_60559_BFP_EXT)
^
|
|
|
|
|
|
|
|
| |
This issue doesn't appear to be fixed upstream, I have done a simple
patch.
The issue is a missing `#include <functional>` causing errors about
`std::function` being undefined. (I'm not sure how this ever worked).
|
|
|
|
|
| |
The upstream looks abandoned so I have applied the patches
to our baserock/ branch.
|
|
|
|
|
|
| |
They helpfully force -Werror on everyone so we have to backport a couple
of `// FALLTHRU` comments to fix the build... the patches don't seem to
even work so I have also disabled -Werror forcefully.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is to fix build issues with GCC 7 in QtWebKit and QtIvi.
Note that the GENIVI IVI shell patches were merged upstream in QtWayland
commit f144f0f71f1b75df92 so we should no longer need to use a fork of
that component.
qtwebengine 5.9 requires GNU gzip to build -- the `grit` tool (Google
Resource and Internationalization Tool) expects to be able to call `gzip
--rsyncable` which is a feature only provided by GNU gzip. I used
'master' of gzip.git because otherwise the build of the embedded gnulib
components fail with GCC 7 (due to warnings and -Werror).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This began due to build issues in Clutter with GCC 7, and turned
into a wide-ranging update of GNOME components. Many of these are
needed due to deprecation warnings introduced by the GTK+ upgrade.
The Gettext and GLIB upgrades are needed by GTK+.
The libgdata upgrade was due to deprecation warnings triggered by
GTK+ and this now pulls in autoconf-archive.
Upgrading Clutter requires upgrading Mutter, which in turn requires
new libinput. Note that libinput also required an upgrade to
linux-api-headers (done before). I have updated to Mutter 3.22.3
rather than 3.24 to avoid having to upgrade xrandr.
WebKit has a bug that causes compile failures with GCC 7:
<https://bugs.webkit.org/show_bug.cgi?id=167642>.
The gcrypt upgrade is required to build new WebKit.
gnome-control-center needed to be upgraded which in turn
pulls in network-manager-applet.
|