public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Andreas Reichel <andreas.reichel.ext@siemens.com>
To: isar-users@googlegroups.com
Cc: christian.storm@siemens.com, jan.kiszka@siemens.com
Subject: Re: interesting problem with custom kernel
Date: Mon, 21 Jan 2019 10:58:08 +0100	[thread overview]
Message-ID: <20190121095808.GB30529@iiotirae> (raw)
In-Reply-To: <20190121094225.GA30529@iiotirae>

On Mon, Jan 21, 2019 at 10:42:27AM +0100, [ext] Andreas Reichel wrote:
> Hi,
> 
> I created a recipe for a custom kernel exactly as in the example
> and get
> 
> ----
> Currently  1 running tasks (28 of 36)  75% |###################################################################                       |↲
>   2 0: linux-qoriq-4.14-LSDK-18.09-LS1043-r0 do_install_builddeps - 239830s (pid 16877)↲
> ----
Okay there were several problems with the recipe, after cleaning /tmp I
indeed got errors. Never mind.

Andreas

> 
> where 240 thousand seconds seem a little long for my taste.
> 
> 
> local.conf:
> MACHINE = "qemuarm64"
> DISTRO_ARCH = "arm64"
> KERNEL_NAME = "qoriq"
> 
> Recipe is:
> 
> recipes-kernel/linux/linux-qoriq_4.14.bb
> ----
> require recipes-kernel/linux/linux-custom.inc
> 
> SRC_URI += " \
> 	git://source.codeaurora.org/external/qoriq/qoriq-components/linux; \
> 	file://ls1043_defconfig"
> 
> SRCREV = "f2f35bbfc16b384f447a30dd0b240637331fd132"
> PV = "4.14-LSDK-18.09-LS1043"
> 
> KERNEL_DEFCONFIG_qemuarm64 = "ls1043_defconfig"
> ----
> 
> Just noted it has not built over the weekend but no error message.
> 
> kind regards
> Andreas
> 
> -- 
> Andreas Reichel
> Dipl.-Phys. (Univ.)
> Software Consultant
> 
> Andreas.Reichel@tngtech.com, +49-174-3180074
> TNG Technology Consulting GmbH, Betastr. 13a, 85774 Unterfoehring
> Geschaeftsfuehrer: Henrik Klagges, Dr. Robert Dahlke, Gerhard Mueller
> Sitz: Unterfoehring * Amtsgericht Muenchen * HRB 135082
> 
> -- 
> You received this message because you are subscribed to the Google Groups "isar-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
> To post to this group, send email to isar-users@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/isar-users/20190121094225.GA30529%40iiotirae.
> For more options, visit https://groups.google.com/d/optout.

-- 
Andreas Reichel
Dipl.-Phys. (Univ.)
Software Consultant

Andreas.Reichel@tngtech.com, +49-174-3180074
TNG Technology Consulting GmbH, Betastr. 13a, 85774 Unterfoehring
Geschaeftsfuehrer: Henrik Klagges, Dr. Robert Dahlke, Gerhard Mueller
Sitz: Unterfoehring * Amtsgericht Muenchen * HRB 135082


      reply	other threads:[~2019-01-21  9:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-21  9:42 Andreas Reichel
2019-01-21  9:58 ` Andreas Reichel [this message]

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=20190121095808.GB30529@iiotirae \
    --to=andreas.reichel.ext@siemens.com \
    --cc=christian.storm@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=jan.kiszka@siemens.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