-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gtkdialog does not build with gcc-14 #160
Comments
g_vprintf() is a glib function and it's present in my dpup (Debian testing, glib 2.78). lunar has 2.76, so it should have it too. |
This was Noble which has glib 2.80 ? printing.c needs: https://packages.ubuntu.com/hu/noble/i386/libglib2.0-dev/filelist gprintf.h contains: |
glib 2.70 (2021?) docs say:
If it's been this way for at least 3 years, it needs to be mandatory and not conditional. (The Wayback Machine doesn't have older copies of the glib API docs) |
Searching for gprintf.h within the gtkdialog code base shows that it is not included anywhere. It should be added to printing.h I assume? |
I'd do this in printing.c, it's the only file that uses g_vprintf(). |
Made the update - but although a build was actioned it doesn't seem to have resulted in a new release..... |
build.yml only builds, it doesn't create a tag on success. |
And for a new release generally bump the version number in Line 2 in 967cc40
|
Made release 0.8.5d |
Sadly.... still failing to build gtkdialog with gcc-14:
|
I think variables.c:1122 should be |
The other error, "implicit declaration of yywarning" is less clear without more information. Is your build running bison to overwrite the parser.c file? It think the build shouldn't mess with the included parser.[ch] because they were generated a long time ago with an old bison version. |
Hi Step - thanks for your interest I'm doing a GTK+2 build so the build instructions are:
No mention of bison.... |
it's inconsistent with other functions in this file for puppylinux-woof-CE#160
Hi peebee, please see if PR 161 can help. I can't reproduce your exact environment because I only have access to gcc-12. |
I bet the problem is missing or broken bison or flex and/or a gcc/glibc mismatch (let me guess: mix of Ubuntu and Debian packages). The build passes in a clean EDIT: nope, undefined functions when forcing use of GCC 14 in noble although it defaults to 13 |
Closing this issue for the moment. Have incorporated recent changes (thanks both) and re-released version 0.8.5d. Looks like Ubuntu Noble Numbat is shipping with gcc-13 and gcc-14, although available, is "experimental". |
For reference later: |
Slackware-Current has just moved to GCC-14 |
Line 1258 in 6e46ac6
|
Should return; return a value as per #161 ? |
Depends on Lines 1139 to 1148 in 6e46ac6
|
Applied the patch via a temporary cp - @ line 4 Next problem: maybe line 686: |
Just change it from int to size_t, the types are incorrect
|
Next problems are different for GTK2 and GTK3 builds: fail3-gtk2-gtkdialog.txt fail3-gtk3-gtkdialog.txt |
You can just copy/paste the code here instead of having to download: like so
Demo: something or other
|
OK - going to follow the advice at: and create a gcc wrapper script /usr/bin/gcc:
This "reverts" GCC-14 to GCC-13 behaviour so fixes the problem for now..... but allows gtkdialog to build with GCC-14 However the stricter error checking in GCC-14 is exposing some coding problems in gtkdialog which probably need to be fixed "properly" for the future. |
The code base is ancient . Thunor did what he could and he certainly was a fine programmer, but he's been awol for years. Unfortunately, none of the big distros (apart from pclinuxos - a mandrake fork - and we all know what happened to mandrake) ever picked up on it. Without a few fine software engineers I'm afraid that gtkdialog is on it's last legs. |
These functions return Do you read these build logs before you share them here?
|
Tried building gtkdialog with gcc-14 for NoblePup32 and got:
builds OK with gcc-12 (and I think gcc-13)
The text was updated successfully, but these errors were encountered: