From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/Makefile.in: Do not add --enable-debug flag.
Date: Wed, 11 Mar 2015 21:42:25 +0100 [thread overview]
Message-ID: <20150311214225.746fe0cd@free-electrons.com> (raw)
In-Reply-To: <1426093401-23108-1-git-send-email-johan.oudinet@gmail.com>
Dear Johan Oudinet,
On Wed, 11 Mar 2015 18:03:21 +0100, Johan Oudinet wrote:
> Adding this flag when BR2_ENABLE_DEBUG is activated make several
> packages to produce binaries that do not work as expected (e.g., dhcp,
> lame, nano). Moreover, the help message of BR2_ENABLE_DEBUG does not
> say it is adding this flag. It is supposed to build packages with
> debugging symbols enabled. So, let it do that only.
>
> Signed-off-by: Johan Oudinet <johan.oudinet@gmail.com>
I am personally in favor of this change, so thanks for bringing it up.
> -ifeq ($(BR2_ENABLE_DEBUG),y)
> -ENABLE_DEBUG := --enable-debug
> -else
> +ifneq ($(BR2_ENABLE_DEBUG),y)
> ENABLE_DEBUG := --disable-debug
> endif
So if we have BR2_ENABLE_DEBUG enabled, then we don't pass
--disable-debug. And when BR2_ENABLE_DEBUG is disabled, we're passing
it. I'm not sure to understand the logic here.
Shouldn't we simply unconditionally pass --disable-debug, or not pass
anything at all?
Also, a number of packages had workarounds in their specific .mk file
to avoid --enable-debug. It would be good to get rid of such
workarounds as well.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-03-11 20:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-11 17:03 [Buildroot] [PATCH 1/1] package/Makefile.in: Do not add --enable-debug flag Johan Oudinet
2015-03-11 20:42 ` Thomas Petazzoni [this message]
2015-03-12 13:01 ` Johan Oudinet
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=20150311214225.746fe0cd@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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