From: Ian Ray <ian.ray@ge.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/1] More fixes for a distro with a merged /usr
Date: Mon, 4 Jan 2016 15:14:53 +0200 [thread overview]
Message-ID: <cover.1451912446.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.
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
next reply other threads:[~2016-01-04 14:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-04 13:14 Ian Ray [this message]
2016-01-04 13:14 ` [PATCH 1/1] linux-firmware: remove hard-coded paths Ian Ray
2016-01-04 16:11 ` Matthias Schiffer
2016-01-04 16:32 ` Mark Hatle
2016-01-04 22:26 ` Matthias Schiffer
2016-01-04 22:56 ` Mark Hatle
2016-01-04 23:57 ` Matthias Schiffer
2016-01-05 0:28 ` Mark Hatle
2016-01-05 1:26 ` Matthias Schiffer
2016-01-05 14:03 ` Mark Hatle
2016-01-05 14:04 ` Ray, Ian (GE Healthcare)
2016-01-05 14:33 ` Mark Hatle
2016-01-05 14:41 ` Ray, Ian (GE Healthcare)
2016-01-05 17:06 ` Mark Hatle
2016-01-05 22:20 ` Phil Blundell
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.1451912446.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