Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/3 v2] Upgrade RPM 5 to 5.4.16 (CVS HEAD)
Date: Mon, 29 Feb 2016 09:36:07 -0600	[thread overview]
Message-ID: <56D46567.7070409@windriver.com> (raw)
In-Reply-To: <56D23094.20207@windriver.com>

Status update.

I was able to reproduce the issue and I have added a configure check to see if
the compiler supports the atomic operations or not.  RPM will then configure
itself to use them if available.

I also disabled the blake tests which were causing issues in some parallel builds.

Finally I found an issue where a specific dependency (internal to the package)
was not being properly determined by RPM.  I'm currently investigating this.

--Mark

On 2/27/16 5:26 PM, Mark Hatle wrote:
> On 2/27/16 4:47 PM, Burton, Ross wrote:
>>
>> On 27 February 2016 at 04:26, Mark Hatle <mark.hatle@windriver.com
>> <mailto:mark.hatle@windriver.com>> wrote:
>>
>>     I am not getting this error on qemux86.
>>
>>     My build configuration:
>>
>>     BB_VERSION        = "1.29.0"
>>     BUILD_SYS         = "x86_64-linux"
>>     NATIVELSBSTRING   = "Fedora-23"
>>     TARGET_SYS        = "i586-oe-linux"
>>     MACHINE           = "qemux86"
>>     DISTRO            = "nodistro"
>>     DISTRO_VERSION    = "nodistro.0"
>>     TUNE_FEATURES     = "m32 i586"
>>     TARGET_FPU        = ""
>>     meta              = "mhatle/rpm-5.4.16:004efb3aaa973dba030847c1c8218238f0cc68c5"
>>
>>     The local.conf is the stock one with buildhistory and package_rpm enabled.
>>
>>     Which compiler do you have enabled?  I'm building with the default 5.3.0
>>     compiler.
>>
>>     Since I'm not reproducing the problem, I'd like to know what the difference in
>>     configurations is.
>>
>>
>> This was on the autobuilder and happened twice in rpm-native:
>>
>> http://errors.yoctoproject.org/Errors/Details/38006/ (Debian 8.3)
>> http://errors.yoctoproject.org/Errors/Details/38000/ (Ubuntu 14.04)
>>
>> I guess the -native bit is important there.
> 
> Ok.. so that is different.  It means the host compiler is too old and doesn't
> support atomic transactions.
> 
>> Also, another failure happened more globally:
>>
>> gcc: error: tblake2bp.o: No such file or directory
>>
>> Several times in rpm for target:
>> http://errors.yoctoproject.org/Errors/Details/37991/
>> http://errors.yoctoproject.org/Errors/Details/38001/
>> http://errors.yoctoproject.org/Errors/Details/38007/
>> http://errors.yoctoproject.org/Errors/Details/38004/
> 
> Ok. I'll investigate this one as well.  Likely this is a parallel build issue,
> hopefully I can spot the fault.
> 
> --Mark
> 
>> And once in rpm-native:
>> http://errors.yoctoproject.org/Errors/Details/37995/
>>
>> Ross
> 



  reply	other threads:[~2016-02-29 15:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-26  3:28 [PATCH 0/3 v2] Upgrade RPM 5 to 5.4.16 (CVS HEAD) Mark Hatle
2016-02-26  3:28 ` [PATCH 1/3 v2] rpm: Uprev to rpm-5.4.16 (pre) and rpm-5.4+cvs to current CVS head Mark Hatle
     [not found]   ` <39dcc8978920aeaf0eeb206b7292f32af4b775f7.1456456877.git.mark.hatle@wi ndriver.com>
2016-02-26 15:01     ` alexander.kanavin
2016-02-26 14:26       ` Mark Hatle
2016-02-29 13:16         ` Alexander Kanavin
2016-02-29 15:18           ` Mark Hatle
2016-02-26  3:28 ` [PATCH 2/3 v2] rpm: Enable specific crypto and digest settings via variables Mark Hatle
2016-02-26  3:28 ` [PATCH 3/3 v2] rpm: A number of the patches have been submitted upstream Mark Hatle
2016-02-26 23:11 ` [PATCH 0/3 v2] Upgrade RPM 5 to 5.4.16 (CVS HEAD) Burton, Ross
2016-02-27  4:26   ` Mark Hatle
2016-02-27 22:47     ` Burton, Ross
2016-02-27 23:26       ` Mark Hatle
2016-02-29 15:36         ` Mark Hatle [this message]
2016-03-01  1:33           ` Mark Hatle

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=56D46567.7070409@windriver.com \
    --to=mark.hatle@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.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