Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 1573] New: Alsa-utils alsactl/init/* not installed to target
Date: Thu, 15 Apr 2010 12:52:35 +0000 (UTC)	[thread overview]
Message-ID: <bug-1573-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=1573

           Summary: Alsa-utils alsactl/init/* not installed to target
           Product: buildroot
           Version: 2010.02
          Platform: Other
        OS/Version: Linux
            Status: NEW
          Severity: major
          Priority: P5
         Component: Other
        AssignedTo: unassigned at buildroot.uclibc.org
        ReportedBy: nick at leverton.org
                CC: buildroot at uclibc.org
   Estimated Hours: 0.0


When building alsa-utils 1.0.22 on BR 2010.02, the contents of ./alsactl/init
are copied to the staging dir, but not to the target.  This means that alsactl
on the target may not run correctly.  The following error message will be seen
on the device console during boot:

Restoring mixer state: /usr/sbin/alsactl: parse:1655: Unable to open file
'/usr/share/alsa/init/00main': No such file or directory

I think the target might be where these run-time scripts should go anyway,
rather than the staging dir ?


-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

             reply	other threads:[~2010-04-15 12:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-15 12:52 bugzilla at busybox.net [this message]
2010-04-15 12:58 ` [Buildroot] [Bug 1573] Alsa-utils alsactl/init/* not installed to target bugzilla at busybox.net
2010-04-26 20:59 ` bugzilla at busybox.net

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-1573-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@busybox.net \
    /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