From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] polarssl: disable assembly for more scenarios
Date: Mon, 27 Oct 2014 17:59:51 +0100 [thread overview]
Message-ID: <20141027175951.3f27a70b@free-electrons.com> (raw)
In-Reply-To: <544E789C.8090402@zacarias.com.ar>
Dear Gustavo Zacarias,
On Mon, 27 Oct 2014 13:53:48 -0300, Gustavo Zacarias wrote:
> > It's not really great to have to build things differently debugging on
> > BR2_ENABLE_DEBUG, because the prompt of BR2_ENABLE_DEBUG is "build
> > packages with debugging symbols". So the user may expect that we build
> > the same set of features, just with debugging symbols.
> >
> > Though I agree that with BR2_ENABLE_DEBUG also activating
> > --enable-debug, a lot more than just debugging symbols actually happens.
> >
> > Therefore, committed, thanks!
>
> Well i'm not very happy to build things differently (asm vs no asm) if
> debugging is on since it can change the result and make it pointless,
> but it wouldn't be too good to disable asm in general for thumb either
> so i threw the dice on the lesser evil.
Yeah, I'm fine with the trade-off as well.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-10-27 16:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-27 14:07 [Buildroot] [PATCH 1/2] polarssl: security bump to version 1.2.12 Gustavo Zacarias
2014-10-27 14:07 ` [Buildroot] [PATCH 2/2] polarssl: disable assembly for more scenarios Gustavo Zacarias
2014-10-27 16:48 ` Thomas Petazzoni
2014-10-27 16:53 ` Gustavo Zacarias
2014-10-27 16:59 ` Thomas Petazzoni [this message]
2014-10-27 16:47 ` [Buildroot] [PATCH 1/2] polarssl: security bump to version 1.2.12 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=20141027175951.3f27a70b@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