From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Gary Thomas <gary@mlbassoc.com>
Cc: Yocto Project <yocto@yoctoproject.org>
Subject: Re: fetchall strangeness
Date: Tue, 08 Apr 2014 15:11:34 +0100 [thread overview]
Message-ID: <1396966294.24597.106.camel@ted> (raw)
In-Reply-To: <5343F995.4080402@mlbassoc.com>
On Tue, 2014-04-08 at 07:28 -0600, Gary Thomas wrote:
> I just ran 'bitbake <image> -c fetchall' in a clean build tree
> and noticed that this builds a bunch of native packages:
>
> $ ls -l tmp/work/*/*/*/temp/log.do_compile.*
> -rw-r--r-- 1 gary develop 76530 Apr 8 14:17 tmp/work/i686-linux/apr-native/1.4.8-r0/temp/log.do_compile.8115
> -rw-r--r-- 1 gary develop 51866 Apr 8 14:17 tmp/work/i686-linux/apr-util-native/1.5.2-r0/temp/log.do_compile.19690
> -rw-r--r-- 1 gary develop 27916 Apr 8 14:11 tmp/work/i686-linux/autoconf-native/2.69-r11/temp/log.do_compile.20820
> -rw-r--r-- 1 gary develop 11925 Apr 8 14:11 tmp/work/i686-linux/automake-native/1.14-r0/temp/log.do_compile.22425
> -rw-r--r-- 1 gary develop 28129 Apr 8 14:14 tmp/work/i686-linux/bzip2-native/1.0.6-r5/temp/log.do_compile.12000
> -rw-r--r-- 1 gary develop 85 Apr 8 14:11 tmp/work/i686-linux/cryptodev-linux-native/1.6-r0/temp/log.do_compile.13477
> -rw-r--r-- 1 gary develop 5815 Apr 8 14:14 tmp/work/i686-linux/expat-native/2.1.0-r0/temp/log.do_compile.25198
> -rw-r--r-- 1 gary develop 41125 Apr 8 14:15 tmp/work/i686-linux/file-native/5.16-r0/temp/log.do_compile.28856
> -rw-r--r-- 1 gary develop 92543 Apr 8 14:14 tmp/work/i686-linux/gdbm-native/1.11-r0/temp/log.do_compile.5100
> -rw-r--r-- 1 gary develop 110 Apr 8 14:10 tmp/work/i686-linux/gettext-minimal-native/0.18.3.2-r0/temp/log.do_compile.9603
> -rw-r--r-- 1 gary develop 85 Apr 8 14:10 tmp/work/i686-linux/gnu-config-native/20120814-r0/temp/log.do_compile.8957
> -rw-r--r-- 1 gary develop 787508 Apr 8 14:18 tmp/work/i686-linux/gnutls-native/2.12.23-r8.4/temp/log.do_compile.6985
> -rw-r--r-- 1 gary develop 10398 Apr 8 14:10 tmp/work/i686-linux/libcap-native/2.22-r6/temp/log.do_compile.10990
> -rw-r--r-- 1 gary develop 129792 Apr 8 14:15 tmp/work/i686-linux/libgcrypt-native/1.5.3-r0/temp/log.do_compile.15135
> -rw-r--r-- 1 gary develop 26450 Apr 8 14:14 tmp/work/i686-linux/libgpg-error-native/1.12-r0/temp/log.do_compile.1064
> -rw-r--r-- 1 gary develop 83871 Apr 8 14:14 tmp/work/i686-linux/libtasn1-native/3.4-r0/temp/log.do_compile.23801
> -rw-r--r-- 1 gary develop 34071 Apr 8 14:12 tmp/work/i686-linux/libtool-native/2.4.2-r6.1/temp/log.do_compile.27475
> -rw-r--r-- 1 gary develop 278406 Apr 8 14:21 tmp/work/i686-linux/libxml2-native/2.9.1-r0/temp/log.do_compile.3191
> -rw-r--r-- 1 gary develop 189586 Apr 8 14:12 tmp/work/i686-linux/lzo-native/2.06-r1/temp/log.do_compile.10403
> -rw-r--r-- 1 gary develop 101354 Apr 8 14:11 tmp/work/i686-linux/m4-native/1.4.17-r0/temp/log.do_compile.19559
> -rw-r--r-- 1 gary develop 829027 Apr 8 14:13 tmp/work/i686-linux/ncurses-native/5.9-r15.1/temp/log.do_compile.11001
> -rw-r--r-- 1 gary develop 14753 Apr 8 14:21 tmp/work/i686-linux/neon-native/0.30.0-r0/temp/log.do_compile.15805
> -rw-r--r-- 1 gary develop 504937 Apr 8 14:16 tmp/work/i686-linux/openssl-native/1.0.1e-r15.0/temp/log.do_compile.30233
> -rw-r--r-- 1 gary develop 3170 Apr 8 14:13 tmp/work/i686-linux/pigz-native/2.3.1-r0/temp/log.do_compile.4503
> -rw-r--r-- 1 gary develop 149805 Apr 8 14:13 tmp/work/i686-linux/pkgconfig-native/0.28-r0/temp/log.do_compile.12369
> -rw-r--r-- 1 gary develop 100152 Apr 8 14:19 tmp/work/i686-linux/python-native/2.7.3-r0.1/temp/log.do_compile.32093
> -rw-r--r-- 1 gary develop 1585 Apr 8 14:10 tmp/work/i686-linux/quilt-native/0.61-r0/temp/log.do_compile.8085
> -rw-r--r-- 1 gary develop 34761 Apr 8 14:14 tmp/work/i686-linux/readline-native/6.3-r0/temp/log.do_compile.19880
> -rw-r--r-- 1 gary develop 8633 Apr 8 14:15 tmp/work/i686-linux/sqlite3-native/1_3.8.3.1-r0/temp/log.do_compile.28334
> -rw-r--r-- 1 gary develop 473033 Apr 8 14:23 tmp/work/i686-linux/subversion-native/1.7.10-r0/temp/log.do_compile.19956
> -rw-r--r-- 1 gary develop 911700 Apr 8 14:16 tmp/work/i686-linux/util-linux-native/2.24.1-r0/temp/log.do_compile.2925
> -rw-r--r-- 1 gary develop 475772 Apr 8 14:13 tmp/work/i686-linux/xz-native/5.1.3alpha-r0/temp/log.do_compile.21732
> -rw-r--r-- 1 gary develop 8341 Apr 8 14:13 tmp/work/i686-linux/zlib-native/1.2.8-r0/temp/log.do_compile.614
>
> Why?
>
> Note: this is using the latest Poky/Yocto master, but I've
> seen this behaviour for a long time...
There are svn repositories in there and its therefore building
subversion-native. I believe that has dependencies that look like most
of the above.
Cheers,
Richard
prev parent reply other threads:[~2014-04-08 14:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-08 13:28 fetchall strangeness Gary Thomas
2014-04-08 14:11 ` Richard Purdie [this message]
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=1396966294.24597.106.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=gary@mlbassoc.com \
--cc=yocto@yoctoproject.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.