From: Johan Oudinet <johan.oudinet@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 2/3] lame: Remove --enable-debug workaround.
Date: Thu, 12 Mar 2015 16:12:26 +0100 [thread overview]
Message-ID: <1426173147-27755-2-git-send-email-johan.oudinet@gmail.com> (raw)
In-Reply-To: <1426173147-27755-1-git-send-email-johan.oudinet@gmail.com>
This is not needed since BR2_ENABLE_DEBUG does not set this flag
anymore.
Signed-off-by: Johan Oudinet <johan.oudinet@gmail.com>
---
package/lame/lame.mk | 7 -------
1 file changed, 7 deletions(-)
diff --git a/package/lame/lame.mk b/package/lame/lame.mk
index e47e0af..dcd155f 100644
--- a/package/lame/lame.mk
+++ b/package/lame/lame.mk
@@ -14,13 +14,6 @@ LAME_CONF_OPTS = --enable-dynamic-frontends
LAME_LICENSE = LGPLv2+
LAME_LICENSE_FILES = COPYING
-# Building lame with debug symbols needs the following macros to be
-# defined: _FPU_MASK_IM, _FPU_MASK_ZM, _FPU_MASK_OM.
-# So, if BR2_ENABLE_DEBUG is selected, then we have force lame to be
-# built without debug symbols because a number of architectures don't
-# have those macros defined.
-LAME_CONF_OPTS += --disable-debug
-
ifeq ($(BR2_PACKAGE_LIBSNDFILE),y)
LAME_DEPENDENCIES += libsndfile
LAME_CONF_OPTS += --with-fileio=sndfile
--
2.1.0
next prev parent reply other threads:[~2015-03-12 15:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-12 15:12 [Buildroot] [PATCH v2 1/3] Remove --{enable, disable}-debug configure flags Johan Oudinet
2015-03-12 15:12 ` Johan Oudinet [this message]
2015-04-06 15:29 ` [Buildroot] [PATCH v2 2/3] lame: Remove --enable-debug workaround Yann E. MORIN
2015-03-12 15:12 ` [Buildroot] [PATCH v2 3/3] mp4v2: Remove --disable-debug workaround Johan Oudinet
2015-04-06 15:29 ` Yann E. MORIN
2015-04-06 10:22 ` [Buildroot] [PATCH v2 1/3] Remove --{enable, disable}-debug configure flags Thomas Petazzoni
2015-04-06 15:28 ` Yann E. MORIN
2015-06-05 14:26 ` Thomas Petazzoni
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=1426173147-27755-2-git-send-email-johan.oudinet@gmail.com \
--to=johan.oudinet@gmail.com \
--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