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 5774] New: Not able to build ALSA-Utils for static build
Date: Fri,  7 Dec 2012 05:06:17 +0000 (UTC)	[thread overview]
Message-ID: <bug-5774-163@https.bugs.busybox.net/> (raw)

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

           Summary: Not able to build ALSA-Utils for static build
           Product: buildroot
           Version: 2012.08
          Platform: PC
        OS/Version: Windows
            Status: NEW
          Severity: critical
          Priority: P5
         Component: Other
        AssignedTo: unassigned at buildroot.uclibc.org
        ReportedBy: pankaj.dev at st.com
                CC: buildroot at uclibc.org
   Estimated Hours: 0.0


Created attachment 4688
  --> https://bugs.busybox.net/attachment.cgi?id=4688
Patch to build alsa-utils statically

When building ALSA-Utils for static build, there is a compilation faliure.
Added
a patch(attached) inside "package/multimedia\alsa-utils" directory to build
properly.

Not able to log this bug in ALSA project, the web-site hangs. The bug also
exists in ALSA 1.0.26(latest) included in buildroot 2012.11

The correction is not a generic, one. Not able to figure out how to modify the
configure script such that it includes "-ldl" only for non-static builds

-- 
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:[~2012-12-07  5:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-07  5:06 bugzilla at busybox.net [this message]
2014-02-07 12:55 ` [Buildroot] [Bug 5774] Not able to build ALSA-Utils for static build bugzilla at busybox.net
2014-02-21 14:34 ` bugzilla at busybox.net
2014-02-23 14:43 ` 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-5774-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