Trouble building darktable from master [solved]

Software darktable
1

I’m having issues building darktable from master. It was working some time ago but for some reason not anymore.

> ./build.sh -j 1 --prefix /opt/darktable-test --build-type Release --install --sudo
...
[ 56%] Linking C shared module libcolorout.so
[ 57%] Built target colorout
[ 58%] Generating introspection_colorchecker.c
/usr/include/c++/13.1.1/bits/stl_vector.h:1208: std::vector<_Tp, _Alloc>::reference std::vector<_Tp, _Alloc>::front() [with _Tp = cmGccStyleDependency; _Alloc = std::allocator<cmGccStyleDependency>; reference = cmGccStyleDependency&]: Assertion '!this->empty()' failed.
make[2]: *** [lib/darktable/plugins/CMakeFiles/colorchecker.dir/build.make:213: lib/darktable/plugins/CMakeFiles/colorchecker.dir/depend] Aborted (core dumped)
make[1]: *** [CMakeFiles/Makefile2:4761: lib/darktable/plugins/CMakeFiles/colorchecker.dir/all] Error 2
make: *** [Makefile:156: all] Error 2

I think I’m on Manjaro or something.

2

I can build latest darktable from master darktable 4.5.0+378~g909e6cdda2 on Debian 12.1 with gcc (Debian 12.2.0-14) 12.2.0.

Based on the error below I guess, but do not know, that you are compiling with gcc-13.

I am not aware of any issues with gcc-13 and darktable. I thought it would work with gcc-13 compile as well, but, again, I am on gcc-12.2.

3

There are issues with GCC 13. One solved example is here: 4.2.1 nor master will build with GCC 13 - upstream GCC issue · Issue #14057 · darktable-org/darktable · GitHub. I suppose they are solved as they appear on master branch.

@okke. please consider filing a trouble report. Issues · darktable-org/darktable · GitHub ‘new issue’.

4

@KarlMagnusLarsson I’m on gcc-13.2.1 and it compiles dt-git just fine.

@okke

I think I’m on Manjaro or something.

Tell us when you know.

Also: are you compiling on a very old machine?
The reason why I ask is that you specified “-j 1”.

What was the output before [56%]? Your lines
just tell that make failed, not why.

5

always check what the OBS master builds do that allows you to easily see the build status over a variety of distros.

FWIW: OBS can build Arch linux packages too iiiiiiiiif someone wanted to contribute a PKGBUILD file.

example here

6

Right, I am using Intel® Core™ i7-3770K × 8 CPU and “-j8” on a CPU from 2013. jx with x > 1 will surely improve build time. Depnds on #cores, i suppose.

7

Yep on Manjaro. I’m on a pretty ancient setup with just 8 gigs of memory and I’m pretty sure some of the builds I tried previously were aborted because I ran out of memory (though I was doing something else at the same time).

Output attached: build.txt (57.4 KB)

8

Good evening, @okke,

A very wild guess from my side:
what if you (in a terminal) go to
the folder where your darktable source code
lives, and write

git status

What reply do you get?

Have fun!
Claes in Lund, Sweden

9 
> git status
On branch master
Your branch is up to date with 'origin/master'.

nothing to commit, working tree clean
1 Like
10

That looks suspicious to me. Is that normal, or did the compiler/make fail completely?

1 Like
11

@okke Thank you.
At least one potential source of error eliminated :slight_smile:

12

Manjaro through the Arch repository offers a totally (foolproof) build of the latest daily version.

1 Like
13

Managed to fix thanks to @Claes . Thank you everyone else also for the help.

Did not really find what the initial problem was though… I did a couple of fresh clones beforehand from github but couldn’t complete the build.

Could be that the issue was related to the earlier failures (maybe due to out of memory killer or something) without the -j 1 flag and I had perhaps not cleared the build folder in this folder before retrying & there was something corrupted left?

1 Like