From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] gdb: Use CONF_ENV and MAKE_ENV
Date: Wed, 30 May 2012 18:50:21 +0200 [thread overview]
Message-ID: <20120530165021.GH31687@pengutronix.de> (raw)
In-Reply-To: <1338208981-8681-16-git-send-email-bartvdrmeulen@gmail.com>
On Mon, May 28, 2012 at 02:42:42PM +0200, Bart vdr. Meulen wrote:
> From: "Bart vdr. Meulen" <bartvdrmeulen@gmail.com>
>
> Use CONF_ENV and MAKE_ENV variables for building GDB 7.2 instead of
> the deprecated _ENV variable. This ensures that system-header dir
> is passed on correctly to gdb make environment.
Can you elaborate, what the problem is? gdb uses autoconf. All the relevant
variables should be set during configure.
Michael
> Signed-off-by: Bart vdr. Meulen <bartvdrmeulen@gmail.com>
> ---
> rules/gdb.make | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/rules/gdb.make b/rules/gdb.make
> index 4309f3d..ecbe020 100644
> --- a/rules/gdb.make
> +++ b/rules/gdb.make
> @@ -34,7 +34,10 @@ GDB_URL := \
> # Prepare
> # ----------------------------------------------------------------------------
>
> -GDB_ENV := \
> +GDB_CONV_ENV := \
> + $(CROSS_ENV) \
> + $(CROSS_ENV_FLAGS_FOR_TARGET)
> +GDB_MAKE_ENV := \
> $(CROSS_ENV) \
> $(CROSS_ENV_FLAGS_FOR_TARGET)
>
> --
> 1.7.9.5
>
>
> --
> ptxdist mailing list
> ptxdist@pengutronix.de
>
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
--
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2012-05-30 16:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-28 12:42 Bart vdr. Meulen
2012-05-30 16:50 ` Michael Olbrich [this message]
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=20120530165021.GH31687@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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