Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "David Nyström" <david.nystrom@enea.com>
To: Laurentiu Palcu <laurentiu.palcu@intel.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v2 00/50] Rootfs/image generation refactoring (cover letter only)
Date: Wed, 5 Feb 2014 13:09:05 +0100	[thread overview]
Message-ID: <52F229E1.3040204@enea.com> (raw)
In-Reply-To: <CAAKB1h3PL6oyL0VG70SVXSMEROxrwX0sJDc82WO+0e=QvSKiaw@mail.gmail.com>

On 2014-02-05 11:58, David Nystrom wrote:
> On Wed, Feb 5, 2014 at 11:07 AM, Laurentiu Palcu
> <laurentiu.palcu@intel.com>wrote:
>
>> V2:
>>   * fix building from feeds for opkg;
>>   * rebase;
>>
>
> | NOTE: ###### Generate rootfs #######
> | NOTE: Installing the following packages: run-postinsts
> packagegroup-core-boot
> | sed: -e expression #1, char 41: unterminated address regex
> | sed: -e expression #1, char 42: unterminated address regex
> | sed: -e expression #1, char 41: unterminated address regex
> | sed: -e expression #1, char 42: unterminated address regex
>
> [david] Why are these seds failing ?, I've seen this in master aswell
> though.

After testing with the yocto 1.5 repo, the postinstall sed failures 
where not seen anymore. Added Bug:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=5789

>
> | NOTE: Installing complementary packages ...
> | NOTE: Installing the following packages:
> | /media/sdb5/bld/tmp/sysroots/x86_64-linux/usr/bin/opkg-cl: the
> ``install'' command requires at least one argument
> | NOTE: Unable to install packages. Command
> /media/sdb5/bld/tmp/sysroots/x86_64-linux/usr/bin/opkg-cl -f
> /media/sdb5/bld/tmp/work/qemuppc-poky-linux/core-image-minimal/1.0-r0/opkg.conf
> -o
> /media/sdb5/bld/tmp/work/qemuppc-poky-linux/core-image-minimal/1.0-r0/rootfs
> --force_postinstall --prefer-arch-to-version   install  returned 1
> | NOTE: Running intercept scripts:
> | NOTE: Executing write_package_manifest ...
> | DEBUG: Executing python function write_package_manifest
> | NOTE: Building from feeds activated!
> | NOTE: Add all feed with URL
> file:///media/sdb5/oel/build/tmp/deploy/ipk/all
> | NOTE: Add qemuppc feed with URL
> file:///media/sdb5/oel/build/tmp/deploy/ipk/qemuppc
> | NOTE: Add ppc7400 feed with URL
> file:///media/sdb5/oel/build/tmp/deploy/ipk/ppc7400
> | DEBUG: Python function write_package_manifest finished
> | NOTE: Executing license_create_manifest ...
> | DEBUG: Executing shell function license_create_manifest
> | ls: cannot access
> /media/sdb5/bld/tmp/sysroots/qemuppc/pkgdata/runtime-reverse/base-files: No
> such file or directory
> | readlink: missing operand
> | Try 'readlink --help' for more information.
> | basename: missing operand
> | Try 'basename --help' for more information.
> | WARNING: exit code 1 from a shell command.
> | DEBUG: Python function do_rootfs finished
> | ERROR: Function failed: license_create_manifest (log file is located at
> /media/sdb5/bld/tmp/work/qemuppc-poky-linux/core-image-minimal/1.0-r0/temp/log.do_rootfs.29007)
> ERROR: Task 6 (/media/sdb5/poky-contrib/meta/recipes-core/images/
> core-image-minimal.bb, do_rootfs) failed with exit code '1'
> NOTE: Tasks Summary: Attempted 504 tasks of which 503 didn't need to be
> rerun and 1 failed.
>
> Summary: 1 task failed:
>    /media/sdb5/poky-contrib/meta/recipes-core/images/core-image-minimal.bb,
> do_rootfs
> Summary: There was 1 ERROR message shown, returning a non-zero exit code
>
> Br,
> David
>

FYI: to easily recreate this testcase:

-Clean build env-

$ grep -C 6 -r FEEDS conf/local.conf
# Default to setting automatically based on cpu count
PARALLEL_MAKE ?= "-j ${@oe.utils.cpu_count()}"
#
# For a quad-core machine, BB_NUMBER_THREADS = "4", PARALLEL_MAKE = "-j 
4" would
# be appropriate for example.

BUILD_IMAGES_FROM_FEEDS="1"
IPK_FEED_URIS = " \
 
all##http://downloads.yoctoproject.org/releases/yocto/yocto-1.5/ipk/all \
	 
${MACHINE}##http://downloads.yoctoproject.org/releases/yocto/yocto-1.5/ipk/${MACHINE} 
\
 
ppc7400##http://downloads.yoctoproject.org/releases/yocto/yocto-1.5/ipk/ppc7400 
\
	   "

PACKAGE_CLASSES="ipk" MACHINE="qemuppc" bitbake -c rootfs core-image-minimal

Br,
David



  reply	other threads:[~2014-02-05 12:09 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-03 11:38 [PATCH 00/49] Rootfs/image generation refactoring (cover letter only) Laurentiu Palcu
2014-02-03 11:54 ` Laurentiu Palcu
2014-02-03 14:32 ` David Nyström
2014-02-03 16:47   ` Laurentiu Palcu
2014-02-04 14:08     ` David Nyström
2014-02-04 14:49       ` David Nyström
2014-02-04 15:34         ` Laurentiu Palcu
2014-02-04 15:40           ` David Nyström
2014-02-05 10:07 ` [PATCH v2 00/50] " Laurentiu Palcu
2014-02-05 10:58   ` David Nystrom
2014-02-05 12:09     ` David Nyström [this message]
2014-02-05 14:43       ` Laurentiu Palcu
2014-02-05 18:00         ` David Nystrom
2014-02-05 15:05 ` [PATCH v3 00/51] " Laurentiu Palcu
2014-02-10  7:53   ` [PATCH v4 00/52] " Laurentiu Palcu
2014-02-10 12:15 ` [PATCH v5 00/53] " Laurentiu Palcu
2014-02-11  8:42   ` David Nyström
2014-02-11  8:50     ` Laurentiu Palcu
2014-02-11  8:56       ` David Nyström
2014-02-11  9:36         ` David Nyström
2014-02-11 14:33   ` David Nyström
2014-02-11 14:50     ` David Nyström

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=52F229E1.3040204@enea.com \
    --to=david.nystrom@enea.com \
    --cc=laurentiu.palcu@intel.com \
    --cc=openembedded-core@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