From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 5768] New: Not able to build ALSA-Lib for static build
Date: Fri, 7 Dec 2012 04:45:27 +0000 (UTC) [thread overview]
Message-ID: <bug-5768-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=5768
Summary: Not able to build ALSA-Lib 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
When building ALSA-Lib for static build, there is a compilation faliure. Added
a patch(attached) inside "package/alsa-lib" 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
Changes are following :
--- a/modules/mixer/simple/sbasedl.c
+++ b/modules/mixer/simple/sbasedl.c
@@ -27,7 +27,11 @@
#include <fcntl.h>
#include <sys/ioctl.h>
#include <math.h>
+#ifdef HAVE_LIBDL
#include <dlfcn.h>
+#else
+#define RTLD_NOW 0
+#endif
#include "config.h"
#include "asoundlib.h"
#include "mixer_abst.h"
--- a/src/mixer/simple_abst.c
+++ b/src/mixer/simple_abst.c
@@ -34,7 +34,12 @@
#include <fcntl.h>
#include <sys/ioctl.h>
#include <math.h>
+#ifdef HAVE_LIBDL
#include <dlfcn.h>
+#else
+#define RTLD_NOW 0
+#define RTLD_GLOBAL 8
+#endif
#include "config.h"
#include "asoundlib.h"
#include "mixer_simple.h"
--
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.
next reply other threads:[~2012-12-07 4:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-07 4:45 bugzilla at busybox.net [this message]
2012-12-07 4:47 ` [Buildroot] [Bug 5768] Not able to build ALSA-Lib for static build bugzilla at busybox.net
2014-02-23 14:38 ` 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-5768-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