collabora issueshttps://gitlab.collabora.com/groups/collabora/-/issues2024-02-15T16:28:29Zhttps://gitlab.collabora.com/collabora/gst-build-sdk/-/issues/3Modernize our cross-file2024-02-15T16:28:29ZNicolas DufresneModernize our cross-fileA minor and simple update to make is to make sure of constants in our cross-files. This would simplify our template and remove redundancy in our end results. Here's a personal tempalte I use for Fedora NFS root management locally.
https...A minor and simple update to make is to make sure of constants in our cross-files. This would simplify our template and remove redundancy in our end results. Here's a personal tempalte I use for Fedora NFS root management locally.
https://gitlab.collabora.com/nicolas/meson-cross/-/blob/master/template.txthttps://gitlab.collabora.com/collabora/gst-build-sdk/-/issues/2Switch repository name2023-03-15T19:03:22ZSebastian FrickeSwitch repository nameWhile this is a big change, that might be unpleasant for some people's workflows. I believe that we should change the name rather now, than later as the situation only becomes worse. The name of the repository was already incorrect when ...While this is a big change, that might be unpleasant for some people's workflows. I believe that we should change the name rather now, than later as the situation only becomes worse. The name of the repository was already incorrect when GStreamer switched to the mono-repository structure and since we add support for other tools like FFmpeg now, the name becomes more and more confusing.
My suggestions would be:
- `multimedia-cross-compilation-SDK` (short: `mm-cross-sdk`)
- `multimedia-cross-builder` (short: `mm-cross-builder`)
And here is a small list of possible required actions after the name change, that popped into my mind:
- Add a notice to Collabora blog posts highlighting this tool
- Search for internal routines using the gst-build-sdk and adjust themhttps://gitlab.collabora.com/collabora/gtimelog/-/issues/5rebase against upstream2022-04-10T19:44:03ZDavid Heidelbergdavid.heidelberg@collabora.comrebase against upstreamCurrent version doesn't work against Debian unstable, while upstream master works just fineCurrent version doesn't work against Debian unstable, while upstream master works just finehttps://gitlab.collabora.com/collabora/gst-build-sdk/-/issues/1Build failures with self-build rootfs2024-02-26T12:53:04ZSebastian FrickeBuild failures with self-build rootfsHey,
I currently experience some issues when I built the rootfs myself.
It looks like there are issues with GLIBC on the rootfs.
____
## Reproduce with:
```bash
debos --scratchsize=4G rootfs.yaml
```
And then enter the rootfs via d...Hey,
I currently experience some issues when I built the rootfs myself.
It looks like there are issues with GLIBC on the rootfs.
____
## Reproduce with:
```bash
debos --scratchsize=4G rootfs.yaml
```
And then enter the rootfs via docker with:
```bash
mkdir ../example_rootfs
sudo tar -xf gst-build-sdk-rootfs-arm64.tar.gz --directory ../example_rootfs
export SYSROOT=`pwd`/../example_rootfs
# from my merge request basically just clones gstreamer and generates cross-file
./prepare_gstreamer_crossbuild.sh
./docker.sh run
```
Within the container I build with (for the record this works fine on the board directly):
```bash
meson build --cross-file cross-file.txt -Dauto_features=disabled -Dbad=enabled -Dbase=enabled -Dgood=enabled -Dgst-plugins-bad:debugutils=enabled -Dgst-plugins-bad:ivfparse=enabled -Dgst-plugins-bad:v4l2codecs=enabled -Dgst-plugins-bad:videoparsers=enabled -Dgst-plugins-base:app=enabled -Dgst-plugins-base:playback=enabled -Dgst-plugins-base:tools=enabled -Dgst-plugins-base:typefind=enabled -Dgst-plugins-base:videoconvert=enabled -Dgst-plugins-good:matroska=enabled -Dgstreamer:tools=enabled -Dwrap_mode=nofallback -Dgst-plugins-good:v4l2=enabled -Dgst-plugins-base:videotestsrc=enabled -Dgst-plugins-base:rawparse=enabled -Dbackend=ninja
```
The used cross-file looks like this:
```bash
[host_machine]
system = 'linux'
cpu_family = 'aarch64'
cpu = 'aarch64'
endian = 'little'
[properties]
sys_root = '/home/basti/Projects/example_rootfs'
pkg_config_libdir = '/home/basti/Projects/example_rootfs/usr/lib/pkgconfig:/home/basti/Projects/example_rootfs/usr/lib/aarch64-linux-gnu/pkgconfig:/home/basti/Projects/example_rootfs/usr/share/pkgconfig'
[built-in options]
c_args = ['--sysroot=/home/basti/Projects/example_rootfs']
cpp_args = ['--sysroot=/home/basti/Projects/example_rootfs', '-I/home/basti/Projects/example_rootfs/usr/include/c++/10']
c_link_args = ['--sysroot=/home/basti/Projects/example_rootfs']
cpp_link_args = ['--sysroot=/home/basti/Projects/example_rootfs']
[binaries]
c = 'aarch64-linux-gnu-gcc'
cpp = 'aarch64-linux-gnu-g++'
ar = 'aarch64-linux-gnu-ar'
strip = 'aarch64-linux-gnu-strip'
pkgconfig = 'pkg-config'
```
## Error
The build fails during `ninja -C build`
```
uid-1000@basti-XPS-13-9310:/home/basti/Projects/example_rootfs/home/user/gstreamer$ ninja -C build
ninja: Entering directory `build'
[154/589] Linking target subprojects/gstreamer/libs/gst/helpers/gst-ptp-helper
FAILED: subprojects/gstreamer/libs/gst/helpers/gst-ptp-helper
aarch64-linux-gnu-gcc -o subprojects/gstreamer/libs/gst/helpers/gst-ptp-helper subprojects/gstreamer/libs/gst/helpers/gst-ptp-helper.p/gst-ptp-helper.c.o -Wl,--as-needed -Wl,--no-undefined -Wl,-Bsymbolic-functions --sysroot=/home/basti/Projects/example_rootfs '-Wl,-rpath,$ORIGIN/../../../gst' -Wl,-rpath-link,/home/basti/Projects/example_rootfs/home/user/gstreamer/build/subprojects/gstreamer/gst -Wl,--start-group subprojects/gstreamer/gst/libgstreamer-1.0.so.0.2100.0 /home/basti/Projects/example_rootfs/usr/lib/aarch64-linux-gnu/libgio-2.0.so /home/basti/Projects/example_rootfs/usr/lib/aarch64-linux-gnu/libgobject-2.0.so /home/basti/Projects/example_rootfs/usr/lib/aarch64-linux-gnu/libglib-2.0.so -lm -Wl,--export-dynamic /home/basti/Projects/example_rootfs/usr/lib/aarch64-linux-gnu/libgmodule-2.0.so -pthread /home/basti/Projects/example_rootfs/usr/lib/aarch64-linux-gnu/libcap.so -Wl,--end-group
/usr/lib/gcc-cross/aarch64-linux-gnu/11/../../../../aarch64-linux-gnu/bin/ld: /home/basti/Projects/example_rootfs/lib/aarch64-linux-gnu/libmount.so.1: undefined reference to `fstat@GLIBC_2.33'
/usr/lib/gcc-cross/aarch64-linux-gnu/11/../../../../aarch64-linux-gnu/bin/ld: /home/basti/Projects/example_rootfs/usr/lib/aarch64-linux-gnu/libgio-2.0.so: undefined reference to `fstat64@GLIBC_2.33'
/usr/lib/gcc-cross/aarch64-linux-gnu/11/../../../../aarch64-linux-gnu/bin/ld: /home/basti/Projects/example_rootfs/lib/aarch64-linux-gnu/libmount.so.1: undefined reference to `lstat@GLIBC_2.33'
/usr/lib/gcc-cross/aarch64-linux-gnu/11/../../../../aarch64-linux-gnu/bin/ld: /home/basti/Projects/example_rootfs/lib/aarch64-linux-gnu/libmount.so.1: undefined reference to `stat@GLIBC_2.33'
/usr/lib/gcc-cross/aarch64-linux-gnu/11/../../../../aarch64-linux-gnu/bin/ld: /home/basti/Projects/example_rootfs/usr/lib/aarch64-linux-gnu/libgio-2.0.so: undefined reference to `lstat64@GLIBC_2.33'
/usr/lib/gcc-cross/aarch64-linux-gnu/11/../../../../aarch64-linux-gnu/bin/ld: /home/basti/Projects/example_rootfs/lib/aarch64-linux-gnu/libdl.so.2: undefined reference to `_dl_catch_error_ptr@GLIBC_PRIVATE'
/usr/lib/gcc-cross/aarch64-linux-gnu/11/../../../../aarch64-linux-gnu/bin/ld: /home/basti/Projects/example_rootfs/lib/aarch64-linux-gnu/libmount.so.1: undefined reference to `fstatat@GLIBC_2.33'
/usr/lib/gcc-cross/aarch64-linux-gnu/11/../../../../aarch64-linux-gnu/bin/ld: /home/basti/Projects/example_rootfs/usr/lib/aarch64-linux-gnu/libgio-2.0.so: undefined reference to `stat64@GLIBC_2.33'
collect2: error: ld returned 1 exit status
[156/589] Linking target subprojects/gstreamer/libs/gst/helpers/gst-plugin-scanner
FAILED: subprojects/gstreamer/libs/gst/helpers/gst-plugin-scanner
aarch64-linux-gnu-gcc -o subprojects/gstreamer/libs/gst/helpers/gst-plugin-scanner subprojects/gstreamer/libs/gst/helpers/gst-plugin-scanner.p/gst-plugin-scanner.c.o -Wl,--as-needed -Wl,--no-undefined -Wl,-Bsymbolic-functions --sysroot=/home/basti/Projects/example_rootfs '-Wl,-rpath,$ORIGIN/../../../gst' -Wl,-rpath-link,/home/basti/Projects/example_rootfs/home/user/gstreamer/build/subprojects/gstreamer/gst -Wl,--start-group subprojects/gstreamer/gst/libgstreamer-1.0.so.0.2100.0 /home/basti/Projects/example_rootfs/usr/lib/aarch64-linux-gnu/libgobject-2.0.so /home/basti/Projects/example_rootfs/usr/lib/aarch64-linux-gnu/libglib-2.0.so -Wl,--export-dynamic /home/basti/Projects/example_rootfs/usr/lib/aarch64-linux-gnu/libgmodule-2.0.so -pthread -lm -Wl,--end-group
/usr/lib/gcc-cross/aarch64-linux-gnu/11/../../../../aarch64-linux-gnu/bin/ld: /home/basti/Projects/example_rootfs/usr/lib/aarch64-linux-gnu/libglib-2.0.so: undefined reerence to `fstat64@GLIBC_2.33'
/usr/lib/gcc-cross/aarch64-linux-gnu/11/../../../../aarch64-linux-gnu/bin/ld: /home/basti/Projects/example_rootfs/usr/lib/aarch64-linux-gnu/libglib-2.0.so: undefined reference to `lstat64@GLIBC_2.33'
/usr/lib/gcc-cross/aarch64-linux-gnu/11/../../../../aarch64-linux-gnu/bin/ld: /home/basti/Projects/example_rootfs/lib/aarch64-linux-gnu/libdl.so.2: undefined reference to `_dl_catch_error_ptr@GLIBC_PRIVATE'
/usr/lib/gcc-cross/aarch64-linux-gnu/11/../../../../aarch64-linux-gnu/bin/ld: /home/basti/Projects/example_rootfs/usr/lib/aarch64-linux-gnu/libglib-2.0.so: undefined reference to `stat64@GLIBC_2.33'
collect2: error: ld returned 1 exit status
[163/589] Compiling C object subprojects/gstreamer/plugins/elements/libgstcoreelements.so.p/gstmultiqueue.c.o
ninja: build stopped: subcommand failed.f
```https://gitlab.collabora.com/collabora/gtimelog/-/issues/4No longer handles initial usage2021-04-12T12:21:41ZRylie PavlikNo longer handles initial usageI think this is because of the recent change to open. On first start I see:
```
Traceback (most recent call last):
File "/home/ryan/.local/lib/python3.7/site-packages/gtimelog/timelog.py", line 679, in load
with open(self.filename...I think this is because of the recent change to open. On first start I see:
```
Traceback (most recent call last):
File "/home/ryan/.local/lib/python3.7/site-packages/gtimelog/timelog.py", line 679, in load
with open(self.filename) as f:
FileNotFoundError: [Errno 2] No such file or directory: '/home/ryan/.gtimelog/tasks.txt'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/ryan/.local/lib/python3.7/site-packages/gtimelog/main.py", line 1929, in _activate
tasks = TaskList(os.path.join(configdir, 'tasks.txt'))
File "/home/ryan/.local/lib/python3.7/site-packages/gtimelog/timelog.py", line 653, in __init__
self.load()
File "/home/ryan/.local/lib/python3.7/site-packages/gtimelog/timelog.py", line 685, in load
print(e.message)
AttributeError: 'FileNotFoundError' object has no attribute 'message'
```
After setting up gtimelogrc, I instead get:
```
Traceback (most recent call last):
File "/home/ryan/.local/lib/python3.7/site-packages/gtimelog/timelog.py", line 679, in load
with open(self.filename) as f:
FileNotFoundError: [Errno 2] No such file or directory: '/home/ryan/.gtimelog/remote-tasks.txt'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/ryan/.local/lib/python3.7/site-packages/gtimelog/main.py", line 1927, in _activate
os.path.join(configdir, 'remote-tasks.txt'))
File "/home/ryan/.local/lib/python3.7/site-packages/gtimelog/collabora.py", line 228, in __init__
TaskList.__init__(self, cache_filename)
File "/home/ryan/.local/lib/python3.7/site-packages/gtimelog/timelog.py", line 653, in __init__
self.load()
File "/home/ryan/.local/lib/python3.7/site-packages/gtimelog/timelog.py", line 685, in load
print(e.message)
AttributeError: 'FileNotFoundError' object has no attribute 'message'
```
cc @smcvhttps://gitlab.collabora.com/collabora/gtimelog/-/issues/3Silently ignores/mishandles out-of-order or empty entries2020-03-20T12:21:06ZRylie PavlikSilently ignores/mishandles out-of-order or empty entriesThis has caused me issues in the past due to copy/paste typos. I have a commit to check this assumption and warn on stdout: https://gitlab.collabora.com/collabora/gtimelog/-/commit/e622e10ce22392d9d28962f087d6847f914ee500 but this is a ...This has caused me issues in the past due to copy/paste typos. I have a commit to check this assumption and warn on stdout: https://gitlab.collabora.com/collabora/gtimelog/-/commit/e622e10ce22392d9d28962f087d6847f914ee500 but this is a big enough problem I think it should be warned in the GUI.
cc @evelikov @andrewsh https://gitlab.collabora.com/collabora/gtimelog/-/issues/2Virtual midnight should be evaluated in the time zone of an entry2020-04-06T12:39:12ZRylie PavlikVirtual midnight should be evaluated in the time zone of an entryRight now it looks like it's evaluated in my computer's current timezone. However, if I (normal resident of -0600) go to Europe and log in +0100, that's the timezone in which 4am has meaning. Right now, if I leave those entries in my tim...Right now it looks like it's evaluated in my computer's current timezone. However, if I (normal resident of -0600) go to Europe and log in +0100, that's the timezone in which 4am has meaning. Right now, if I leave those entries in my timelog once I get back to the US and change my timezone back to -0600, they'll error out since it'll say missing client for my "arrived" entries. It seems as though my workaround is to change the timezone on those timelog entries (!) to -0600 as well.
(The alternative would be to ditch the virtual midnight thing and just mandate some kind of standard "arrived" entry, which seems less error prone to me.)https://gitlab.collabora.com/collabora/gtimelog/-/issues/1Update build on OBS2019-12-12T16:38:08ZRylie PavlikUpdate build on OBSWould be good to push a new build to https://build.collabora.co.uk/package/show/collabora:sysadmin:public/collabora-gtimelogWould be good to push a new build to https://build.collabora.co.uk/package/show/collabora:sysadmin:public/collabora-gtimeloghttps://gitlab.collabora.com/collabora/ci-demo/-/issues/4Create JSON -> xUnit converting script for LAVA test results2018-11-08T12:27:17ZMichał GałkaCreate JSON -> xUnit converting script for LAVA test resultshttps://gitlab.collabora.com/collabora/ci-demo/-/issues/3Add image storing to the pipeline2018-11-08T12:26:28ZMichał GałkaAdd image storing to the pipelinehttps://gitlab.collabora.com/collabora/ci-demo/-/issues/2Create Jenkins pipeline to build a qemu based image2018-11-08T12:26:26ZMichał GałkaCreate Jenkins pipeline to build a qemu based imageMichał GałkaMichał Gałkahttps://gitlab.collabora.com/collabora/ci-demo/-/issues/1Clean up the repository2018-11-02T16:25:51ZMichał GałkaClean up the repositoryCreate a generic CI pipeline for the ci-demo.Michał GałkaMichał Gałka