Description of problem: Package graphviz fails to build from source in Fedora Rawhide. gvloadimage_gs.c: In function 'gs_error': gvloadimage_gs.c:75:16: error: 'e_VMerror' undeclared (first use in this function) if (err >= e_VMerror) ^~~~~~~~~ gvloadimage_gs.c:75:16: note: each undeclared identifier is reported only once for each function it appears in gvloadimage_gs.c:77:21: error: 'e_unregistered' undeclared (first use in this function) else if (err >= e_unregistered) ^~~~~~~~~~~~~~ gvloadimage_gs.c:79:21: error: 'e_invalidid' undeclared (first use in this function) else if (err >= e_invalidid) ^~~~~~~~~~~ Dependency changes in buildroot between last success build and failing build: ghostscript-devel 9.16-5.fc26 > 9.20-2.fc26 ghostscript-core 9.16-5.fc26 > 9.20-2.fc26 ghostscript 9.16-5.fc26 > 9.20-2.fc26 ghostscript-x11 9.16-5.fc26 > 9.20-2.fc26 kernel-headers 4.9.0-0.rc0.git2.1.... > 4.9.0-0.rc0.git3.2.... systemd-libs 231-7.fc26 > 231-9.fc26 libcurl 7.50.3-1.fc26 > 7.50.3-2.fc26 vim-minimal 2:8.0.003-1.fc26 > 2:8.0.018-1.fc26 systemd 231-7.fc26 > 231-9.fc26 curl 7.50.3-1.fc26 > 7.50.3-2.fc26 systemd-pam 231-7.fc26 > 231-9.fc26 Additional info: This package is tracked by Koschei. See: http://apps.fedoraproject.org/koschei/package/graphviz
It looks like ghostscript-9.18+ minor incompatibility, but unfortunately I am unable to test it in the rawhide, as it is now heavily broken (deps and also bug 1384777).
Created attachment 1210530 [details] Proposed fix
It's also now reproducible in f25. From what I heard it will be probably also rebased in f23+, strange.
graphviz-2.38.0-39.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-481fbe2f49
graphviz-2.38.0-39.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.