public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Fedin <p.fedin@samsung.com>
To: linux-kbuild@vger.kernel.org
Cc: 'Michal Marek' <mmarek@suse.com>
Subject: PING: [PATCH] make build tool dependencies portable
Date: Fri, 04 Sep 2015 16:32:54 +0300	[thread overview]
Message-ID: <01e001d0e716$34a48b80$9deda280$@samsung.com> (raw)

Ping

Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia


> -----Original Message-----
> From: linux-kbuild-owner@vger.kernel.org [mailto:linux-kbuild-owner@vger.kernel.org] On
> Behalf Of Pavel Fedin
> Sent: Thursday, August 27, 2015 12:08 PM
> To: linux-kbuild@vger.kernel.org
> Cc: Michal Marek
> Subject: [PATCH] make build tool dependencies portable
> 
> Autogenerated .c files depend on their generator tool, and an implicit
> rule is used to build the tool itself. However, an explicit rule
> is required on platforms where the .exe suffix is used for hostprogs.
> 
> This fixes the following errors when building on Cygwin:
> 
> make[3]: *** No rule to make target 'drivers/video/logo/logo_linux_clut224.c',
> needed by 'drivers/video/logo/logo_linux_clut224.o'.  Stop.
> scripts/Makefile.build:403: recipe for target 'drivers/video/logo' failed
> 
> make[2]: *** No rule to make target 'crypto/asymmetric_keys/x509-asn1.c',
> needed by 'crypto/asymmetric_keys/x509-asn1.o'.  Stop.
> scripts/Makefile.build:403: recipe for target 'crypto/asymmetric_keys' failed
> 
> Signed-off-by: Pavel Fedin <p.fedin@samsung.com>
> ---
>  drivers/video/logo/Makefile | 1 +
>  scripts/Makefile.build      | 2 ++
>  2 files changed, 3 insertions(+)
> 
> diff --git a/drivers/video/logo/Makefile b/drivers/video/logo/Makefile
> index 3b43781..cc636f1 100644
> --- a/drivers/video/logo/Makefile
> +++ b/drivers/video/logo/Makefile
> @@ -38,6 +38,7 @@ extra-y += $(call logo-cfiles,_clut224,ppm)
>  extra-y += $(call logo-cfiles,_gray256,pgm)
> 
>  pnmtologo := scripts/pnmtologo
> +$(pnmtologo): $(objtree)/scripts/pnmtologo.c
> 
>  # Create commands like "pnmtologo -t mono -n logo_mac_mono -o ..."
>  quiet_cmd_logo = LOGO    $@
> diff --git a/scripts/Makefile.build b/scripts/Makefile.build
> index 01df30a..c9ce3b0 100644
> --- a/scripts/Makefile.build
> +++ b/scripts/Makefile.build
> @@ -316,6 +316,8 @@ quiet_cmd_asn1_compiler = ASN.1   $@
>  $(obj)/%-asn1.c $(obj)/%-asn1.h: $(src)/%.asn1 $(objtree)/scripts/asn1_compiler
>  	$(call cmd,asn1_compiler)
> 
> +$(objtree)/scripts/asn1_compiler: $(objtree)/scripts/asn1_compiler.c
> +
>  # Build the compiled-in targets
>  # ---------------------------------------------------------------------------
> 
> --
> 2.4.4
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


             reply	other threads:[~2015-09-04 13:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-04 13:32 Pavel Fedin [this message]
2015-09-05 15:26 ` PING: [PATCH] make build tool dependencies portable Masahiro Yamada
2015-09-07  6:56   ` Pavel Fedin
2015-09-07 13:20     ` Masahiro Yamada
2015-09-09  8:34       ` Pavel Fedin

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='01e001d0e716$34a48b80$9deda280$@samsung.com' \
    --to=p.fedin@samsung.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=mmarek@suse.com \
    /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