Re: [Devel] Bad problems due to function renaming

[Owen Taylor]

On Thu, 2003-11-13 at 09:13, Tim Ruehsen wrote:
> > > Just to show you the problem with libpango:
> > > ldd -r /usr/lib/libpangoft2-1.0.so.0
> > >         libgobject-2.0.so.0 => /usr/lib/libgobject-2.0.so.0 (0x40048000)
> > >         libgmodule-2.0.so.0 => /usr/lib/libgmodule-2.0.so.0 (0x40080000)
> > >         libdl.so.2 => /lib/libdl.so.2 (0x40085000)
> > >         libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0x40088000)
> > >         libpango-1.0.so.0 => /usr/lib/libpango-1.0.so.0 (0x400f3000)
> > >         libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0x40125000)
> > >         libc.so.6 => /lib/i686/libc.so.6 (0x40176000)
> > >         /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000)
> > > undefined symbol: FT_Seek_Stream        (/usr/lib/libpangoft2-1.0.so.0)
> > > undefined symbol: FT_Get_Short  (/usr/lib/libpangoft2-1.0.so.0)
> > > undefined symbol: FT_Forget_Frame       (/usr/lib/libpangoft2-1.0.so.0)
> > > undefined symbol: FT_Access_Frame       (/usr/lib/libpangoft2-1.0.so.0)
> > > undefined symbol: FT_Get_Long   (/usr/lib/libpangoft2-1.0.so.0)
> >
> > Pango *does* use these symbols directly (as part of some low-level
> > OpenType table code.) They are clearly internal symbols, so we didn't
> > expect compatibility guarantees for them.
> 
> OK. Just to understand it: how comes that there are no compiler errors when 
> compiling pango with freetype 2.1.x includes? 

Pango uses different symbols depending on the version of FreeType it's
being compiled against (there are compatibility #defines)

Regards,
                                                Owen