GNOME Bugzilla – Bug 358758
Compile issues due to incompatible pointer types
Last modified: 2006-10-06 16:28:31 UTC
While compiling gnome-pilot-2.0.14 with pilot-link-0.12.0-pre2 and gcc-4.1.1 I get this compilation error. ccache cc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -DG_LOG_DOMAIN=\"gpilotd\" -DGP_PILOT_LINK_VERSION=\"..\" -DDEVICE_XML_DIR=\"/usr/test/garnome2/share/gnome-pilot\" -DGNOMELOCALEDIR=\"/usr/test/garnome2/share/locale\" -DORBIT2=1 -pthread -I/usr/test/garnome2/include/libxml2 -I/usr/test/garnome2/include/libgnome-2.0 -I/usr/test/garnome2/include/glib-2.0 -I/usr/test/garnome2/lib/glib-2.0/include -I/usr/test/garnome2/include/orbit-2.0 -I/usr/test/garnome2/include/libbonobo-2.0 -I/usr/test/garnome2/include/gconf/2 -I/usr/test/garnome2/include/gnome-vfs-2.0 -I/usr/test/garnome2/lib/gnome-vfs-2.0/include -I/usr/test/garnome2/include/bonobo-activation-2.0 -I/usr/test/garnome2/include/libgnomeui-2.0 -I/usr/test/garnome2/include/libgnomecanvas-2.0 -I/usr/test/garnome2/include/gtk-2.0 -I/usr/test/garnome2/include/libart-2.0 -I/usr/test/garnome2/include/libbonoboui-2.0 -I/usr/test/garnome2/include/gnome-keyring-1 -I/usr/test/garnome2/include/pango-1.0 -I/usr/test/garnome2/include -I/usr/test/garnome2/include/freetype2 -I/usr/test/garnome2/lib/gtk-2.0/include -I/usr/test/garnome2/include/atk-1.0 -I/usr/test/garnome2/include/cairo -I/usr/test/garnome2/include/libglade-2.0 -I/usr/local/include -I/usr/X11R6/include -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/test/garnome2/include/dbus-1.0 -I/usr/test/garnome2/lib/dbus-1.0/include -I/usr/test/garnome2/include/glib-2.0 -I/usr/test/garnome2/lib/glib-2.0/include -I/usr/test/garnome2/include/hal -I/usr/test/garnome2/include -g -I/usr/test/garnome2/include -L/usr/test/garnome2/lib -O2 -pipe -m3dnow -mtune=athlon-tbird -Wall -Wmissing-prototypes -MT gnome-pilot-structures.lo -MD -MP -MF .deps/gnome-pilot-structures.Tpo -c gnome-pilot-structures.c -fPIC -DPIC -o .libs/gnome-pilot-structures.o gnome-pilot-structures.c: In function 'gpilot_network_device_init': gnome-pilot-structures.c:439: warning: passing argument 2 of 'pi_bind' from incompatible pointer type gnome-pilot-structures.c:439: error: too many arguments to function 'pi_bind'
It seems that gnome-pilot isn't detecting that you have a 0.12.x - based version of pilot-link. There are a couple of possible reasons. Have you re-run ./configure? Does it report that it is compiling against pilot-link 0.12.x? You shouldn't be using pilot-link-0.12.0-pre2. That pre-release version is now superceded by the released pilot-link 0.12.1. It is possible (I haven't checked) that the pilot-link header files in 0.12.x have changed since 0.12.0-pre2, and that gnome-pilot-2.0.14 can't properly detect the pilot-link version in 0.12.0-pre2. I strongly recommend upgrading to pilot-link 0.12.1. You will have pain with 0.12.0-pre2! Please update this ticket to let us know if you have problems with gp-2.0.14 and pl-0.12.1.
update: I just compiled 2.0.14 against 0.12.0pre2. I had to change one line in pilot-link source to get it to compile (a variable was static, and I had to change delete the static keyword, ugh.). I got: > ./configure --with-pisock=/tmp/pl0.12.0pre2 [...] Configuration : gnome-vfs : yes network sync : yes usb : yes HAL/DBUS : yes gob : yes pilot-link : 0.12.0-pre2 > make (no errors). If you've still got problems, check that gnome-pilot-2.0.14/config.h contains the line: "#define PILOT_LINK_0_12"
Things are not looking very bright :-( I don't see the mention of #define PILOT_LINK_0_12 in the config.h file nor do I see pilot-link with a version number. I did compile pilot-link-0.12.1 as you suggested which sounded like a very good idea as the version that I had was ancient but the file in /usr/local/lib/pkgconfig for pilot-link isn't picked up correctly while the PKG_CONFIG_PATH does point into the folder and other programs do compile correctly using other libs that are stored in that location.
If gnome-pilot 2.0.14 isn't finding your newly compiled (and installed?) pilot-link 0.12.1, then you can tell gnome-pilot the location of your pilot-link using the "--with-pisock" option to the configure script. e.g.: ./configure --with-pisock=/usr/local I don't think gnome-pilot uses pilot-link's pkgconfig setup. Maybe because it didn't exist when the g-p build script was put together.
That definatly solved the issue adding ./configure --with-pisock=/usr/local :-D very strange that gnome-pilot doesn't use pkgconfig as it's source of truth
From a quick look at the pilot-link source, it seems that the pilot-link pkgconfig support is new in 0.12.x. Thus, it would be impossible to support 0.11.8 if we relied on pkgconfig. Presumably you have a conflicting pilot-link installation that is getting picked up first (in /usr?), so presumably gnome-pilot would have found your /usr pkgconfig info if it used pkgconfig anyway! Glad --with-pisock solved your problem. ./configure --help is always worth a look :)