Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 4864 - gtk+-2.0.5-r1 wont emerge - pango not found
Summary: gtk+-2.0.5-r1 wont emerge - pango not found
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Library (show other bugs)
Hardware: x86 Linux
: Normal blocker (vote)
Assignee: Gabriele Giorgetti
URL:
Whiteboard:
Keywords:
: 4899 (view as bug list)
Depends on:
Blocks:
 
Reported: 2002-07-11 10:09 UTC by Francis Koclas
Modified: 2003-02-04 19:42 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Francis Koclas 2002-07-11 10:09:47 UTC
While trying to emerge gtk+-2.0.5-r1
( with GCC 2.95.3-r7 )


checking Pango flags...   -I/usr/include/pango-1.0 -I/usr/X11R6/include
-I/usr/include/freetype2 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include   
 -lpangoxft-1.0 -lpangox-1.0 -lpango-1.0 -lgobject-2.0 -lgmodule-2.0 -ldl
-lglib-2.0  
checking for pango_context_new in -lpango-1.0... no
configure: error:
*** Can't link to Pango. Pango is required to build
*** GTK+. For more information see http://www.pango.org
!!! ERROR: The ebuild did not complete successfully.
!!! Function src_compile, Line 47, Exitcode 1
!!! (no error message)
!!! emerge aborting on  /usr/portage/x11-libs/gtk+/gtk+-2.0.5-r1.ebuild .


Pango *is* emerged fine.
It's been doing this for over a month

_______

User kerb on #gentoo reported this problem, I reported it for him tho
Comment 1 Gabriele Giorgetti 2002-07-11 18:55:00 UTC
Pasting the user's ChangeLog for further reference:

configure:16973: checking Pango flags
configure:16979: result:   -I/usr/include/pango-1.0 -I/usr/X11R6/include
-I/usr/include/freetype2 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include    
-lpangoxft-1.0 -lpangox-1.0 -lpango-1.0 -lgobject-2.0 -lgmodule-2.0 -ldl
-lglib-2.0  
configure:17002: checking for pango_context_new in -lpango-1.0
configure:17035: i586-pc-linux-gnu-gcc -o conftest -mcpu=i586 -march=i586 -O3
-pipe -g -Wall   -I/usr/include/pango-1.0 -I/usr/X11R6/include
-I/usr/include/freetype2 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include    
conftest.c -lpango-1.0   -lpangoxft-1.0 -lpangox-1.0 -lpango-1.0 -lgobject-2.0
-lgmodule-2.0 -ldl -lglib-2.0     >&5
/usr/lib/libpangoxft-1.0.so: undefined reference to `FT_Stream_GetShort'
/usr/lib/libpangoxft-1.0.so: undefined reference to `FT_Stream_ExitFrame'
/usr/lib/libpangoxft-1.0.so: undefined reference to `FT_Stream_GetLong'
/usr/lib/libpangoxft-1.0.so: undefined reference to `FT_Stream_Seek'
/usr/lib/libpangoxft-1.0.so: undefined reference to `FT_Stream_EnterFrame'
collect2: ld returned 1 exit status
configure:17038: $? = 1
configure: failed program was:
#line 17009 "configure"
#include "confdefs.h"

Comment 2 Gabriele Giorgetti 2002-07-11 18:57:51 UTC
/* Override any gcc2 internal prototype to avoid an error.  */
#ifdef __cplusplus
extern "C"
#endif
/* We use char because int might match the return type of a gcc2
   builtin and then its argument prototype would still apply.  */
char pango_context_new ();
#ifdef F77_DUMMY_MAIN
#  ifdef __cplusplus
     extern "C"
#  endif
   int F77_DUMMY_MAIN() { return 1; }
#endif
int
main ()
{
pango_context_new ();
  ;
  return 0;
}
configure:17055: result: no
configure:17062: error:
*** Can't link to Pango. Pango is required to build
*** GTK+. For more information see http://www.pango.org
Comment 3 Gabriele Giorgetti 2002-07-11 19:00:21 UTC
Also, user  said emerge unmerge pango didn't fix that.
Comment 4 Gabriele Giorgetti 2002-07-11 19:30:47 UTC
Ok my guess here is that you have a broken libXft
I think that you should emerge xfree again to fix that.
Also mjc (at gentoo.org) said that he had the same error once, and
emerging xfree fixed it.

Well then, please re-emerge xfree and reopen this bug if you are 
still getting the same error.


(CC'ing this one to Azarah...too)


Comment 5 Gabriele Giorgetti 2002-07-12 05:45:22 UTC
*** Bug 4899 has been marked as a duplicate of this bug. ***