public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Fedin <p.fedin@samsung.com>
To: 'Masahiro Yamada' <yamada.masahiro@socionext.com>
Cc: 'Linux Kbuild mailing list' <linux-kbuild@vger.kernel.org>,
	'Michal Marek' <mmarek@suse.com>
Subject: RE: PING: [PATCH] make build tool dependencies portable
Date: Mon, 07 Sep 2015 09:56:22 +0300	[thread overview]
Message-ID: <014501d0e93a$4ee5ea90$ecb1bfb0$@samsung.com> (raw)
In-Reply-To: <CAK7LNAS3UFq17rHobEUpS=fbyefscPunyHu9DMTAJESzcSfLxw@mail.gmail.com>

 Hello!

> scripts/Makefile has the following:
> 
> hostprogs-$(CONFIG_LOGO)         += pnmtologo
> 
> 
> This should work if you enable CONFIG_LOGO in Kconfig.

 Yes, i know this. But, pnmlogo, in its turn, depends on pnmlogo.c. This is currently implicit (i don't see explicit lines anywhere), and this appears not to work correctly everywhere.

> Please do not screw up Kbuild for Cygwin.
> 
> See the answer from Michal (and you agreed)
> https://patchwork.kernel.org/patch/7014361/

 Yes, i remember. And my fix doesn't contain any it's etc, it's simple and actually it's generic. Ok, how can improve it further? What about adding explicit dependencies to scripts/Makefile then? These explicit dependencies not only fix Cygwin-related problem, but also make the Makefile more readable, don't they?

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



  reply	other threads:[~2015-09-07  6:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-04 13:32 PING: [PATCH] make build tool dependencies portable Pavel Fedin
2015-09-05 15:26 ` Masahiro Yamada
2015-09-07  6:56   ` Pavel Fedin [this message]
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='014501d0e93a$4ee5ea90$ecb1bfb0$@samsung.com' \
    --to=p.fedin@samsung.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=mmarek@suse.com \
    --cc=yamada.masahiro@socionext.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