Error installing gtkdialog...

[test0945]

Hi, I'm using Ubuntu 24.04 and when I tried to brew install gtkdialog I got this error message:

/usr/bin/make all-recursive
make[1]: Entering directory '/var/tmp/gtkdialog-20260304-64519-w40cad/gtkdialog-0.8.5e'
Making all in src
make[2]: Entering directory '/var/tmp/gtkdialog-20260304-64519-w40cad/gtkdialog-0.8.5e/src'
/bin/bash ../ylwrap gtkdialog_parser.y y.tab.c gtkdialog_parser.c y.tab.h echo gtkdialog_parser.c | sed -e s/cc$/hh/ -e s/cpp$/hpp/ -e s/cxx$/hxx/ -e s/c++$/h++/ -e s/c$/h/ y.output gtkdialog_parser.output -- yacc -d -p $(basename gtkdialog_parser.c parser.c)
../ylwrap: line 174: yacc: command not found
make[2]: *** [Makefile:570: gtkdialog_parser.c] Error 127
make[2]: Leaving directory '/var/tmp/gtkdialog-20260304-64519-w40cad/gtkdialog-0.8.5e/src'
make[1]: *** [Makefile:430: all-recursive] Error 1
make[1]: Leaving directory '/var/tmp/gtkdialog-20260304-64519-w40cad/gtkdialog-0.8.5e'
make: *** [Makefile:369: all] Error 2

I did successfully install decklinksdk and ffmpeg-ma --with-iec61883. Plus I tried to reinstall texinfo, but I'm still getting the same error above. Any help, please, guys?

[privatezero]

hi @test0945, thanks for reporting - it looks like a dependency is somehow not getting found. It looks like it is failing when it tries to run yacc, which I think might be a related to bison. What is the output of running the command: which bison on your end?

[test0945]

I type which bison on my end and the output is:

/usr/bin/bison

[test0945]

But now after installing bison, when I try again with installing gtkdialog, I get this error this time:

mv -f .deps/attributes.Tpo .deps/attributes.Po
mv -f .deps/widgets.Tpo .deps/widgets.Po
mv -f .deps/stringman.Tpo .deps/stringman.Po
mv -f .deps/gtkdialog.Tpo .deps/gtkdialog.Po
mv -f .deps/actions.Tpo .deps/actions.Po
mv -f .deps/gtkdialog_parser.Tpo .deps/gtkdialog_parser.Po
mv -f .deps/automaton.Tpo .deps/automaton.Po
mv -f .deps/variables.Tpo .deps/variables.Po
mv -f .deps/signals.Tpo .deps/signals.Po
make[3]: Leaving directory '/var/tmp/gtkdialog-20260305-9065-f1u7gx/gtkdialog-0.8.5e/src'
make[2]: *** [Makefile:410: all] Error 2
make[2]: Leaving directory '/var/tmp/gtkdialog-20260305-9065-f1u7gx/gtkdialog-0.8.5e/src'
make[1]: *** [Makefile:430: all-recursive] Error 1
make[1]: Leaving directory '/var/tmp/gtkdialog-20260305-9065-f1u7gx/gtkdialog-0.8.5e'
make: *** [Makefile:369: all] Error 2

[retokromer]

@test0945 Many thanks for reporting.
@privatezero Cound you reproduce?
@privatezero and @dericed What are the pros and cons of sticking with GTK 2, whose support was discontinued in December 2020, instead of switching to GTK 3 or 4?

[privatezero]

@retokromer - no I have not been able to reproduce on my end (but that doesn't surprise me with how mercurial brew installs can be on Linux). I don't have any deep thoughts on my end about GTK versions - I assume one of the newer ones would work with gtkdialog just fine?

[privatezero]

@retokromer I have been able to reproduce the first issue on my end if I remove the version of bison installed via my package manager and attempt to install gtkdialog via brew. On my end at least using a version of bison installed via brew does not fix the issue - it needs bison to be installed through apt.

@test0945 - I'm still not sure what is causing your second issue, but maybe we are having some issues with where linuxbrew is sitting on your path - when you run echo "$PATH" are the .linuxbrew folders sitting at the start of that chain?

[test0945]

Hi, @privatezero.

When I type in echo "$PATH", this is what I get:

/.local/bin:/opt/vapoursynth/bin:/home/linuxbrew/.linuxbrew/bin:/home/linuxbrew/.linuxbrew/sbin:/home/[myusername]/.cargo/bin:/.local/bin:/opt/vapoursynth/bin:/home/[myusername]/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/snap/bin

UPDATE: after editing my .bashrc file by removing a custom script for vapoursynth, here is it now:
/home/linuxbrew/.linuxbrew/bin:/home/linuxbrew/.linuxbrew/sbin:/home/[myusername]/.cargo/bin:/.local/bin:/opt/vapoursynth/bin:/home/[myusername]/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/snap/bin

[iamdamosuzuki]

Hi, I'm getting a similar error when trying to install vrecord on MacOS 26.2:

Last 15 lines from /Users/videolabmini/Library/Logs/Homebrew/gtkdialog/02.make.log:
make[3]: *** [gtkdialog.o] Error 1
make[3]: *** Waiting for unfinished jobs....
mv -f .deps/stringman.Tpo .deps/stringman.Po
mv -f .deps/signals.Tpo .deps/signals.Po
mv -f .deps/actions.Tpo .deps/actions.Po
mv -f .deps/gtkdialog_parser.Tpo .deps/gtkdialog_parser.Po
mv -f .deps/automaton.Tpo .deps/automaton.Po
mv -f .deps/variables.Tpo .deps/variables.Po
mv -f .deps/scrolling.Tpo .deps/scrolling.Po
mv -f .deps/widget_button.Tpo .deps/widget_button.Po
mv -f .deps/widget_checkbox.Tpo .deps/widget_checkbox.Po
mv -f .deps/widget_chooser.Tpo .deps/widget_chooser.Po
make[2]: *** [all] Error 2
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2

[privatezero]

@iamdamosuzuki I've been able to reproduce on macOS 15.7.4 - this seems to be maybe the same as #446. I'll try to poke at things today to see what might have changed

[privatezero]

@dericed, @retokromer, in testing on my end it looks like the fix of adding ENV.append_to_cflags "-Wno-implicit-function-declaration" # Workaround for Xcode 14.3. in f169574 has stopped working for some reason.

Not gonna lie - I did some vibe coding to figure out what might make the compiler happy as a way to fix the old code, but the following patch seems to allow gtkdialog to install via brew on my end. Does this seem like a legit approach?

__END__
--- a/src/gtkdialog.c
+++ b/src/gtkdialog.c
@@ -0,0 +1 @@
+int gtkdialog_parse(void);

[retokromer]

This should be resolved in #447. Please test.

[test0945]

@retokromer I'm really confused. Do I type brew install gtkdialog like usual for testing?

[retokromer]

@test0945 I don't know how you use gtkdialog. If it's via vrecord, what I presume, then reinstall vrecord. Yet if it's stand alone, then indeed use the command you mentioned.