From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] ptxdist: Get rid of toolchain check-error message
Date: Wed, 30 May 2012 09:24:11 +0200 [thread overview]
Message-ID: <20120530072411.GK19394@pengutronix.de> (raw)
In-Reply-To: <1338208981-8681-4-git-send-email-bartvdrmeulen@gmail.com>
On Mon, May 28, 2012 at 02:42:30PM +0200, Bart vdr. Meulen wrote:
> From: Remy Bohmer <linux@bohmer.net>
>
> If no toolchain info is specified, skip check completely
>
> Ptxdist does a toolchain check, but if all fields are empty we
> assume it is an external (not an OSELAS) toolchain.
>
> Signed-off-by: Remy Bohmer <linux@bohmer.net>
> ---
> bin/ptxdist | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/bin/ptxdist b/bin/ptxdist
> index 440a7aa..d9486e4 100755
> --- a/bin/ptxdist
> +++ b/bin/ptxdist
> @@ -1382,6 +1382,14 @@ do_select_toolchain_guess()
> local target="$(ptxd_get_ptxconf PTXCONF_GNU_TARGET)"
> local gcc_version="$(ptxd_get_ptxconf PTXCONF_CROSSCHAIN_CHECK)"
>
> + if [ -z "${vendor}" -a \
> + ! -z "${target}" -a \
! -z == -n
> + -z "${gcc_version}" ]; then
I'd prefer to actually check the gcc version. Or at least allow for both.
Michael
> + ptxd_dialog_msgbox \
> + "info: No toolchain information, assuming external toolchain..."
> + return 1
> + fi
> +
> if [ -z "${vendor}" -o \
> -z "${target}" -o \
> -z "${gcc_version}" ]; then
> --
> 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 7:24 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 7:24 ` 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=20120530072411.GK19394@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