From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 569] New: Alsa-utils build fails
Date: Fri, 14 Aug 2009 08:32:49 +0000 (UTC) [thread overview]
Message-ID: <bug-569-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=569
Host: i686
Target: i686
Build: x86_64
Summary: Alsa-utils build fails
Product: buildroot
Version: unspecified
Platform: All
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: fpasch at googlemail.com
CC: buildroot at uclibc.org
Estimated Hours: 0.0
Building alsa-utils for i686 on a x86_64 machine fails while linking alsamixer
because the linker uses the wrong ncurses-lib.
I've seen those alsa-utils-1.0.18-acs_map.patch.<ARCH> patches, but for x86
this approach fails...
The problem is, that alsa-configure uses the script ncurses5-config from host
to obtain the paths to ncurses-lib.
Perhaps a better workaround than those acs_maps-patches could be to define the
correct ncurses5-config:
--- 1/package/multimedia/alsa-utils/alsa-utils.mk
+++ 2/package/multimedia/alsa-utils/alsa-utils.mk
@@ -25,6 +25,7 @@
(cd $(ALSA_UTILS_DIR); rm -f config.cache; \
$(TARGET_CONFIGURE_OPTS) \
$(TARGET_CONFIGURE_ARGS) \
+ ac_cv_prog_ncurses5_config=$(STAGING_DIR)/bin/ncurses5-config \
CFLAGS="$(TARGET_CFLAGS)" \
LDFLAGS="$(TARGET_LDFLAGS)" \
./configure \
Simon Pasch
--
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:[~2009-08-14 8:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-14 8:32 bugzilla at busybox.net [this message]
2009-08-19 22:13 ` [Buildroot] [Bug 569] Alsa-utils build fails 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-569-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 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.