Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Johan Oudinet <johan.oudinet@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 3/3] mp4v2: Remove --disable-debug workaround.
Date: Thu, 12 Mar 2015 16:12:27 +0100	[thread overview]
Message-ID: <1426173147-27755-3-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/mp4v2/mp4v2.mk | 6 ------
 1 file changed, 6 deletions(-)

diff --git a/package/mp4v2/mp4v2.mk b/package/mp4v2/mp4v2.mk
index 5d38116..1da5bc3 100644
--- a/package/mp4v2/mp4v2.mk
+++ b/package/mp4v2/mp4v2.mk
@@ -16,12 +16,6 @@ MP4V2_LICENSE_FILES = COPYING
 # disable it
 MP4V2_CONF_ENV = ac_cv_prog_FOUND_HELP2MAN=no
 
-# infrastructure passes --disable-debug if !BR2_ENABLE_DEBUG. With
-# mpv42 the only thing this option does is that it tries to strip any
-# -g* options from CFLAGS/CXXFLAGS. The logic to do so is
-# unfortunately buggy, so just pass --enable-debug to disable this
-MP4V2_CONF_OPTS = --enable-debug
-
 ifeq ($(BR2_LARGEFILE),y)
 MP4V2_CONF_OPTS += --enable-largefile
 else
-- 
2.1.0

  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 ` [Buildroot] [PATCH v2 2/3] lame: Remove --enable-debug workaround Johan Oudinet
2015-04-06 15:29   ` Yann E. MORIN
2015-03-12 15:12 ` Johan Oudinet [this message]
2015-04-06 15:29   ` [Buildroot] [PATCH v2 3/3] mp4v2: Remove --disable-debug workaround 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-3-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