LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Oleg Verych <olecom@flower.upol.cz>
To: akpm@linux-foundation.org
Cc: vapier.adi@gmail.com, olecom@flower.upol.cz, sam@ravnborg.org,
	linux-kernel@vger.kernel.org
Subject: Re: + search-a-little-harder-for-mkimage.patch added to -mm tree
Date: Thu, 8 Feb 2007 15:11:36 +0100	[thread overview]
Message-ID: <E1HF9zs-0006Ei-2k@flower> (raw)
In-Reply-To: <200702080607.l1867c0D006861@shell0.pdx.osdl.net>

> From: akpm@linux-foundation.org
> Newsgroups: gmane.linux.kernel.commits.mm
> Subject: + search-a-little-harder-for-mkimage.patch added to -mm tree
> Date: Wed, 07 Feb 2007 22:07:38 -0800
[]
> ------------------------------------------------------
> Subject: search a little harder for mkimage
> From: "Mike Frysinger" <vapier.adi@gmail.com>
>
> Check to see if `${CROSS_COMPILE}mkimage` exists and if not, fall back to
> the standard `mkimage`

Understanding of what mkuboot.sh is doing leads to:

-- ordinary addition of PATH to (possible) executable, named mkimage;
-- in case of any other problem to execute it: permissions, aliasing due to
   wrong $PATH (and setting it up isn't handle either), script will print
   *wrong* message, in case of CROSS_COMPILE filename;
-- minor overkill due to double wrapping of all of this;

`make' itself executes programs by search $PATH, prints *right*
messages in case of errors.

Unless author of the patch or script itself have really strong position to
not remove it, please.

There are currently four users of this, all like this:

MKIMAGE := $(srctree)/scripts/mkuboot.sh
[...]
quiet_cmd_uimage = UIMAGE  $@
      cmd_uimage = $(CONFIG_SHELL) $(MKIMAGE) -A sh -O linux -T kernel \
                    -C gzip -a $(KERNEL_LOAD) -e $(KERNEL_LOAD) \
                    -n'Linux-$(KERNELRELEASE)' -d $< $@

proposition is to substitute:
     "$(CONFIG_SHELL) $(MKIMAGE)"
with
     "mkimage"

and optional, for particular Makefile, "$(CROSS_COMPILE)" prefix.
Remove mkuboot.sh.

> The Blackfin toolchain includes mkimage, but we dont want to namespace
> collide with any of the user's system setup, so we prefix it with our
> toolchain name.
>
> Signed-off-by: Mike Frysinger <vapier@gentoo.org>
> Cc: Sam Ravnborg <sam@ravnborg.org>
> Cc: Oleg Verych <olecom@flower.upol.cz>
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> ---
>
>  scripts/mkuboot.sh |   11 +++++++----
>  1 file changed, 7 insertions(+), 4 deletions(-)
>
> diff -puN scripts/mkuboot.sh~search-a-little-harder-for-mkimage scripts/mkuboot.sh
> --- a/scripts/mkuboot.sh~search-a-little-harder-for-mkimage
> +++ a/scripts/mkuboot.sh
> @@ -4,12 +4,15 @@
>  # Build U-Boot image when `mkimage' tool is available.
>  #
>  
> -MKIMAGE=$(type -path mkimage)
> +MKIMAGE=$(type -path ${CROSS_COMPILE}mkimage)
>  
>  if [ -z "${MKIMAGE}" ]; then
> -	# Doesn't exist
> -	echo '"mkimage" command not found - U-Boot images will not be built' >&2
> -	exit 0;
> +	MKIMAGE=$(type -path mkimage)
> +	if [ -z "${MKIMAGE}" ]; then
> +		# Doesn't exist
> +		echo '"mkimage" command not found - U-Boot images will not be built' >&2
> +		exit 0;
> +	fi
>  fi
>  
>  # Call "mkimage" to create U-Boot image
> _
>
> Patches currently in -mm which might be from vapier.adi@gmail.com are
>
> search-a-little-harder-for-mkimage.patch
> scrub-non-__glibc__-checks-in-linux-socketh-and-linux-stath.patch
>

       reply	other threads:[~2007-02-08 14:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200702080607.l1867c0D006861@shell0.pdx.osdl.net>
2007-02-08 14:11 ` Oleg Verych [this message]
2007-02-08 14:28   ` Mike Frysinger
2007-02-08 20:25     ` Oleg Verych
2007-02-08 20:35       ` Mike Frysinger
2007-02-08 21:40         ` - " Oleg Verych

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=E1HF9zs-0006Ei-2k@flower \
    --to=olecom@flower.upol.cz \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.org \
    --cc=vapier.adi@gmail.com \
    --subject='Re: + search-a-little-harder-for-mkimage.patch added to -mm tree' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).