Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-core@lists.openembedded.org
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: State of bitbake world, Failed tasks 2017-03-01
Date: Thu, 2 Mar 2017 09:46:23 +0100	[thread overview]
Message-ID: <o98m4o$7ao$1@blaine.gmane.org> (raw)
In-Reply-To: <CALbNGRTO37A-tbDj93nuNi0vu6h3fJg7Wg6P6N8asz45e8H9bg@mail.gmail.com>

Op 02-03-17 om 00:14 schreef Andreas Müller:
> On Wed, Mar 1, 2017 at 8:55 PM, Martin Jansa <martin.jansa@gmail.com> wrote:
>>     * openembedded-core/meta/recipes-extended/parted/parted_3.2.bb:do_compile_ptest_base
> Before Martin blacklists gparted for dependency :)
> 
> 1. Autobuilder error log says:
> 
> | ../libparted/fs/.libs/libparted-fs-resize.so: error: undefined
> reference to 'uuid_generate'
> | collect2: error: ld returned 1 exit status
> | Makefile:1422: recipe for target 'fs-resize' failed
> | make: *** [fs-resize] Error 1
> | make: Leaving directory
> '/home/jenkins/oe/world/shr-core/tmp-glibc/work/armv5te-oe-linux-gnueabi/parted/3.2-r1/build/tests'
> | ERROR: Function failed: do_compile_ptest_base (log file is located
> at /home/jenkins/oe/world/shr-core/tmp-glibc/work/armv5te-oe-linux-gnueabi/parted/3.2-r1/temp/log.do_compile_ptest_base.7114)
> 
> 2. grepping in gparted's source
> [superandy@very-old-builder parted-3.2]$ grep -r uuid_generate
> configure.ac:AC_CHECK_LIB([uuid], [uuid_generate], [UUID_LIBS="-luuid"],
> <...>
> 
> I think adding ossp-uuid to DEPENDS will do. 

Util-linux is the preferred provider for libuuid (it moved from e2fsprogs to
util-linux a few years ago).

regards,

Koen




  reply	other threads:[~2017-03-02  8:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-01 19:55 State of bitbake world, Failed tasks 2017-03-01 Martin Jansa
2017-03-01 23:14 ` Andreas Müller
2017-03-02  8:46   ` Koen Kooi [this message]
2017-03-02 13:47     ` Andreas Müller

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='o98m4o$7ao$1@blaine.gmane.org' \
    --to=koen@dominion.thruhere.net \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=openembedded-devel@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox