All of lore.kernel.org
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@linux.intel.com>
To: openembedded-core@lists.openembedded.org,
	Saul Wold <sgw@linux.intel.com>
Cc: Darren Hart <dvhart@linux.intel.com>,
	Ross Burton <ross.burton@intel.com>
Subject: [PATCH 0/1] syslinux: Avoid using linux.ext2_fs.h if possible
Date: Wed,  4 Apr 2012 15:30:00 -0700	[thread overview]
Message-ID: <cover.1333578393.git.dvhart@linux.intel.com> (raw)

The following patch is intended as a stop gap to address the compilation
failure for the Yocto 1.2 release. This patch is a backport from syslinux
4.6-pre3. After the Yocto Project 1.2 release and the syslinux 4.6 (or later)
release, the syslinux recipe will be updated and the patch will be dropped.

Tested building atom-pc core-image-minimal live images on Fedora 16 amd64
with the linux/ext2_fs.h file renamed.

The following changes since commit 3e4562500956550dbae5467a5fe9289f1d32f775:

  self-hosted-image: Increase space for build and allow builder user sudo access (2012-04-04 17:17:11 +0100)

are available in the git repository at:
  git://git.yoctoproject.org/user-contrib/dvhart/oe-core syslinux
  http://git.yoctoproject.org/cgit.cgi/user-contrib/dvhart/oe-core/log/?h=syslinux

Darren Hart (1):
  syslinux: Avoid using linux.ext2_fs.h if possible

 .../libinstaller-Avoid-using-linux-ext2_fs.h.patch |  975 ++++++++++++++++++++
 meta/recipes-devtools/syslinux/syslinux_4.03.bb    |    5 +-
 2 files changed, 978 insertions(+), 2 deletions(-)
 create mode 100644 meta/recipes-devtools/syslinux/files/libinstaller-Avoid-using-linux-ext2_fs.h.patch

-- 
1.7.6.5




             reply	other threads:[~2012-04-04 22:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-04 22:30 Darren Hart [this message]
2012-04-04 22:30 ` [PATCH 1/1] syslinux: Avoid using linux.ext2_fs.h if possible Darren Hart

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=cover.1333578393.git.dvhart@linux.intel.com \
    --to=dvhart@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.com \
    --cc=sgw@linux.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 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.