From: "Andy Pont" <andy.pont@sdcsystems.com>
To: "'Burton, Ross'" <ross.burton@intel.com>,
"'Trevor Woerner'" <twoerner@gmail.com>
Cc: yocto@yoctoproject.org
Subject: Re: Dumping sysvinit
Date: Wed, 16 Sep 2015 10:24:59 +0100 [thread overview]
Message-ID: <008c01d0f061$904fd7b0$b0ef8710$@pont@sdcsystems.com> (raw)
In-Reply-To: <CAJTo0LaXx_DR7j0og26UK7mvmmR6fPk6ZnGiyVSOeGfw7JYQ7g@mail.gmail.com>
Hello all,
> > I think if you remove/comment-out the last of those 3 lines or install
> > your host's SDL-devel package you'll solve this issue (?)
> >
> Yes, that's right. Either disable the graphical qemu support, or install
> the host's sdl-devel package so it can build.
On my CentOS 6.7 host system running the package manager reports that SDL-devel is already installed:
# yum install SDL-devel
Package SDL-devel-1.2.14-6.el6.x86_64 already installed and latest version
Nothing to do
This is probably something to do with the fact that in order to get Fido to build I have to use the devtoolset-2.1 package to get a recent gcc version and it probably isn't aware of the standard SDL-devel libraries.
Commenting out just the last line of the 3 QEMU/SDL related lines throws out a couple of errors whereas removing all of them gives me a build.
Now to figure out why the tar.gz file for the root file system has grown from just under 3MiB to almost 15MiB!
Thanks for all the help and advice.
Andy.
next prev parent reply other threads:[~2015-09-16 9:25 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
[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 [this message]
[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='008c01d0f061$904fd7b0$b0ef8710$@pont@sdcsystems.com' \
--to=andy.pont@sdcsystems.com \
--cc=ross.burton@intel.com \
--cc=twoerner@gmail.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.