public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Ian Ray <ian.ray@ge.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH v2 0/1] More fixes for a distro with a merged /usr
Date: Fri,  8 Jan 2016 09:28:50 +0200	[thread overview]
Message-ID: <cover.1452235739.git.ian.ray@ge.com> (raw)

When building a distro with a merged /usr[1] the linux-firmware
recipe causes /lib to be re-created because of hard-coded paths.

Replace /lib with nonarch_base_libdir, as discussed in the email
thread for the first version of this patch.

Tested by building an image and verifying that rootfs contains a
link from lib to usr/lib as expected.

1. https://wiki.freedesktop.org/www/Software/systemd/TheCaseForTheUsrMerge/

Ian Ray (1):
  linux-firmware: remove hard-coded paths

 .../linux-firmware/linux-firmware_git.bb           | 134 ++++++++++-----------
 1 file changed, 67 insertions(+), 67 deletions(-)

-- 
2.4.5



             reply	other threads:[~2016-01-08  7:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-08  7:28 Ian Ray [this message]
2016-01-08  7:28 ` [PATCH v2 1/1] linux-firmware: remove hard-coded paths Ian Ray
2016-05-31  5:21   ` Ian Ray
2016-06-05 20:32     ` Burton, Ross

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.1452235739.git.ian.ray@ge.com \
    --to=ian.ray@ge.com \
    --cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox