SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I am trying to create avahi slackbuild package on Slackware 14.1 (avah-0.6.31), but I got the following error when the ./avahi-SlackBuild script is running.
make[2]: Entering directory `/tmp/SBo/avahi-0.6.31/avahi-discover-standalone'
CC avahi_discover_standalone-main.o
main.c:31:21: fatal error: gtk/gtk.h: No such file or directory
#include <gtk/gtk.h>
I have installed packages:
gtk+-1.2.10-i486-5
gtk+2-2.24.20-i486-1
gtk+3-3.8.2-i486-2
and they are all have gtk.h file. However the gtk.h files and gtk directory are all located under
/usr/include/gtk-1.2,
/usr/include/gtk-2.0,
and
/usr/include/gtk-3.0
No such thing as /usr/include/gtk/gtk.h
I look at the main.c of the avahi-discover-standalone directory and the #include definition is <gtk/gtk.h>
I can probably modify this to <gtk-1.2/gtk/gtk.h> or something similar, however how do I know which gtk.h header to use (1.2,2.0 or 3.0) ?
You'll have to Ctrl-C it or it'll scroll on by and you'll never see it again.
Another thing you can check is the config.log in the /tmp/SBo/avahi-0.6.31/ directory.
Its huge, be ready. What I'd do is go to the very end, then search up until I see something to do with an error in gtk. There will be errors in there but the script will correct for them, its expected to see some errors. (Things like when it searched for Mono for example)
Last edited by codeguy; 05-24-2015 at 09:18 AM.
Reason: Snipped super long CFLAGS to fix formatting
prefix: /usr sysconfdir: /etc localstatedir: /var avahi socket: /var/run/avahi-daemon/socket dbus-1 system.d dir: /etc/dbus-1/system.d dbus-1 version: 1.6.12 dbus-1 system socket: unix:path=/var/run/dbus/system_bus_socket C Compiler: gcc -std=gnu99 CFLAGS: -O2 -march=i486 -mtune=i686 -fstack-protector -std=c99 -Wall -W -Wextra -pedantic -pipe -Wformat -Wold-style-definition -Wdeclaration-after-statement -Wfloat-equal -Wmissing-declarations -Wmissing-prototypes -Wstrict-prototypes -Wredundant-decls -Wmissing-noreturn -Wshadow -Wendif-labels -Wpointer-arith -Wbad-function-cast -Wcast-qual -Wcast-align -Wwrite-strings -fdiagnostics-show-option -Wno-cast-qual -fno-strict-aliasing Enable GLIB: yes Enable GLIB GObject: yes Enable GObject Introspection: yes Enable GTK 2.0: yes Enable GTK 3.0: yes Enable D-Bus: yes With XML: expat Enable GDBM: yes Enable DBM: no Enable libdaemon: yes Enable Python: yes Enable pygtk: yes Enable python-dbus: yes Enable QT3: no Enable QT4: yes Enable Mono: no Enable Monodoc: no Distribution/OS: slackware User for avahi-daemon: avahi Group for avahi-daemon: avahi Priviliged access group for Avahi clients: netdev User for avahi-autoipd: avahi-autoipd Group for avahi-autoipd: avahi-autoipd Enable chroot(): no Enable Linux inotify: yes Enable stack-smashing protection: yes systemd unit directory:
Building libavahi-core yes Building avahi-daemon: yes Building avahi-dnsconfd: yes Building libavahi-client: yes Building avahi-utils: yes Building avahi-python: yes Building libavahi-glib: yes Building libavahi-gobject: yes Building avahi-discover-standalone: yes Building libavahi-qt3: no Building libavahi-qt4: yes Building avahi-sharp: no Building avahi-compat-libdns_sd: yes Building avahi-compat-howl: yes Building tests: yes Building avahi-core documentation: yes Building avahi-autoipd: no Building libavahi-ui: yes
Should not be that GTK20_CFLAGS ='-I/usr/include/gtk-1.2 -I/usr/include/glib-1.2 -I/usr/lib/glib/include' instead of just empty ?
But how do I fix that ?
One question I have, is the main.c on under 'avahi-discover-standalone' directory is hardcoded or is it created on the fly by configure process ?
What your #include looks like ?
sorry aherrys, looking at an (a few days) older post from you, it seems to me that you are trying to do a minimal install and if building fails it can be because you are missing something: consider that avahi from SBo (as any other script from there) has been tested on a full installation of slackware stable and any other platform is just unsupported (as debugging individual problems can become extremely painful).
that said, good luck!
P.S. the best compromise I can suggest is to create a full install in a virtual machine, build what you need there and move the packages on your minimal one.
obviously, you can also use the full install in the virtual machine to be able to do the tests you are asking above and so be able to debug stuff yourself...
sorry aherrys, looking at an (a few days) older post from you, it seems to me that you are trying to do a minimal install and if building fails it can be because you are missing something
[snip]
In a minimal install environment, pkg-config can be quite useful because it will fail and describe what is missing if some dependency if not installed. Try running 'pkg-config --cflags-only-I gtk+-2.0'
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.