[gentoo-dev] freetype related build errors

[gentoo-dev] freetype related build errors

[John Newman]

When I'm attempting to build seemingly any package that needs
libfreetype I get these errors at the bottom of the build:

# emerge libwnck
Calculating dependencies ...done!
>>> emerge x11-libs/libwnck-0.17 to /

[ snip ]

/usr/lib/libpangoxft-1.0.so: undefined reference to `FT_Seek_Stream'
/usr/lib/libpangoxft-1.0.so: undefined reference to `FT_Get_Short'
/usr/lib/libpangoxft-1.0.so: undefined reference to `FT_Forget_Frame'
/usr/lib/libpangoxft-1.0.so: undefined reference to `FT_Access_Frame'
/usr/lib/libpangoxft-1.0.so: undefined reference to `FT_Get_Long'
collect2: ld returned 1 exit status
make[2]: *** [test-wnck] Error 1
make[2]: Leaving directory
`/usr/tmp/portage/libwnck-0.17/work/libwnck-0.17/libwnck'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory
`/usr/tmp/portage/libwnck-0.17/work/libwnck-0.17'
make: *** [all-recursive-am] Error 2

I found the symbolds:

nm /usr/X11R6/lib/libfreetype.a | egrep 'FT_(Seek_Stream|Get_Short)'

00005068 T FT_Get_Short
0000511c T FT_Get_ShortLE
00004e44 T FT_Seek_Stream

This is obviously keeping me from building gnome and lots and lots
of other packages :)  I currently have freetype-2.0.9 and
freetype-2.1.2-r1 installed.  I've tried uninstalling the 2.0.9
version and reinstalling both versions and I still get the
exact same build error on other packages.   Anybody have any idea
whats causing this?  The only way I've found to fix the packages
that are blowing up is to manually add /usr/X11R6/lib/libfreetype.a
to the end of the final gcc line and then to emerge -i the package
to insert a stub so that portage knows its installed.


-- 
john

Re: [gentoo-dev] freetype related build errors

[Spider]

[-- Attachment #1: Type: text/plain, Size: 1335 bytes --]

begin  quote
On Thu, 24 Oct 2002 17:08:47 -0500
John Newman <jnn@cachehit.net> wrote:

> When I'm attempting to build seemingly any package that needs
> libfreetype I get these errors at the bottom of the build:
> 
> 
> This is obviously keeping me from building gnome and lots and lots
> of other packages :)  I currently have freetype-2.0.9 and
> freetype-2.1.2-r1 installed.  I've tried uninstalling the 2.0.9
> version and reinstalling both versions and I still get the
> exact same build error on other packages.   Anybody have any idea
> whats causing this?  The only way I've found to fix the packages
> that are blowing up is to manually add /usr/X11R6/lib/libfreetype.a
> to the end of the final gcc line and then to emerge -i the package
> to insert a stub so that portage knows its installed.
> 
> 

this isn't pretty.. .the package appears to build with the freetype
2.1.x headers from /usr/lib.. and then at the final link stage it uses
the /usr/X11...  version of freetype, and thats where it breaks.  I've
had a few bugs like this but I've never been able to solve this.  all
discussion is welcome and I know this isn't what you'd want to hear from
the devs  : (

//Spider


--
begin  .signature
This is a .signature virus! Please copy me into your .signature!
See Microsoft KB Article Q265230 for more information.
end

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-dev] freetype related build errors

[John Newman]

On Fri, Oct 25, 2002 at 01:57:29AM +0200, Spider wrote:
> this isn't pretty.. .the package appears to build with the freetype
> 2.1.x headers from /usr/lib.. and then at the final link stage it uses
> the /usr/X11...  version of freetype, and thats where it breaks.  I've
> had a few bugs like this but I've never been able to solve this.  all
> discussion is welcome and I know this isn't what you'd want to hear from
> the devs  : (

Anybody have any ideas on what I can do to fix this?  In my case it is
making portage pretty unusable for X11 apps, which blows.

--
john

Re: [gentoo-dev] freetype related build errors

[John Newman]

On Sat, Oct 26, 2002 at 02:24:04PM -0500, John Newman wrote:
> On Fri, Oct 25, 2002 at 01:57:29AM +0200, Spider wrote:
> > this isn't pretty.. .the package appears to build with the freetype
> > 2.1.x headers from /usr/lib.. and then at the final link stage it uses
> > the /usr/X11...  version of freetype, and thats where it breaks.  I've
> > had a few bugs like this but I've never been able to solve this.  all
> > discussion is welcome and I know this isn't what you'd want to hear from
> > the devs  : (
> 
> Anybody have any ideas on what I can do to fix this?  In my case it is
> making portage pretty unusable for X11 apps, which blows.

I mv'd the /usr/lib/libfreetype* out of /usr/lib, did the same with 
/usr/include/freetype*, and left everything in /usr/X11R6 and everything
seems to emerge properly now.  

-- 
john