Magnus, Would you be so kind as to build some new Docker images at your earliest convenience? I added ghostscript as a Buildrequires to the specfiles. So no the builds are all failing … but at least not silently any longer :wink: As mentioned separately, I also removed the reuirement for glade…

I pushed new Docker images yesterday which are a union of master and not yet merged Dockerfile changes: Add rtest (!1395) · Merge requests · graphviz / graphviz · GitLab and Change to install libedit-devel instead of symlinking (!1400) · Merge requests · graphviz / graphviz · GitLab . If anyone has …

Yes, I will do that. It takes a couple of hours to build them all so I plan to start a batch job when I call it a day here and push them in the morning.

[image] Ellson: I added ghostscript as a Buildrequires to the specfiles. So no the builds are all failing … but at least not silently any longer :wink: They are not failing because of that. It’s because of your previous commit. See Error: Unable to find a match: glade3-libgladeui-devel - #17 …

I’ve pushed mages for Centos7 & 8 now and triggered a new pipeline run.

Still not getting pdf in graphiz-doc Most pdf are built during the portable-source stage. Did you update the Ubuntu Docker images?

I’ve pushed a new Docker image for Ubuntu 18.04 that is used in the pipeline to build the portable source and triggered a new pipeline run. It became it green :sunglasses:

Thanks. That was it. Now installed pdf files from the graphviz-doc package are non-zero length. E.g. /usr/share/doc/graphviz-doc/pdf/acyclic.1.pdf

FYI the autotools setup does not check for the presence of ps2pdf. So if you clone the current head and try to build without it, you end up staring at the following confusing error: groff -Tps -man ./cdt.3 | false - - >cdt.3.pdf make[3]: *** [Makefile:1113: cdt.3.pdf] Error 1 make[3]: Leaving direc…

The check for ps2pdf is done from the configure script, which is generated from autogen.sh, and which is run during the first phase for generating portable-sources. The reason that the errors from “false” started appearing yesterday was because I removed the preceding “-” character in the Makefile …

Yes, I think I followed this. However, my confusion was that I expected ./configure to fail if it found something missing that would result in a subsequent make failing. Is this just an incorrect assumption on my part?

Requesting new Docker images with ghostscript

Dev

magjac May 31, 2020, 8:43pm 3

They are not failing because of that. It’s because of your previous commit. See Error: Unable to find a match: glade3-libgladeui-devel - #17 by magjac

Topic		Replies	Views
Supported build systems going forward Dev	12	774	August 18, 2020
Building for Ubuntu 16.04 LTS in CI Dev	27	2591	June 16, 2020
Does anyone here know CMake? Dev	26	4404	October 8, 2022
New Installer Package for macOS Dev	21	3585	November 11, 2023
Windows x86, x86-64 builds Help	19	3507	August 27, 2020

Requesting new Docker images with ghostscript

Related topics