public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Still <mikal@stillhq.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Makefile dependancies: scripts depending on configured kernel?
Date: Mon, 22 Mar 2004 20:14:52 +1100	[thread overview]
Message-ID: <405EAE8C.2090602@stillhq.com> (raw)
In-Reply-To: <20040322055617.GA2250@mars.ravnborg.org>

Sam Ravnborg wrote:

> The dependency for docs is (now) wrong.
> It should be:
> # Documentation targets
> # ---------------------------------------------------------------------------
> %docs: scripts_basic FORCE
>         $(Q)$(MAKE) $(build)=Documentation/DocBook $@
> 
> docproc is the only binary used by Documentation/Docbook, and it is already
> placed in scripts_basic.

True.

> Trivial - so I will include this in some other kbuild patch
> I'm preparing.

Cool, it will be nice to have this working out of the box again.

> Test a bit more, and you will see they are indeed needed.
> Note, some archs other than i386 have a bit different requirements
> because thay do not use an asm-offsett.h file.

Interesting. I built most of the targets and they still worked. I'm 
happy to accept that it's needed though.

Cheers,
Mikal

-- 

Michael Still (mikal@stillhq.com) | "All my life I've had one dream,
http://www.stillhq.com            |  to achieve my many goals"
UTC + 11                          |    -- Homer Simpson

      reply	other threads:[~2004-03-22  9:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-21 22:16 Makefile dependancies: scripts depending on configured kernel? Michael Still
2004-03-22  5:56 ` Sam Ravnborg
2004-03-22  9:14   ` Michael Still [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=405EAE8C.2090602@stillhq.com \
    --to=mikal@stillhq.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.org \
    /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