From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 14471] New: alsa_utils wrong deployment
Date: Tue, 21 Dec 2021 20:20:48 +0000 [thread overview]
Message-ID: <bug-14471-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=14471
Bug ID: 14471
Summary: alsa_utils wrong deployment
Product: buildroot
Version: 2021.11
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned@buildroot.uclibc.org
Reporter: htenberge@gmail.com
CC: buildroot@uclibc.org
Target Milestone: ---
When the alsa_utils package is deployed, it deploys the /usr/share/alsa one
level too deep.
Instead of having a /usr/share/alsa with several files and subdirectories, some
parts are being deployed in /usr/share/alsa/alsa.
I'm not entirely what the right way is to fix this, but this simple hack fixed
it:
diff --git a/package/alsa-utils/alsa-utils.mk
b/package/alsa-utils/alsa-utils.mk
index 427280c1e6..da00f07d52 100644
--- a/package/alsa-utils/alsa-utils.mk
+++ b/package/alsa-utils/alsa-utils.mk
@@ -76,8 +76,8 @@ define ALSA_UTILS_INSTALL_TARGET_CMDS
cp -rdpf $(STAGING_DIR)/usr/share/sounds/alsa/*
$(TARGET_DIR)/usr/share/sounds/alsa/; \
fi
if [ -x "$(TARGET_DIR)/usr/sbin/alsactl" ]; then \
- mkdir -p $(TARGET_DIR)/usr/share/; \
- cp -rdpf $(STAGING_DIR)/usr/share/alsa/
$(TARGET_DIR)/usr/share/alsa/; \
+ mkdir -p $(TARGET_DIR)/usr/share/alsa; \
+ cp -rdpf $(STAGING_DIR)/usr/share/alsa/*
$(TARGET_DIR)/usr/share/alsa/; \
fi
endef
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2021-12-21 20:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-21 20:20 bugzilla [this message]
2021-12-22 14:15 ` [Buildroot] [Bug 14471] alsa_utils wrong deployment bugzilla
2021-12-25 13:38 ` bugzilla
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=bug-14471-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@uclibc.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.