From: Mark Hatle <mark.hatle@windriver.com>
To: yocto@yoctoproject.org
Subject: Re: Recent build issues.
Date: Thu, 23 Dec 2010 18:53:06 -0600 [thread overview]
Message-ID: <4D13EEF2.8080605@windriver.com> (raw)
In-Reply-To: <1293150141.17519.560.camel@rex>
On 12/23/10 6:22 PM, Richard Purdie wrote:
> On Thu, 2010-12-23 at 14:08 -0800, Flanagan, Elizabeth wrote:
...
>> mips seems to have run poky-image-minimal ok, but with Bug #611, I
>> can't be sure that is the case and I doubt it's actually the case. My
>> inclination is that there is an issue with arm and mips builds that
>> should be looked at.
>
> Also, qemux86 was broken until a fix I pushed a few minutes ago (kernel
> was missing IDE support and wouldn't boot in qemu).
>
> It looks like the new version of opkg we've upgraded to fixing certain
> meta-toolchain corruption issues has some other new characteristics such
> as refusing to install overlapping files. This is good but its exposed
> bugs (and why isn't rpm showing this?).
There are two cases in which RPM allows "overlapping" files.
The first is that the files are identical. I.e. same md5sum/same sha1. There
are reasons for overlapping files in most distros, so they are handled
gracefully. (To me not supporting identical files in multiple packages is a
defect.. because of the second reason...)
The second is two files of different ELF types. This can occur when you are on
a multilib system. You have duplicate packages (one 32-bit, one 64-bit) to be
installed at the same time. They may contain duplicate files, as well as endian
specific files (libraries and binaries). In the case of overlapping binaries
RPM will check and use a configured policy to determine which one is installed
and which is ignored. (On IA32 systems, generally 64-bit is installed, and
32-bit is ignored.) Goal is to allow for both 64-bit and 32-bit libraries, all
common data files and the "preferred" binary format to be installed onto a system.
> There is currently an issue with that when building meta-toolchain and
> poky-image-lsb that I know of. Patches to fix these bugs welcome (and
> bugs need filing).
>
...
next prev parent reply other threads:[~2010-12-24 0:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-23 22:08 Recent build issues Flanagan, Elizabeth
2010-12-24 0:22 ` Richard Purdie
2010-12-24 0:53 ` Mark Hatle [this message]
2010-12-24 1:31 ` Xu, Jiajun
2011-01-03 20:38 ` Bruce Ashfield
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=4D13EEF2.8080605@windriver.com \
--to=mark.hatle@windriver.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.