All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: richard.purdie@linuxfoundation.org
Cc: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/1] linux-libc-headers: fix long path name build breakage
Date: Thu, 10 Jan 2013 15:49:15 -0500	[thread overview]
Message-ID: <cover.1357850854.git.bruce.ashfield@windriver.com> (raw)

Richard/Saul,

Here's a patch to fix the recent autobuilder failures with the updated
linux-libc-headers (3.7) as the default.

I wasn't sure if we needed a PR bump, but I added one anyone. Let
me know if I should respin with it removed.

I'll send this patch upstream for comments as well, but in it's current
form it does get us up and running on the builders.

Until this is accepted, it will be propagated to any > 3.7 kernel headers,
just in case they are used in a long path name configuration.

Cheers,

Bruce

The following changes since commit 66f4c8a674d9f8db958b13866af4d63ab8cbcd44:

  guile: add explicit dependency to avoid parallel build issue (2013-01-09 15:05:26 +0000)

are available in the git repository at:

  git://git.pokylinux.org/poky-contrib zedd/kernel
  http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel

Bruce Ashfield (1):
  linux-libc-headers: fix headers install in long path name
    environments

 ...efile.headersinst-install-headers-from-sc.patch |   47 ++++++++++++++++++++
 .../linux-libc-headers/linux-libc-headers_3.7.bb   |    4 ++
 2 files changed, 51 insertions(+)
 create mode 100644 meta/recipes-kernel/linux-libc-headers/linux-libc-headers/scripts-Makefile.headersinst-install-headers-from-sc.patch

-- 
1.7.10.4




             reply	other threads:[~2013-01-10 21:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-10 20:49 Bruce Ashfield [this message]
2013-01-10 20:49 ` [PATCH 1/1] linux-libc-headers: fix headers install in long path name environments Bruce Ashfield

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.1357850854.git.bruce.ashfield@windriver.com \
    --to=bruce.ashfield@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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.