All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Andy Pont" <andy.pont@sdcsystems.com>
To: "'Mark Hatle'" <mark.hatle@windriver.com>, <yocto@yoctoproject.org>
Subject: Re: Dumping sysvinit
Date: Tue, 15 Sep 2015 17:03:40 +0100	[thread overview]
Message-ID: <000f01d0efd0$17ac53b0$4704fb10$@pont@sdcsystems.com> (raw)
In-Reply-To: <55F822C0.8030404@windriver.com>

Mark wrote...

> > Bit of a newbie question (probably) but what is the easiest way to dump
> > sysvinit and use Busybox init in a core-image-minimal image?
> 
> It has been a while since I've done this.  But unless things have changed
> dramatically.  You will need to define your own custom image.

On the basis that sounded like more hard work than I have time for I thought
I would try switching to systemd.  Following the instructions in the dev
manual [1].

If I add the extra variables to build/conf/local.conf then with the machine
type set to genericx86 I get this build error:

ERROR: Function failed: do_configure (log file is located at
XXXXX/build/tmp/work/x86_64-linux/qemu-native/2.2.0-r1/temp/log.do_configure
.1926)
ERROR: Logfile of failure stored in:
XXXXX/build/tmp/work/x86_64-linux/qemu-native/2.2.0-r1/temp/log.do_configure
.1926
Log data follows:
| DEBUG: Executing python function sysroot_cleansstate
| DEBUG: Python function sysroot_cleansstate finished
| DEBUG: Executing shell function autotools_preconfigure
| DEBUG: Shell function autotools_preconfigure finished
| DEBUG: Executing python function autotools_copy_aclocals
| DEBUG: Python function autotools_copy_aclocals finished
| DEBUG: Executing shell function do_configure
| 
| ERROR: User requested feature sdl
|        configure was not able to find it.
|        Install SDL devel

I'm guessing that this is me being dim and that build/conf/local.conf isn't
what the documentation refers to as "your distribution configuration file".
Can someone point me in the right direction?

Thanks,

Andy.

[1]
http://www.yoctoproject.org/docs/1.8/dev-manual/dev-manual.html#selecting-an
-initialization-manager



  reply	other threads:[~2015-09-15 16:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-15 11:16 Dumping sysvinit Andy Pont
2015-09-15 13:53 ` Mark Hatle
2015-09-15 16:03   ` Andy Pont [this message]
     [not found]   ` <55f84188.e17c420a.cd394.2235SMTPIN_ADDED_BROKEN@mx.google.com>
2015-09-15 16:27     ` Trevor Woerner
2015-09-16  7:44       ` Burton, Ross
2015-09-16  9:24         ` Andy Pont
     [not found]         ` <55f9358a.44f2440a.38b16.7e0cSMTPIN_ADDED_BROKEN@mx.google.com>
2015-09-16 10:02           ` Burton, Ross
2015-09-16 14:13             ` Andy Pont
2015-09-17  7:16               ` Mike Looijmans
2015-09-21 10:48                 ` Andy Pont
2015-09-21 11:48                   ` Mike Looijmans

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='000f01d0efd0$17ac53b0$4704fb10$@pont@sdcsystems.com' \
    --to=andy.pont@sdcsystems.com \
    --cc=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.