On Wed, Sep 24, 2008 at 10:06:14AM -0400, Alexander Hansen wrote:
> Ben Abbott wrote:
> >> $ fink install gtkglext1
> >> [...]
> >> checking for gtk+-2.0 >= 2.0.0 gdk-2.0 >= 2.0.0 pango >= 1.0.0  
> >> gmodule-2.0 >= 2.0.0 ... yes
> >> checking BASE_DEPENDENCIES_CFLAGS... -I/sw/lib/pango-ft219/include/ 
> >> pango-1.0 -I/sw/lib/fontconfig2/include -I/sw/lib/freetype219/ 
> >> include/freetype2 -I/sw/lib/freetype219/include -I/sw/include/ 
> >> glib-2.0 -I/sw/lib/glib-2.0/include -I/sw/include/pixman-1 -I/sw/ 
> >> include/libpng12 -I/sw/include -I/sw/include/cairo -I/sw/include/ 
> >> gtk-2.0 -I/sw/lib/gtk-2.0/include -I/sw/include/atk-1.0 -I/usr/X11R6/ 
> >> include -I/usr/X11/include
> >> checking BASE_DEPENDENCIES_LIBS... -L/sw/lib/pango-ft219/lib -L/sw/ 
> >> lib/fontconfig2/lib -L/sw/lib/freetype219/lib -L/sw/lib -L/usr/X11R6/ 
> >> lib -L/usr/X11/lib -Wl,-framework,CoreServices -Wl,- 
> >> framework,ApplicationServices -lgtk-x11-2.0 -latk-1.0 -lgdk-x11-2.0 - 
> >> lgdk_pixbuf-2.0 -lpangocairo-1.0 -lXrender -lX11 -lXext -lXinerama - 
> >> lXrandr -lXcursor -lXcomposite -lXdamage -lcairo -lpangoft2-1.0 - 
> >> lfreetype -lz -lfontconfig -lXfixes -lpango-1.0 -lm -lgobject-2.0 - 
> >> lgmodule-2.0 -lglib-2.0 -lintl -liconv
> >> checking for pkg-config... (cached) /sw/bin/pkg-config
> >> checking for GLIB - version >= 2.0.0... yes (version 2.14.6)
> >> checking for pkg-config... (cached) /sw/bin/pkg-config
> >> checking for GTK+ - version >= 2.0.0... no
> >> *** Could not run GTK+ test program, checking why...
> >> *** The test program compiled, but did not run. This usually means
> >> *** that the run-time linker is not finding GTK+ or finding the wrong
> >> *** version of GTK+. If it is not finding GTK+, you'll need to set  
> >> your
> >> *** LD_LIBRARY_PATH environment variable, or edit /etc/ld.so.conf to  
> >> point
> >> *** to the installed location  Also, make sure you have run ldconfig  
> >> if that
> >> *** is required on your system
> >> ***
> >> *** If you have an old version installed, it is best to remove it,  
> >> although
> >> *** you may also be able to get things to work by modifying  
> >> LD_LIBRARY_PATH
> >> configure: error: GTK+ 2.0 not found
> >> ### execution of ./configure failed, exit code 1
> >> Removing runtime build-lock...
> >> Removing build-lock package...
> >> /sw/bin/dpkg-lockwait -r fink-buildlock-gtkglext1-1.0.6-1008
> >> (Reading database ... 142426 files and directories currently  
> >> installed.)
> >> Removing fink-buildlock-gtkglext1-1.0.6-1008 ...
> >> Failed: phase compiling: gtkglext1-1.0.6-1008 failed
> >>     
> >
> > Of the two itemized problems, it doesn't appear that I have a wrong  
> > version.
> >
> >   
> >> $ fink list gtk+
> >> Information about 7216 packages read in 1 seconds.
> >>      gtk+                          1.2.10-51              The Gimp  
> >> Toolkit
> >>      gtk+-data                     1.2.10-51              The Gimp  
> >> Toolkit
> >>      gtk+-shlibs                   1.2.10-51              The Gimp  
> >> Toolkit
> >>  i   gtk+2                         2.12.11-2              The Gimp  
> >> Toolkit
> >>  i   gtk+2-dev                     2.12.11-2              The Gimp  
> >> Toolkit
> >>  i   gtk+2-shlibs                  2.12.11-2              The Gimp  
> >> Toolkit
> >>      gtk+extra17                   0.99.17-14             Useful  
> >> widgets for creating GUI's using GTK+
> >>      gtk+extra17-shlibs            0.99.17-14             Useful  
> >> widgets for creating GUI's using GTK+
> >>     
> >
> > So my question is; Is the problem really with LD_LIBRARY_PATH?
> >
> > and if so; What is the proper LD_LIBRARY_PATH to set in my environment?
> >
> > TiA
> > Ben
> >
> >
> >   
> I don't even know if LD_LIBRARY_PATH does anything on OS X, and even if
> it did, Fink would unset your setting of it before building.  That
> message is targeted toward building the package manually on Linux.
> 
> Check the config.log file in the gtkglext1 build directory.  When
> validating packages off the tracker via clean builds, I've often
> encountered issues where the message that came up was the same as what
> you're seeing, but the problem was that something else altogether was
> missing.

Often caused by installing an OS X update that overwrites some files
from xquartz. "If you had previously installed xquartz, reinstall it"
is always good after OS X updates.

dan

-- 
Daniel Macks
[EMAIL PROTECTED]
http://www.netspace.org/~dmacks


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Fink-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fink-users

Reply via email to