I'm trying to compile a program (opencpn-1.3.4 from SourceForge)* and after I run the ./configure command, all goes well until I get this
*** Could not run GTK+ test program, checking why...
The full output is...
++++++++++++++++++++++
[pork@localhost opencpn-1.3.4]$ ./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking whether gcc needs -traditional... no
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking how to run the C++ preprocessor... g++ -E
checking how to run the C preprocessor... gcc -E
checking for a BSD-compatible install... /usr/bin/install -c
checking for SSP support/disable... yes
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for useable OpenGLU Library
checking for gluNewTess in -lGLU... yes
checking wxWidgets wx-config... wx-config
checking wxWidgets version... 2.8.10
checking for wxWidgets location... /usr
checking for wxWidgets release (major, minor) number... 2.8
checking for wxWidgets setup header... /usr/lib/wx/include/
/usr/lib/wx/include/gtk2-unicode-release-2.8/wx/setup.h
checking for __WXX11__... no
checking for __WXGTK__... yes
checking for pkg-config... /usr/bin/pkg-config
checking for GTK+ - version >= 2.0.0... yes
checking for libgtk2.0-dev include files... yes
checking for cairo.h in include path... yes
checking for GTK+-2.0 test compile and run...
checking for GTK+ version...
checking for pkg-config... /usr/bin/pkg-config
checking for GTK+ - version >= 2.0.0... no
*** Could not run GTK+ test program, checking why...
*** The test program failed to compile or link. See the file config.log for the
*** exact error that occured. This usually means GTK+ is incorrectly installed.
configure: creating ./config.status
config.status: creating Makefile
config.status: executing depfiles commands
[pork@localhost opencpn-1.3.4]$
++++++++++++++++++++++
Now, about 8 lines up from the bottom, it says "checking for GTK+ - version >= 2.0.0... no"
But, earlier it says "checking for GTK+ - version >= 2.0.0... yes"
The config.log file is singularly uninstructive as to what the root cause is. I've don any amount of googling about and all I seem to see are messages saying to install this or that set of headers, which the trace above seems to say I have already. All I can think is that maybe, just maybe, there's a config issue on my system where I do have all I need but haven't indicated where these all are to the compiler. Or, I could be completely wrong.
Ideas, anyone? And in your responses assume you're dealing with an idiot who's just smart enough to have ditched Windows about a year or two ago. PCLinuxOS was my first foray into linux-land but not my only one by far, and I'm still here.
*For the curious - opencpn is an opensource chartplotter/navigation tool, great for those who enjoy messing about in boats. V 1.3.2 was packaged as an RPM by some kind soul but the latest version hasn't been, which is why I ended up trying to compile from source as there were enhancements that I needed. That and I though it's be fun to try. I even had the daft idea of learning to package and taking on responsibility for maintaining the package. Another learning curve there doubtless - but **someone** has to do it....
