All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: <yocto@yoctoproject.org>
Subject: Re: Can't build util-linux
Date: Thu, 5 Jan 2012 10:35:38 -0600	[thread overview]
Message-ID: <4F05D15A.30504@windriver.com> (raw)
In-Reply-To: <4F059C60.8020507@mlbassoc.com>

I'm getting the same error.  There is a workaround:

Add the following to your local.conf

WARN_QA = "ldflags useless-rpaths rpaths"

A new QA check went in, and it appears to be missing part of the merge.

(WARN_QA is normally defined as:
WARN_QA ?= "ldflags useless-rpaths rpaths unsafe-references-in-binaries 
unsafe-references-in-scripts")

On 1/5/12 6:49 AM, Gary Thomas wrote:
> Using a freshly updated master
>
> OE Build Configuration:
> BB_VERSION        = "1.15.0"
> TARGET_ARCH       = "arm"
> TARGET_OS         = "linux-gnueabi"
> MACHINE           = "beagleboard"
> DISTRO            = "poky"
> DISTRO_VERSION    = "1.1+snapshot-20120105"
> TUNE_FEATURES     = "armv7a vfp neon cortexa8"
> TARGET_FPU        = "vfp-neon"
> meta
> meta-yocto        = "master:5aabdbaff7b8be319a86c5e33cc2eb8c2e4aa2ef"
>
> | NOTE: DO PACKAGE QA
> | NOTE: Checking Package: util-linux-agetty
> | ERROR: Error executing a python function in /tmp/poky-multi/meta/recipes-core/util-linux/util-linux_2.20.1.bb:
> | AttributeError: 'module' object has no attribute 'check_output'
> |
> | ERROR: The stack trace of python calls that resulted in this exception/failure was:
> | ERROR:   File "do_package_qa", line 68, in<module>
> | ERROR:
> | ERROR:   File "do_package_qa", line 57, in do_package_qa
> | ERROR:
> | ERROR:   File "insane.bbclass", line 19, in package_qa_walk
> | ERROR:
> | ERROR:   File "insane.bbclass", line 17, in package_qa_check_unsafe_references_in_binaries
> | ERROR:
> | ERROR: The code that was being executed was:
> | ERROR:      0064:        bb.fatal("QA run found fatal errors. Please consider fixing them.")
> | ERROR:      0065:    bb.note("DONE with PACKAGE QA")
> | ERROR:      0066:
> | ERROR:      0067:
> | ERROR:  *** 0068:do_package_qa(d)
> | ERROR:      0069:
> | ERROR: (file: 'do_package_qa', lineno: 68, function:<module>)
> | ERROR:      0053:                errorchecks.append(g[testmatrix[e]])
> | ERROR:      0054:
> | ERROR:      0055:        bb.note("Checking Package: %s" % package)
> | ERROR:      0056:        path = "%s/%s" % (pkgdest, package)
> | ERROR:  *** 0057:        if not package_qa_walk(path, warnchecks, errorchecks, skip, package, d):
> | ERROR:      0058:            walk_sane  = False
> | ERROR:      0059:        if not package_qa_check_rdepends(package, pkgdest, skip, d):
> | ERROR:      0060:            rdepends_sane = False
> | ERROR:      0061:
> | ERROR: (file: 'do_package_qa', lineno: 57, function: do_package_qa)
> | ERROR: Function 'do_package_qa' failed
> NOTE: package util-linux-2.20.1-r1: task do_package: Failed
>
> Ideas?
>



  reply	other threads:[~2012-01-05 16:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-05 12:49 Can't build util-linux Gary Thomas
2012-01-05 16:35 ` Mark Hatle [this message]
2012-01-05 16:54 ` Scott Garman
2012-01-05 17:52   ` Chris Larson

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=4F05D15A.30504@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.