From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/beecrypt: Fix build with BR2_ENABLE_DEBUG=yes
Date: Sun, 19 Oct 2014 17:31:11 +0200 [thread overview]
Message-ID: <20141019173111.07415809@free-electrons.com> (raw)
In-Reply-To: <1413732225-14832-1-git-send-email-bernd.kuhls@t-online.de>
Dear Bernd Kuhls,
On Sun, 19 Oct 2014 17:23:44 +0200, Bernd Kuhls wrote:
> Otherwise configure issues this error message:
> configure: error: --enable-debug cannot be used in conjunction with --enable-expert-mode
>
> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
> ---
> package/beecrypt/beecrypt-0003-configure.patch | 30 ++++++++++++++++++++++++
> package/beecrypt/beecrypt.mk | 4 ++++
> 2 files changed, 34 insertions(+)
> create mode 100644 package/beecrypt/beecrypt-0003-configure.patch
I don't quite understand what's going on here. You need both a patch
*and* passing --disable-expert-mode to get --enable-debug to work? What
is the relation between the two?
In our case, I would expect to always use --enable-expert-mode, since
we do want beecrypt to use Buildroot CFLAGS, not its own CFLAGS.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-10-19 15:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-19 15:23 [Buildroot] [PATCH 1/1] package/beecrypt: Fix build with BR2_ENABLE_DEBUG=yes Bernd Kuhls
2014-10-19 15:23 ` [Buildroot] [PATCH 1/1] package/mesa3d: Fix uClibc " Bernd Kuhls
2014-10-19 15:32 ` Thomas Petazzoni
2014-10-19 15:28 ` [Buildroot] [PATCH 1/1] package/beecrypt: Fix " Bernd Kuhls
2014-10-19 15:31 ` Thomas Petazzoni [this message]
2014-10-19 16:37 ` Bernd Kuhls
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=20141019173111.07415809@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