From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 191] New: alsa-lib ARM binaries always built with EABI
Date: Wed, 18 Mar 2009 11:08:07 +0000 (UTC) [thread overview]
Message-ID: <bug-191-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=191
Target: xscale dev board
Build: buildroot-2009.02
Summary: alsa-lib ARM binaries always built with EABI
Product: buildroot
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: per-henrik.lundblom at connectblue.com
CC: buildroot at uclibc.org
Estimated Hours: 0.5
When configuring buildroot-2009.02 for OABI binaries (both uClibc/GCC and
kernel) and enabling ALSA lib, the output binaries always will be EABI
binaries.
Relevant buildroot config options:
BR2_VERSION="2009.02"
BR2_arm=y
BR2_xscale=y
BR2_ARM_TYPE="ARM_XSCALE"
BR2_ARM_OABI=y
BR2_ARCH="arm"
BR2_ENDIAN="LITTLE"
BR2_GCC_TARGET_TUNE="xscale"
BR2_GCC_TARGET_ABI="apcs-gnu"
BR2_PACKAGE_ALSA_LIB=y
This is due to a misconfiguration in package/multimedia/alsa-lib/alsa-lib.mk
Supplied patch should fix everything:
--- buildroot-2009.02/package/multimedia/alsa-lib/alsa-lib.mk 2009-02-12
09:49:56.000000000 +0100
+++ buildroot-2009.02-patched/package/multimedia/alsa-lib/alsa-lib.mk
2009-03-18 11:16:01.000000000 +0100
@@ -13,7 +13,7 @@ ALSA_LIB_TARGET_BINARY:=usr/lib/$(ALSA_L
ALSA_LIB_CFLAGS=$(TARGET_CFLAGS)
-ifeq ($(BR2_arm),y)
+ifeq ($(BR2_ARM_EABI),y)
ALSA_LIB_CFLAGS+=-mabi=aapcs-linux
endif
--
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-03-18 11:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-18 11:08 bugzilla at busybox.net [this message]
2009-03-18 11:17 ` [Buildroot] [Bug 191] alsa-lib ARM binaries always built with EABI bugzilla at busybox.net
2009-03-18 11:28 ` 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-191-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