[oe] [meta-oe][meta-filesystems][PATCH 1/2] libimobiledevice: remove runtime configure check

S. Lockwood-Childs sjl at vctlabs.com
Fri Oct 2 04:49:48 UTC 2015


On Thu, Oct 01, 2015 at 05:06:45PM +0200, Martin Jansa wrote:
> On Fri, Jul 17, 2015 at 05:38:12PM -0700, S. Lockwood-Childs wrote:
> > configure.ac had a runtime check for large file support that got run
> > on 64-bit architectures, and all runtime checks must go away to be
> > cross-compile safe.
> > 
> > Luckily that runtime check was extraneous, so just remove it;
> > standard AC_SYS_LARGEFILE macro should be sufficient for figuring out
> > proper settings to get large file support.
> > 
> > Also un-blacklist libimobiledevice, since this problem was the
> > reason for the blacklist.
> 
> There is another issue, probably triggered by switch to gcc-5, are you
> willing to fix it?
> 
> | /home/jenkins/oe/world/shr-core/tmp-glibc/work/armv5te-oe-linux-gnueabi/libimobiledevice/1.1.4-r0/libimobiledevice-1.1.4/src/afc.c:258: error: undefined reference to 'debug_buffer'
> | /home/jenkins/oe/world/shr-core/tmp-glibc/work/armv5te-oe-linux-gnueabi/libimobiledevice/1.1.4-r0/libimobiledevice-1.1.4/src/afc.c:273: error: undefined reference to 'debug_buffer'
> | /home/jenkins/oe/world/shr-core/tmp-glibc/work/armv5te-oe-linux-gnueabi/libimobiledevice/1.1.4-r0/libimobiledevice-1.1.4/src/afc.c:247: error: undefined reference to 'debug_buffer'
> | /home/jenkins/oe/world/shr-core/tmp-glibc/work/armv5te-oe-linux-gnueabi/libimobiledevice/1.1.4-r0/libimobiledevice-1.1.4/src/afc.c:258: error: undefined reference to 'debug_buffer'
> | collect2: error: ld returned 1 exit status
> | make[2]: *** [libimobiledevice.la] Error 1
> | make[2]: Leaving directory `/home/jenkins/oe/world/shr-core/tmp-glibc/work/armv5te-oe-linux-gnueabi/libimobiledevice/1.1.4-r0/build/src'
> | make[1]: *** [all-recursive] Error 1
> | make[1]: Leaving directory `/home/jenkins/oe/world/shr-core/tmp-glibc/work/armv5te-oe-linux-gnueabi/libimobiledevice/1.1.4-r0/build'
> | make: *** [all] Error 2
> 
> otherwise I'll blacklist it again in few days (it was reported in couple world builds already).

Yes, I can take a look this weekend. Thanks for the heads up.



More information about the Openembedded-devel mailing list