Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Trevor Woerner <twoerner@gmail.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] util-linux: 2.28.1 -> 2.29
Date: Mon, 19 Dec 2016 16:42:58 -0500	[thread overview]
Message-ID: <20161219214258.GA16333@openSUSE-i7.site> (raw)
In-Reply-To: <CAJTo0LYV2qMTBVpm8ASDb7BdwwezWfysAn6fJbM7Xwh6FXCcyg@mail.gmail.com>

On Mon 2016-12-19 @ 08:31:25 PM, Burton, Ross wrote:
> On 19 December 2016 at 15:23, Trevor Woerner <twoerner@gmail.com> wrote:
> 
> > Is anyone else seeing build failures as a result of this commit?
> >
> 
> Can you reproduce this on demand?

Yes. Last night's raspi2 and minnow/turbot builds failed, and trying with qemu
(x86-64 and x86) all failed.

A fresh build in a new directory fails readily:

$ git clone git://git.openembedded.org/openembedded-core.git
(e82a7f879419828b42b5cc71e6229c8235090f21)
$ git clone git://git.openembedded.org/bitbake.git
(50633012a64a3b5f0662145e29ff426374fb7683)
$ . openembedded-core/oe-init-build-env build bitbake
$ bitbake util-linux-native


Build Configuration:
BB_VERSION        = "1.32.0"
BUILD_SYS         = "x86_64-linux"
NATIVELSBSTRING   = "opensuse-42.2"
TARGET_SYS        = "i586-oe-linux"
MACHINE           = "qemux86"
DISTRO            = "nodistro"
DISTRO_VERSION    = "nodistro.0"
TUNE_FEATURES     = "m32 i586"
TARGET_FPU        = ""
meta              = "master:e82a7f879419828b42b5cc71e6229c8235090f21"

*BOOM!* ;-)

| disk-utils/cfdisk-cfdisk.o:cfdisk.c:(.text.startup+0x8fd): more undefined references to `_nc_stdscr' follow
| collect2: error: ld returned 1 exit status
| Makefile:5737: recipe for target 'cfdisk' failed
| make[2]: *** [cfdisk] Error 1
| make[2]: Leaving directory '/z/qemu/build/tmp-glibc/work/x86_64-linux/util-linux-native/2.29-r0/build'
| Makefile:11450: recipe for target 'all-recursive' failed
| make[1]: *** [all-recursive] Error 1
| make[1]: Leaving directory '/z/qemu/build/tmp-glibc/work/x86_64-linux/util-linux-native/2.29-r0/build'
| Makefile:4781: recipe for target 'all' failed
| make: *** [all] Error 2
| ERROR: Function failed: do_compile (log file is located at /z/qemu/build/tmp-glibc/work/x86_64-linux/util-linux-native/2.29-r0/temp/log.do_compile.28460)
ERROR: Task (virtual:native:/z/qemu/openembedded-core/meta/recipes-core/util-linux/util-linux_2.29.bb:do_compile) failed with exit code '1'


  reply	other threads:[~2016-12-19 21:42 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-13  3:30 [PATCH] util-linux: 2.28.1 -> 2.29 Zheng Ruoqin
2016-12-19 15:23 ` Trevor Woerner
2016-12-19 20:31   ` Burton, Ross
2016-12-19 21:42     ` Trevor Woerner [this message]
2016-12-19 21:47       ` Burton, Ross
2016-12-19 21:53         ` Burton, Ross
2016-12-19 22:01           ` Trevor Woerner
2016-12-19 22:12             ` Khem Raj
2016-12-20 14:36               ` Burton, Ross
2016-12-20 14:41               ` Burton, Ross
2016-12-20 14:55                 ` Trevor Woerner
2016-12-20 15:00                   ` Burton, Ross
2016-12-20 15:05                     ` Burton, Ross
2016-12-20 15:14                       ` Trevor Woerner
2016-12-20 15:16                         ` Burton, Ross
2016-12-20 15:22                           ` Trevor Woerner
2016-12-20 15:17                         ` Trevor Woerner

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=20161219214258.GA16333@openSUSE-i7.site \
    --to=twoerner@gmail.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