From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Steve Sakoman <steve@sakoman.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: Re-execution of tasks - test report and results
Date: Sat, 31 Mar 2012 17:55:13 +0100 [thread overview]
Message-ID: <1333212913.18082.247.camel@ted> (raw)
In-Reply-To: <CAOSpxdYFKMVW99UNaWvNGwZ+WhSjUXoXD2XCP1zcuOYBcXFCqg@mail.gmail.com>
On Sat, 2012-03-31 at 08:59 -0700, Steve Sakoman wrote:
> On Sat, Mar 31, 2012 at 8:34 AM, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
>
> > Hmm, yes. We already have a bug open against git but I'd like to
> > understand shadow-native and sqlite. If you have the failure logs for
> > those two, I think it would be worth opening bugs for them.
>
> Details for shadow-native and sqlite below:
>
> shadow-native:
>
> | aclocal: unknown warning category `cross'
> | configure.in:496: warning: macro `AM_GNU_GETTEXT_VERSION' not found in library
> | configure.in:497: warning: macro `AM_GNU_GETTEXT' not found in library
> | autoreconf: configure.in: tracing
> | autoreconf: configure.in: AM_GNU_GETTEXT_VERSION is used, but not
> AM_GNU_GETTEXT
> | autoreconf: running: libtoolize --copy --force
> | libtoolize: putting auxiliary files in `.'.
> | libtoolize: copying file `./ltmain.sh'
> | libtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.in and
> | libtoolize: rerunning libtoolize, to keep the correct libtool macros in-tree.
> | libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
> | aclocal: unknown warning category `cross'
> | configure.in:496: warning: macro `AM_GNU_GETTEXT_VERSION' not found in library
> | configure.in:497: warning: macro `AM_GNU_GETTEXT' not found in library
> | autoreconf: running:
> /media/data/yocto/tmp/sysroots/x86_64-linux/usr/bin/autoconf
> --include=/media/data/yocto/tmp/sysroots/x86_64-linux/usr/share/aclocal-1.11
> --include=/media/data/yocto/tmp/work/x86_64-linux/shadow-native-4.1.4.3-r3/shadow-4.1.4.3/aclocal-copy/
> --force --warnings=cross
> | configure.in:496: error: possibly undefined macro: AM_GNU_GETTEXT_VERSION
> | If this token and others are legitimate, please use m4_pattern_allow.
> | See the Autoconf documentation.
> | configure.in:497: error: possibly undefined macro: AM_GNU_GETTEXT
> | autoreconf: /media/data/yocto/tmp/sysroots/x86_64-linux/usr/bin/autoconf
> failed with exit status: 1
> | ERROR: autoreconf execution failed.
> NOTE: package shadow-native-4.1.4.3-r3: task do_configure: Failed
> ERROR: Task 1316
> (/home/steve/source/yocto/poky/meta/recipes-extended/shadow/shadow-native_4.1.4.3.bb,
> do_configure) failed with exit code '1'
This looks like a missing gettext dependency...
> sqlite:
>
> ERROR: Function failed: do_configure (see
> /media/data/yocto/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/sqlite-2.8.17-r7/temp/log.do_configure.20769
> for further information)
> ERROR: Logfile of failure stored in:
> /media/data/yocto/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/sqlite-2.8.17-r7/temp/log.do_configure.20769
> Log data follows:
> | DEBUG: Removing manifest:
> /media/data/yocto/tmp/sysroots/omap3-multi/usr/include/sqlite.h
> | DEBUG: Removing manifest:
> /media/data/yocto/tmp/sysroots/omap3-multi/usr/lib/libsqlite.so.0
> | DEBUG: Removing manifest:
> /media/data/yocto/tmp/sysroots/omap3-multi/usr/lib/libsqlite.so.0.8
> | DEBUG: Removing manifest:
> /media/data/yocto/tmp/sysroots/omap3-multi/usr/lib/libsqlite.so.0.8.6
> | DEBUG: Removing manifest:
> /media/data/yocto/tmp/sysroots/omap3-multi/usr/lib/libsqlite.so
> | DEBUG: Removing manifest:
> /media/data/yocto/tmp/sysroots/omap3-multi/usr/lib/pkgconfig/sqlite.pc
> | DEBUG: Removing manifest:
> /media/data/yocto/tmp/sysroots/omap3-multi/usr/lib/pkgconfig/
> | DEBUG: Removing manifest:
> /media/data/yocto/tmp/sysroots/omap3-multi/usr/include/
> | DEBUG: Removing manifest: /media/data/yocto/tmp/sysroots/omap3-multi/usr/lib/
> | DEBUG: Removing manifest: /media/data/yocto/tmp/sysroots/omap3-multi/usr/
> | DEBUG: SITE files ['endian-little', 'bit-32', 'arm-common',
> 'common-linux', 'common-glibc', 'arm-linux', 'arm-linux-gnueabi',
> 'common']
> | ERROR: Function failed: do_configure (see
> /media/data/yocto/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/sqlite-2.8.17-r7/temp/log.do_configure.20769
> for further information)
> | main.mk is patched, no need to configure
> | mv: cannot stat
> `/media/data/yocto/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/sqlite-2.8.17-r7/sqlite.pc':
> No such file or directory
> NOTE: package sqlite-2.8.17-r7: task do_configure: Failed
> ERROR: Task 1673
> (/home/steve/source/yocto/poky/meta-openembedded/meta-oe/recipes-support/sqlite/sqlite_2.8.17.bb,
> do_configure) failed with exit code '1'
I've just realised, this is from meta-oe, not OE-Core. sqlite3 doesn't
seem to have this problem...
Cheers,
Richard
next prev parent reply other threads:[~2012-03-31 17:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-31 14:07 Re-execution of tasks - test report and results Richard Purdie
2012-03-31 15:04 ` Steve Sakoman
2012-03-31 15:34 ` Richard Purdie
2012-03-31 15:59 ` Steve Sakoman
2012-03-31 16:55 ` Richard Purdie [this message]
2012-04-02 3:45 ` Richard Purdie
2012-04-02 9:02 ` Paul Eggleton
2012-04-02 11:59 ` Richard Purdie
2012-04-06 18:56 ` Otavio Salvador
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1333212913.18082.247.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=steve@sakoman.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox