FS#53868 - [ogre] libOgreOverlay.so links to non-existing libfreetype.so.2.6
Attached to Project:
Community Packages
Opened by Maarten de Vries (de-vri-es) - Friday, 28 April 2017, 11:26 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Sunday, 30 April 2017, 17:09 GMT
Opened by Maarten de Vries (de-vri-es) - Friday, 28 April 2017, 11:26 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Sunday, 30 April 2017, 17:09 GMT
|
Details
The file libOgreOverlay.so from ogre-1.10.4-1 links to
libfreetype.so.2.6, which doesn't exist. Rebuilding in a
clean chroot solved the problem. Considering the build date
of freetype2 from the repository, it looks like the ogre
package was not built in a clean chroot but on a system with
a local installation of freetype.
ldd output of the repository version: $ ldd /usr/lib/libOgreOverlay.so ... libfreetype.so.2.6 => not found ... After rebuilding in a clean chroot: $ ldd /usr/lib/libOgreOverlay.so ... libfreetype.so.6 => /usr/lib/libfreetype.so.6 ... |
This task depends upon
Comment by
Maarten de Vries (de-vri-es) -
Friday, 28 April 2017, 11:28 GMT
Comment by
Sven-Hendrik Haase (Svenstaro) -
Saturday, 29 April 2017, 05:11 GMT
Comment by
Maarten de Vries (de-vri-es) -
Saturday, 29 April 2017, 09:36 GMT
Comment by
Sven-Hendrik Haase (Svenstaro) -
Saturday, 29 April 2017, 10:09 GMT
Comment by
Maarten de Vries (de-vri-es) -
Saturday, 29 April 2017, 19:58 GMT
Comment by
Sven-Hendrik Haase (Svenstaro) -
Sunday, 30 April 2017, 17:07 GMT
I should have filed this under community packages.. Sorry :(
I built it in a clean chroot (as does everyone with all Arch
packages) and then I rebuilt it and it came out the same. I wonder
what that is about.
That is really weird. Maybe you could try deleting the chroot and
making it again? Or a new chroot at a different location.
I figured it out. Ogre builds its own freetype which happens to be
of this version. I'm going to have to fix that.
That's also odd. When I build the package with extra-x86_64-build
I have no linking problems. Not sure if that is the correct script
for community packages though.
The trick is to use -DOGRE_BUILD_DEPENDENCIES=FALSE. Fixed.