From: Saul Wold <sgw@linux.intel.com>
To: Frans Meulenbroeks <fransmeulenbroeks@gmail.com>
Cc: yocto@yoctoproject.org
Subject: Re: yocto 1.2 first experiences
Date: Wed, 02 May 2012 10:17:57 -0700 [thread overview]
Message-ID: <4FA16C45.6090009@linux.intel.com> (raw)
In-Reply-To: <CACW_hTaEwdB1uiYRkboek=24bm4FNoRwSVEyboKG-FnB7ndQgg@mail.gmail.com>
On 05/02/2012 12:28 AM, Frans Meulenbroeks wrote:
> Dear all,
>
> I have build core-image-minimal with yocto 1.2
> Worked quite nice, but it did give 10 warnings
>
> Four of these were non-fetchers:
> WARNING: Failed to fetch URL
> http://kernel.org/pub/linux/kernel/people/jsipek/guilt/guilt-0.33.tar.gz
> WARNING: Failed to fetch URL
> http://kernel.org/pub/linux/utils/kernel/module-init-tools/module-init-tools-3.16.tar.bz2
> WARNING: Failed to fetch URL
> http://kernel.org/pub/linux/utils/usb/usbutils/usbutils-0.91.tar.gz
> WARNING: Failed to fetch URL
> http://kernel.org/pub/linux/utils/kernel/hotplug/udev-164.tar.gz
>
Thanks for this info, it's a good thing that we have the Mirror, these
are all kernel.org files that do not seem to have been fully restored
since they had their issues.
The below QA issues are known about and will be addressed in 1.3, most
of these have to do with scripts and libraries looking into /usr from /
Thanks for the info.
Sau!
> The other 6 were QA related:
> bash:
> WARNING: QA Issue: bash: Found a reference to /usr/ in
> /home/frans/poky-denzil-7.0-build/tmp/work/i586-poky-linux/bash-4.2-r2/packages-split/bash/bin/bashbug
> WARNING: QA Issue: Shell scripts in base_bindir and base_sbindir
> should not reference anything in exec_prefix
>
> and 4 in sysvinit:
>
> WARNING: QA Issue: udev:
> /home/frans/poky-denzil-7.0-build/tmp/work/i586-poky-linux/udev-164-r13/packages-split/libgudev/lib/libgudev-1.0.so.0.0.1
> links to something under exec_prefix
> WARNING: QA Issue: ldd reports: libudev.so.0 =>
> /home/frans/poky-denzil-7.0-build/tmp/sysroots/qemux86/lib/libudev.so.0
> (0xdead1000)
> libgobject-2.0.so.0 =>
> /home/frans/poky-denzil-7.0-build/tmp/sysroots/qemux86/usr/lib/libgobject-2.0.so.0
> (0xdead2000)
> libffi.so.5 =>
> /home/frans/poky-denzil-7.0-build/tmp/sysroots/qemux86/usr/lib/libffi.so.5
> (0xdead3000)
> libgthread-2.0.so.0 =>
> /home/frans/poky-denzil-7.0-build/tmp/sysroots/qemux86/usr/lib/libgthread-2.0.so.0
> (0xdead4000)
> libpthread.so.0 =>
> /home/frans/poky-denzil-7.0-build/tmp/sysroots/qemux86/lib/libpthread.so.0
> (0xdead5000)
> libglib-2.0.so.0 =>
> /home/frans/poky-denzil-7.0-build/tmp/sysroots/qemux86/usr/lib/libglib-2.0.so.0
> (0xdead6000)
> librt.so.1 =>
> /home/frans/poky-denzil-7.0-build/tmp/sysroots/qemux86/lib/librt.so.1
> (0xdead7000)
> libc.so.6 =>
> /home/frans/poky-denzil-7.0-build/tmp/sysroots/qemux86/lib/libc.so.6
> (0xdead8000)
> /lib/ld-linux.so.2 =>
> /home/frans/poky-denzil-7.0-build/tmp/sysroots/qemux86/lib/ld-linux.so.2
> (0xdead9000)
>
> WARNING: QA Issue: udev:
> /home/frans/poky-denzil-7.0-build/tmp/work/i586-poky-linux/udev-164-r13/packages-split/udev-acl/lib/udev/udev-acl
> links to something under exec_prefix
> WARNING: QA Issue: ldd reports: libacl.so.1 =>
> /home/frans/poky-denzil-7.0-build/tmp/sysroots/qemux86/lib/libacl.so.1
> (0xdead1000)
> libpthread.so.0 =>
> /home/frans/poky-denzil-7.0-build/tmp/sysroots/qemux86/lib/libpthread.so.0
> (0xdead2000)
> libglib-2.0.so.0 =>
> /home/frans/poky-denzil-7.0-build/tmp/sysroots/qemux86/usr/lib/libglib-2.0.so.0
> (0xdead3000)
> libc.so.6 =>
> /home/frans/poky-denzil-7.0-build/tmp/sysroots/qemux86/lib/libc.so.6
> (0xdead4000)
> libattr.so.1 =>
> /home/frans/poky-denzil-7.0-build/tmp/sysroots/qemux86/lib/libattr.so.1
> (0xdead5000)
> /lib/ld-linux.so.2 =>
> /home/frans/poky-denzil-7.0-build/tmp/sysroots/qemux86/lib/ld-linux.so.2
> (0xdead6000)
> librt.so.1 =>
> /home/frans/poky-denzil-7.0-build/tmp/sysroots/qemux86/lib/librt.so.1
> (0xdead7000)
>
> Not too sure if these are really harmful, and I guess they are already
> known, but decided to report them anyway (better safe than sorry :-)
> ).
>
> Best regards, Frans
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
prev parent reply other threads:[~2012-05-02 17:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-02 7:28 yocto 1.2 first experiences Frans Meulenbroeks
2012-05-02 17:17 ` Saul Wold [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=4FA16C45.6090009@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=fransmeulenbroeks@gmail.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.