[OE-core] [PATCH 3/7] freetype: upgrade to 2.5.3

[Richard Purdie]

On Wed, 2014-05-14 at 09:27 +0200, Koen Kooi wrote:
> Op 14 mei 2014, om 06:28 heeft Saul Wold <sgw at linux.intel.com> het volgende geschreven:
> 
> > On 05/12/2014 05:14 AM, Ross Burton wrote:
> >> Also drop the redundant definition of S.
> >> 
> > 
> > There seems to be a problem with this update, both native and target fail as follows:
> > 
> >> | /bin/grep: /srv/ssd/builds/world/tmp/sysroots/qemux86-64/usr/lib64/libfreetype.la: No such file or directory
> >> | sed: can't read /srv/ssd/builds/world/tmp/sysroots/qemux86-64/usr/lib64/libfreetype.la: No such file or directory
> >> | x86_64-poky-linux-libtool: link: `/srv/ssd/builds/world/tmp/sysroots/qemux86-64/usr/lib64/libfreetype.la' is not a valid libtool archive
> >> | make: *** [/srv/ssd/builds/world/tmp/work/core2-64-poky-linux/freetype/2.5.3-r0/freetype-2.5.3/objs/libfreetype.la] Error 1
> >> | ERROR: oe_runmake failed
> >> | WARNING: /srv/ssd/builds/world/tmp/work/core2-64-poky-linux/freetype/2.5.3-r0/temp/run.do_compile.17097:1 exit 1 from
> >> |   exit 1
> >> | ERROR: Function failed: do_compile (log file is located at /srv/ssd/builds/world/tmp/work/core2-64-poky-linux/freetype/2.5.3-r0/temp/log.do_compile.17097)
> 
> I noticed the same this morning, but a build from scratch (no sstate
> or sysroots) seems to get past this. It's still running, but
> do_package_write_ipk has succeed for freetype.

Its an odd error, why would a build of freetype be looking into the
sysroot for a freetype.la file?

Its as if there is some kind of bad state in the sysroot referring to
the freetype.la file, I'm not sure what would do that though and why
freetype would pull it in...

Cheers,

Richard